From e8bb6ee5c058eebeb75882eae16d383d6c19bf44 Mon Sep 17 00:00:00 2001 From: YanMeddour Date: Thu, 30 Nov 2023 14:55:49 +0100 Subject: [PATCH 01/14] Refresh the vmware2 vm doc --- .../procedures/virtualization-vmware2-vm.md | 807 +++++++++++++++--- .../procedures/virtualization-vmware2-vm.md | 804 ++++++++++++++--- 2 files changed, 1387 insertions(+), 224 deletions(-) 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 73da950deffb..4bc851f6d662 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 @@ -5,76 +5,165 @@ title: VMware VM import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -## Vue d'ensemble +## Contenu du pack -VMWare est une solution de Virtualisation et d'infrastructure de Cloud Computing. +### Modèles -Le connecteur de supervision Centreon s'appuie sur le SDK VMWare pour requêter l'API du vCenter au travers d'un connecteur dédié. +Le connecteur de supervision **VMware VM** apporte un modèle d'hôte : -## Contenu du connecteur de supervision +* **Virt-VMWare2-VM-custom** -### Objets supervisés +Le connecteur apporte les modèles de service suivants +(classés selon le modèle d'hôte auquel ils sont rattachés) : -* Virtual Machines + + -### Règles de découvertes +| Alias | Modèle de service | Description | +|:--------------------|:------------------------------------------------|:-------------------------------------------------------------------------------------------------------------| +| Vm-Limit | Virt-VMWare2-Vm-Limit-Generic-custom | Contrôle permettant de vérifier la définition de limites | +| Vm-Snapshot | Virt-VMWare2-Vm-Snapshot-Generic-custom | Contrôle permettant de vérifier l'âge des snapshosts sur la machine virtuelle | +| Vm-Status | Virt-VMWare2-Vm-Status-Generic-custom | Contrôle permettant de vérifier l'état global d'une machine virtuelle | +| Vm-Thinprovisioning | Virt-VMWare2-Vm-Thinprovisioning-Generic-custom | Contrôle permettant de vérifier si une machine virtuelle possède un disque en mode 'thinprovisioning' ou non | +| Vm-Tools | Virt-VMWare2-Vm-Tools-Generic-custom | Contrôle permettant de vérifier l'état des vmtools d'une machine virtuelle | - - +> Les services listés ci-dessus sont créés automatiquement lorsque le modèle d'hôte **Virt-VMWare2-VM-custom** est utilisé. + + + + +| Alias | Modèle de service | Description | +|:-------------------|:-----------------------------------------------|:----------------------------------------------------------------------------------------------------------| +| Vm-Cpu | Virt-VMWare2-Vm-Cpu-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation CPU d'une machine virtuelle | +| Vm-Datastores-Iops | Virt-VMWare2-Vm-Datastores-Iops-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation des datastores rattachées à une machine virtuelle. | +| Vm-Device | Virt-VMWare2-Vm-Device-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation CPU d'une machine virtuelle | +| Vm-Memory | Virt-VMWare2-Vm-Memory-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation mémoire d'une machine virtuelle | +| Vm-Swap | Virt-VMWare2-Vm-Swap-Generic-custom | Contrôle permettant de vérifier si une machine virtuelle swappe | -| Rule name | Description | -| :----------------------------- | :---------------------------------------------------------------- | -| Virt-VMWare2-VM-HostDiscovery | Découvrez vos Machines Virtuelles liées à un vCenter ou à un ESXi | +> Les services listés ci-dessus ne sont pas créés automatiquement lorsqu'un modèle d'hôte est appliqué. Pour les utiliser, [créez un service manuellement](/docs/monitoring/basic-objects/services) et appliquez le modèle de service souhaité. -### Métriques Collectées +### Règles de découverte -En plus des modes et des métriques détaillées ci-après, il est également possible de superviser les éléments suivants : +#### Découverte d'hôtes -* VM-Cpu : Supervision avancée du CPU (CPU ready) -* VM-Datastores-Iops : Utilisation de la VM en Iops sur les Datastores -* VM-Swap : Utilisation du swap de la VM -* VM-Device : Contrôle un périphérique d'une VM (Par exemple VirtualCdrom) +| Nom de la règle | Description | +|:----------------|:--------------------------------| +| VMWare VM | Discover VMWare Virtual Machine | + +Rendez-vous sur la [documentation dédiée](/docs/monitoring/discovery/hosts-discovery) pour en savoir plus sur la découverte automatique d'hôtes. + +### Métriques & statuts collectés + +Voici le tableau des services pour ce connecteur, détaillant les métriques rattachées à chaque service. - + -| Metric name | Description | Unit | -| :---------- | :------------------------------------------------------------- | :--- | -| status | Status of the VMware Tools (installed, running and up-to-date) | | +| Métrique | Unité | +|:----------------------------------------------|:------| +| *vm*~status | N/A | +| *vm*~vm.cpu.utilization.percentage | % | +| *vm*~vm.cpu.utilization.mhz | MHz | +| *vm*~vm.cpu.ready.percentage | % | +| *vm*~*cpu*#vm.core.cpu.utilization.percentage | MHz | + +> Pour obtenir ce nouveau format de métrique, incluez la valeur **--use-new-perfdata** dans la macro de service **EXTRAOPTIONS**. - + + +| Métrique | Unité | +|:-----------------------------------------------|:------| +| *vm*~status | N/A | +| *vm*~vm.datastore.latency.max.milliseconds | ms | +| *vm*~*datastore*#vm.datastore.read.usage.iops | iops | +| *vm*~*datastore*#vm.datastore.write.usage.iops | iops | -| Metric name | Description | Unit | -| :---------- | :----------------------------------------- | :--- | -| status | Status of the Thinprovisoning virtualdisks | | +> Pour obtenir ce nouveau format de métrique, incluez la valeur **--use-new-perfdata** dans la macro de service **EXTRAOPTIONS**. - + + +| Métrique | Unité | +|:--------------------------------|:------| +| vm.devices.connected.count | count | +| *vm*#status | N/A | +| *vm*#vm.devices.connected.count | count | + +> Pour obtenir ce nouveau format de métrique, incluez la valeur **--use-new-perfdata** dans la macro de service **EXTRAOPTIONS**. + + + -| Metric name | Description | Unit | -| :------------ | :----------------------- | :--- | -| status | Overall status of the VM | | +| Métrique | Unité | +|:--------------|:------| +| cpu-status | N/A | +| memory-status | N/A | +| disk-status | N/A | + +> Pour obtenir ce nouveau format de métrique, incluez la valeur **--use-new-perfdata** dans la macro de service **EXTRAOPTIONS**. + + + + +| Métrique | Unité | +|:------------------------------------|:------| +| *vm*~status | N/A | +| *vm*~vm.memory.consumed.usage.bytes | B | +| *vm*~vm.memory.active.usage.bytes | B | +| *vm*~vm.memory.overhead.bytes | B | +| *vm*~vm.memory.ballooning.bytes | B | +| *vm*~vm.memory.shared.bytes | B | + +> Pour obtenir ce nouveau format de métrique, incluez la valeur **--use-new-perfdata** dans la macro de service **EXTRAOPTIONS**. -| Metric name | Description | Unit | -| :---------------------------------- | :------------------------------------------------------------ | :---- | -| vm.snapshots.warning.current.count | Number of VM's snapshot older than 3 days (default threshold) | Count | -| vm.snapshots.critical.current.count | Number of VM's snapshot older than 5 days (default threshold) | Count | +| Métrique | Unité | +|:------------------------------------|:------| +| vm.snapshots.warning.current.count | count | +| vm.snapshots.critical.current.count | count | - + + +| Métrique | Unité | +|:--------------------|:------| +| *vm*#status | N/A | +| *vm*#overall-status | N/A | + +> Pour obtenir ce nouveau format de métrique, incluez la valeur **--use-new-perfdata** dans la macro de service **EXTRAOPTIONS**. + + + + +| Métrique | Unité | +|:--------------------------------------|:------| +| *vm*#status | N/A | +| *vm*#vm.swap.in.usage.bytespersecond | B/s | +| *vm*#vm.swap.out.usage.bytespersecond | B/s | + +> Pour obtenir ce nouveau format de métrique, incluez la valeur **--use-new-perfdata** dans la macro de service **EXTRAOPTIONS**. + + + + +| Métrique | Description | Unité | +|:------------|:-------------------------------------------|:------| +| status | Status of the Thinprovisoning virtualdisks | | + + + -| Metric name | Description | Unit | -| :--------------------------- | :--------------------- | :---- | -| vm.limit.cpu.alerts.count | Alerts on CPU limit | Count | -| vm.limit.memory.alerts.count | Alerts on Memory limit | Count | -| vm.limit.disk.alerts.count | Alerts on Disk limit | Count | +| Métrique | Unité | +|:------------------------------------|:------| +| vm.tools.notupdated.current.count | count | +| vm.tools.notrunning.current.count | count | +| vm.tools.notinstalled.current.count | count | @@ -151,7 +240,7 @@ Vous pouvez vérifiez que votre configuration est fonctionelle en consultant les ### Balises et Attributs personnalisés -Pour découvrir les balises et les attributs personnalisés, vous devez : +Pour découvrir les balises et les attributs personnalisés, vous devez : * utiliser la version **3.2.5** de **centreon-vmware-daemon** * ajouter **--tags** dans les options supplémentaires de découverte : allez à la page **Configuration > Hôtes > Découverte**, et à la 3ème étape (**Définir les paramètres de découverte**), dans la section **Paramètres supplémentaires**, dans le champ **Options supplémentaires**, saisissez **--tags**. @@ -162,126 +251,618 @@ Le Collecteur Centreon avec le connecteur VMWare d'installé doit accéder en HT Les Collecteurs requêtant le Collecteur avec le connecteur VMWare doit accéder en TCP/5700 au Collecteur avec le Connecteur VMWare. -## Installation +## Installer le connecteur de supervision - - +### Pack -1. Installer le Plugin sur l'ensemble des Collecteurs Centreon supervisant l'infrastructure VMWare: +1. Si la plateforme est configurée avec une licence *online*, l'installation d'un paquet +n'est pas requise pour voir apparaître le connecteur dans le menu **Configuration > Gestionnaire de connecteurs de supervision**. +Au contraire, si la plateforme utilise une licence *offline*, installez le paquet +sur le **serveur central** via la commande correspondant au gestionnaire de paquets +associé à sa distribution : + + + ```bash -yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin +dnf install centreon-pack-virtualization-vmware2-vm ``` -2. Installer le connecteur de supervision 'Vmware VM' depuis la page **Configuration > Gestionnaire de connecteurs de supervision** sur l'interface Web de Centreon. - - + + +```bash +dnf install centreon-pack-virtualization-vmware2-vm +``` -1. Installer le Plugin sur l'ensemble des collecteurs Centreon supervisant l'infrastructure VMWare: + + ```bash -yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin +apt install centreon-pack-virtualization-vmware2-vm ``` -2. Installer le RPM du connecteur de supervision contenant les modèles de supervision: + + ```bash yum install centreon-pack-virtualization-vmware2-vm ``` -3. Installer le connecteur de supervision 'Vmware VM' depuis la page **Configuration > Gestionnaire de connecteurs de supervision** sur l'interface Web de Centreon. - -## Configuration +2. Quel que soit le type de la licence (*online* ou *offline*), installez le connecteur **VMware VM** +depuis l'interface web et le menu **Configuration > Gestionnaire de connecteurs de supervision**. -* Depuis l'interface Web de Centreon, ajoutez un nouvel Hôte depuis la page "Configuration > Hôtes". -* Appliquez le modèle "Virt-VMWare2-VM-custom" et configurez toutes les macros : +### Plugin -| Mandatory | Name | Description | -| :---------- | :------------------------- | :----------------------------------------------------- | -| X | CENTREONVMWARECONTAINER | Name of your container in the file centreon_vmware.pm | -| X | CENTREONVMWAREHOST | The Centreon server that launches the connection | -| X | CENTREONVMWAREPORT | By default: 5700 | -| X | VMNAME | Name of the VM (defined in your VMWare infrastructure) | -| | VMUUID | Specify The VM UUID | -| | VMWAREEXTRAOPTIONS | Customize it with your own if needed | +À partir de Centreon 22.04, il est possible de demander le déploiement automatique +du plugin lors de l'utilisation d'un connecteur. Si cette fonctionnalité est activée, et +que vous ne souhaitez pas découvrir des éléments pour la première fois, alors cette +étape n'est pas requise. -## FAQ +> Plus d'informations dans la section [Installer le plugin](/docs/monitoring/pluginpacks/#installer-le-plugin). -### Comment puis-je tester le Plugin et que signifient les options des commandes ? +Utilisez les commandes ci-dessous en fonction du gestionnaire de paquets de votre système d'exploitation : -Une fois le Plugin installé, vous pouvez tester celui-ci directement en ligne de commande depuis votre collecteur Centreon avec l'utilisateur centreon-engine : + + ```bash -/usr/lib/centreon/plugins//centreon_vmware_connector_client.pl - --plugin=apps::vmware::connector::plugin - --mode=tools-vm - --custommode=connector - --connector-hostname='localhost' - --connector-port='5700' - --container='vcenter01' - --vm-hostname='SRV-LIN-TLS' - --filter-uuid='' - --tools-notinstalled-status='critical' - --tools-notrunning-status='critical' - --tools-notup2date-status='warning' +dnf install centreon-plugin-Virtualization-Vmware2-Connector-Plugin ``` -La commande retourne le message de sortie ci-dessous: + + ```bash -OK: VMTools are OK +dnf install centreon-plugin-Virtualization-Vmware2-Connector-Plugin ``` -Cette commande supervise le statut des VMTools (```--plugin=apps::vmware::connector::plugin --mode=tools-vm```) de la VM **SRV-LIN-TLS** (```--vm-hostname='SRV-LIN-TLS'```). -Le plugin se connecte au daemon VMWare sur **localhost** (```--connector-hostname='localhost'```) sur le port **5700** (```--connector-port='5700'```). -Puis la command requête le **container** **vcenter01** (```--container='vcenter01'```) parce que la VM **SRV-LIN-TLS** est managée par **vcenter01**. + + -La commande déclenchera : -* Une alarme WARNING si les VMTools ne sont pas à jour (```--tools-notup2date-status='warning'```) -* Une alarme CRITICAL si les VMTools ne sont pas démarrés ou installés (```--tools-notinstalled-status='critical' --tools-notrunning-status='critical'```) +```bash +apt install centreon-plugin-virtualization-vmware2-connector-plugin +``` -Vous pouvez afficher tous les modes disponibles à l'aide de la commande suivante :` + + ```bash -/usr/lib/centreon/plugins/./centreon_vmware_connector_client.pl \ - --plugin=apps::vmware::connector::plugin \ - --list-mode +yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin ``` -Pour chaque mode, les options disponibles peuvent être consultées en ajoutant l'option --help à la commande : + + + +## Utiliser le connecteur de supervision + +### Utiliser un modèle d'hôte issu du connecteur + +1. Ajoutez un hôte à Centreon depuis la page **Configuration > Hôtes**. +2. Complétez les champs **Nom**, **Alias** & **IP Address/DNS** correspondant à votre ressource. +3. Appliquez le modèle d'hôte **Virt-VMWare2-VM-custom**. Une liste de macros apparaît. Les macros vous permettent de définir comment le connecteur se connectera à la ressource, ainsi que de personnaliser le comportement du connecteur. +4. Renseignez les macros désirées. Attention, certaines macros sont obligatoires. + +| Macro | Description | Valeur par défaut | Obligatoire | +|:---------------------------|:------------------------------------------------------------------------------------------------------|:------------------|:-----------:| +| CENTREONVMWAREPORT | Connector port (default: 5700) | 5700 | | +| CENTREONVMWARECONTAINER | Container to use (it depends of the connector configuration) | default | | +| CENTREONVMWAREHOST | Connector hostname (required) | localhost |X | +| VMNAME | VM hostname to check. If not set, we check all VMs | | | +| VMUUID | Specify The VM UUID | | | +| CENTREONVMWAREEXTRAOPTIONS | Any extra option you may want to add to every command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | + +5. [Déployez la configuration](/docs/monitoring/monitoring-servers/deploying-a-configuration). L'hôte apparaît dans la liste des hôtes 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 de l'hôte : celle-ci montre les valeurs des macros. + +### Utiliser un modèle de service issu du connecteur + +1. Si vous avez utilisé un modèle d'hôte et coché la case **Créer aussi les services liés aux modèles**, les services associés au modèle ont été créés automatiquement, avec les modèles de services correspondants. Sinon, [créez les services désirés manuellement](/docs/monitoring/basic-objects/services) et appliquez-leur un modèle de service. +2. Renseignez les macros désirées (par exemple, ajustez les seuils d'alerte). Les macros indiquées ci-dessous comme requises (**Obligatoire**) doivent être renseignées. + + + + +| 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 | | +| 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} | | | +| WARNINGUSAGE | Warning threshold | 80 | | +| CRITICALUSAGE | Critical threshold | 90 | | +| WARNINGUSAGEMHZ | Warning threshold | | | +| CRITICALUSAGEMHZ | 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) | | | + + + + +| 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 | | +| 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} | | | +| 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 | | + + + + +| 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 | | +| 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} | | | +| 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) | | | + + + + +| 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} | | | +| 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 | | + + + + +| 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 | | +| WARNING | Warning threshold | | | +| CRITICAL | Critical threshold | | | +| WARNINGACTIVE | Warning threshold | | | +| CRITICALACTIVE | Critical threshold | | | +| WARNINGBALLOONING | Warning threshold | | | +| CRITICALBALLOONING | Critical threshold | | | +| WARNINGOVERHEAD | Warning threshold | | | +| 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} | | | +| 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) | | | + + + + +| Macro | Description | Valeur par défaut | Obligatoire | +|:-------------|:----------------------------------------------------------------------------------------------------|:------------------|:-----------:| +| WARNING | Warning threshold for snapshot's age | 259200 | | +| CRITICAL | Critical threshold for snapshot's age | 432000 | | +| 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) | | | + + + + +| 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} | | | +| 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 | | + + + + +| 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} | | | +| WARNINGSWAPIN | Warning threshold | | | +| CRITICALSWAPIN | Critical threshold | | | +| WARNINGSWAPOUT | Warning threshold | | | +| CRITICALSWAPOUT | 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) | | | + + + + +| Macro | Description | Valeur par défaut | Obligatoire | +|:-------------|:----------------------------------------------------------------------------------------------------|:------------------|:-----------:| +| STATUS | Thinprovisioning status (default: none) Example: 'active,CRITICAL' or 'notactive,WARNING' | active,WARNING | X | +| 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 | | + + + + +| Macro | Description | Valeur par défaut | Obligatoire | +|:-------------------|:----------------------------------------------------------------------------------------------------|:------------------|:-----------:| +| NOTINSTALLEDSTATUS | Status if vmtools is not installed (default: critical) | critical | X | +| NOTRUNNINGSTATUS | Status if vmtools is not running (default: critical) | critical | X | +| NOTUP2DATESTATUS | Status if vmtools is not upd2date (default: warning) | warning | | +| 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) | | | + + + + +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. + +## Comment puis-je tester le plugin et que signifient les options des commandes ? + +Une fois le plugin installé, vous pouvez tester celui-ci directement en ligne +de commande depuis votre collecteur Centreon en vous connectant avec +l'utilisateur **centreon-engine** (`su - centreon-engine`). Vous pouvez tester +que le connecteur arrive bien à superviser une ressource en utilisant une commande +telle que celle-ci (remplacez les valeurs d'exemple par les vôtres) : ```bash -/usr/lib/centreon/plugins/./centreon_vmware_connector_client.pl \ - --plugin=apps::vmware::connector::plugin \ - --mode=tools-vm \ - --help +/usr/lib/centreon/plugins/centreon_vmware_connector_client.pl \ + --plugin=apps::vmware::connector::plugin \ + --mode=swap-vm \ + --custommode=connector \ + --connector-hostname='localhost' \ + --connector-port='5700' \ + --container='default' \ + --vm-hostname='' \ + --filter-uuid='' \ + --unknown-status='%{connection_state} !~ /^connected$/i or %{power_state} !~ /^poweredOn$/i' \ + --warning-status='' \ + --critical-status='' \ + --warning-swap-in='' \ + --critical-swap-in='' \ + --warning-swap-out='' \ + --critical-swap-out='' ``` -### J'obtiens les erreurs suivantes : +La commande devrait retourner un message de sortie similaire à : -#### UNKNOWN: Unknown container name 'default' | +```bash +OK: All virtual machines are ok | '*vm*#vm.swap.in.usage.bytespersecond'=B/s;;;0;'*vm*#vm.swap.out.usage.bytespersecond'=B/s;;;0; +``` -Ce message d'erreur signifie que le **container* passé en argument n'existe pas dans la configuration du connecteur VMWare. -Vérifiez la macro **CENTREONVMWARECONTAINER** sur l'hôte ou vérifiez la configuration dans le fichier */etc/centreon/centreon_vmware.pm* +### Diagnostic des erreurs communes -#### UNKNOWN: Cannot get response (timeout received) +Rendez-vous sur la [documentation dédiée](../getting-started/how-to-guides/troubleshooting-plugins.md) +pour le diagnostic des erreurs communes des plugins Centreon. -Ce messsage d'erreur signifie que le plugin n'a pas eu de réponse du daemon VMWare. -Vérifiez vos paramètres de connexion et les macros **CENTREONVMWAREHOST** et **CENTREONVMWAREPORT**. +### Modes disponibles -#### UNKNOWN: Container connection problem | +Dans la plupart des cas, un mode correspond à un modèle de service. Le mode est renseigné dans la commande d'exécution +du connecteur. Dans l'interface de Centreon, il n'est pas nécessaire de les spécifier explicitement, leur utilisation est +implicite dès lors que vous utilisez un modèle de service. En revanche, vous devrez spécifier le mode correspondant à ce +modèle si vous voulez tester la commande d'exécution du connecteur dans votre terminal. -Ce message signifie que vous avez un problème avec les identifiants liés à votre **container**. -Vérifiez les identifiants dans le fichier */etc/centreon/centreon_vmware.pm*. -Vous pouvez aussi regarder les logs pour plus d'informations: */var/log/centreon/centreon_vmware.log* +Tous les modes disponibles peuvent être affichés en ajoutant le paramètre +`--list-mode` à la commande : -#### UNKNOWN: Cannot find 'VirtualMachine' object | +```bash +/usr/lib/centreon/plugins/centreon_vmware_connector_client.pl \ + --plugin=apps::vmware::connector::plugin \ + --list-mode +``` -Ce message d'erreur signifie que le plugin n'a pas trouvé la machine virtuelle. -Vérifiez le nom de la machine virtuelle dans la macro **HOSTVMNAME**, -This error message means that the Plugin didn't find the Virtual Machine. -Check the Virtual Machine name in the macro **HOSTVMNAME**, il doit correspondre au nom défini dans votre infrastructure VMWare. +Le plugin apporte les modes suivants : + +| Mode | Modèle de service associé | +|:---------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------| +| alarm-datacenter [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/alarmdatacenter.pm)] | Not used in this Monitoring Connector | +| alarm-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/alarmhost.pm)] | Not used in this Monitoring Connector | +| countvm-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/countvmhost.pm)] | Not used in this Monitoring Connector | +| cpu-cluster [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/cpucluster.pm)] | Not used in this Monitoring Connector | +| cpu-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/cpuhost.pm)] | Not used in this Monitoring Connector | +| cpu-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/cpuvm.pm)] | Virt-VMWare2-Vm-Cpu-Generic-custom | +| datastore-countvm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/datastorecountvm.pm)] | Not used in this Monitoring Connector | +| datastore-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/datastorehost.pm)] | Not used in this Monitoring Connector | +| datastore-io [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/datastoreio.pm)] | Not used in this Monitoring Connector | +| datastore-iops [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/datastoreiops.pm)] | Not used in this Monitoring Connector | +| datastore-snapshot [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/datastoresnapshot.pm)] | Not used in this Monitoring Connector | +| datastore-usage [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/datastoreusage.pm)] | Not used in this Monitoring Connector | +| datastore-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/datastorevm.pm)] | Virt-VMWare2-Vm-Datastores-Iops-Generic-custom | +| device-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/devicevm.pm)] | Virt-VMWare2-Vm-Device-Generic-custom | +| discovery [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/discovery.pm)] | Used for host discovery | +| getmap [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/getmap.pm)] | Not used in this Monitoring Connector | +| health-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/healthhost.pm)] | Not used in this Monitoring Connector | +| licenses [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/licenses.pm)] | Not used in this Monitoring Connector | +| limit-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/limitvm.pm)] | Virt-VMWare2-Vm-Limit-Generic-custom | +| list-clusters [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/listclusters.pm)] | Not used in this Monitoring Connector | +| list-datacenters [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/listdatacenters.pm)] | Not used in this Monitoring Connector | +| list-datastores [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/listdatastores.pm)] | Not used in this Monitoring Connector | +| list-nichost [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/listnichost.pm)] | Not used in this Monitoring Connector | +| maintenance-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/maintenancehost.pm)] | Not used in this Monitoring Connector | +| memory-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/memoryhost.pm)] | Not used in this Monitoring Connector | +| memory-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/memoryvm.pm)] | Virt-VMWare2-Vm-Memory-Generic-custom | +| net-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/nethost.pm)] | Not used in this Monitoring Connector | +| net-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/netvm.pm)] | Not used in this Monitoring Connector | +| service-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/servicehost.pm)] | Not used in this Monitoring Connector | +| snapshot-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/snapshotvm.pm)] | Virt-VMWare2-Vm-Snapshot-Generic-custom | +| stat-connectors [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/statconnectors.pm)] | Not used in this Monitoring Connector | +| status-cluster [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/statuscluster.pm)] | Not used in this Monitoring Connector | +| status-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/statushost.pm)] | Not used in this Monitoring Connector | +| status-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/statusvm.pm)] | Virt-VMWare2-Vm-Status-Generic-custom | +| storage-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/storagehost.pm)] | Not used in this Monitoring Connector | +| swap-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/swaphost.pm)] | Not used in this Monitoring Connector | +| swap-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/swapvm.pm)] | Virt-VMWare2-Vm-Swap-Generic-custom | +| thinprovisioning-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/thinprovisioningvm.pm)] | Virt-VMWare2-Vm-Thinprovisioning-Generic-custom | +| time-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/timehost.pm)] | Not used in this Monitoring Connector | +| tools-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/toolsvm.pm)] | Virt-VMWare2-Vm-Tools-Generic-custom | +| uptime-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/uptimehost.pm)] | Not used in this Monitoring Connector | +| vmoperation-cluster [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/vmoperationcluster.pm)] | Not used in this Monitoring Connector | +| vsan-cluster-usage [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/vsanclusterusage.pm)] | Not used in this Monitoring Connector | + +### Options disponibles + +#### Options génériques + +Les options génériques sont listées ci-dessous : + +| Option | Description | +|:-------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --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. | +| --mode-version | Check minimal version of mode. If not, unknown error. | +| --version | Return the version of the plugin. | +| --custommode | When a plugin offers several ways (CLI, library, etc.) to get information the desired one must be defined with this option. | +| --list-custommode | List all available custom modes. | +| --multiple | Multiple custom mode objects. This may be required by some specific modes (advanced). | +| --pass-manager | Define the password manager you want to use. Supported managers are: environment, file, keepass, hashicorpvault and teampass. | +| --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. | +| --explode-perfdata-max | 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)' | +| --change-short-output --change-long-output | Modify the short/long output that is returned by the plugin. Syntax: --change-short-output=pattern~replacement~modifier Most commonly used modifiers are i (case insensitive) and g (replace all occurrences). Eg: adding --change-short-output='OK~Up~gi' will replace all occurrences of 'OK', 'ok', 'Ok' or 'oK' with 'Up' | +| --change-exit | Replace an exit code with one of your choice. Eg: adding --change-exit=unknown=critical will result in a CRITICAL state instead of an UNKNOWN state. | +| --range-perfdata | Rewrite the ranges displayed in the perfdata. Accepted values: 0: nothing is changed. 1: if the lower value of the range is equal to 0, it is removed. 2: remove the thresholds from the perfdata. | +| --filter-uom | Mask the units when they don't match the given regular expression. | +| --opt-exit | Replace the exit code in case of an execution error (i.e. wrong option provided, SSH connection refused, timeout, etc). Default: unknown. | +| --output-ignore-perfdata | Remove all the metrics from the service. The service will still have a status and an output. | +| --output-ignore-label | Remove the status label ("OK:", "WARNING:", "UNKNOWN:", CRITICAL:") from the beginning of the output. Eg: 'OK: Ram Total:...' will become 'Ram Total:...' | +| --output-xml | Return the output in XML format (to send to an XML API). | +| --output-json | Return the output in JSON format (to send to a JSON API). | +| --output-openmetrics | Return the output in OpenMetrics format (to send to a tool expecting this format). | +| --output-file | Write output in file (can be combined with json, xml and openmetrics options). E.g.: --output-file=/tmp/output.txt will write the output in /tmp/output.txt. | +| --disco-format | Applies only to modes beginning with 'list-'. Returns the list of available macros to configure a service discovery rule (formatted in XML). | +| --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'. | +| --connector-hostname | Connector hostname (required). | +| --connector-port | Connector port (default: 5700). | +| --container | Container to use (it depends of the connector configuration). | +| --vsphere-address | Address of vpshere/ESX to connect. | +| --vsphere-username | Username of vpshere/ESX connection (with --vsphere-address). | +| --vsphere-password | Password of vpshere/ESX connection (with --vsphere-address). | +| --timeout | Set global execution timeout (Default: 50) | +| --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}. | + +#### Options des modes + +Les options disponibles pour chaque modèle de services sont listées ci-dessous : + + + + +| Option | Description | +|:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. Exemple : --vm-hostname='^((VM-PROD-*))' --filter | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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} | +| --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'. | + + + + +| Option | Description | +|:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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). | +| --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} | +| --warning-* --critical-* | Thresholds. Can be: 'max-total-latency', 'read', 'write'. | + + + + +| Option | Description | +|:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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). | +| --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} | +| --warning-* | Warning threshold. Can be: 'total-device-connected', 'device-connected'. | +| --critical-* | Critical threshold. Can be: 'total-device-connected', 'device-connected'. | + + + + +| Option | Description | +|:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --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} | + + + + +| Option | Description | +|:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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). | +| --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} | +| --units | Units of thresholds (Default: '%') ('%', 'B'). | +| --free | Thresholds are on free space left. | +| --warning-* | Warning threshold. Can be: 'consumed', 'active', 'overhead', 'ballooning', 'shared'. | +| --critical-* | Critical threshold. Can be: 'consumed', 'active', 'overhead', 'ballooning', 'shared'. | + + + + +| Option | Description | +|:----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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). | +| --display-description | Display virtual machine description. | +| --check-consolidation | Check if VM needs consolidation (since vsphere 5.0). | +| --disconnect-status | Status if VM disconnected (default: 'unknown'). | +| --nopoweredon-skip | Skip check if VM is not poweredOn. | +| --empty-continue | Ask to the connector that an empty response is ok. | +| --unit | Select the unit for 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 | Warning threshold for snapshot's age. | +| --critical | Critical threshold for snapshot's age. | + + + + +| Option | Description | +|:--------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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} | + + + + +| Option | Description | +|:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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). | +| --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} | +| --warning-* | Warning threshold. Can be: 'swap-in', 'swap-out'. | +| --critical-* | Critical threshold. Can be: 'swap-in', 'swap-out'. | + + + + +| Option | Description | +|:--------------------------|:---------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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). | +| --disconnect-status | Status if VM disconnected (default: 'unknown'). | +| --nopoweredon-skip | Skip check if VM is not poweredOn. | +| --display-description | Display virtual machine description. | +| --thinprovisioning-status | Thinprovisioning status (default: none) Example: 'active,CRITICAL' or 'notactive,WARNING' | + + + + +| Option | Description | +|:----------------------------|:--------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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). | +| --disconnect-status | Status if VM disconnected (default: 'unknown'). | +| --nopoweredon-skip | Skip check if VM is not poweredOn. | +| --empty-continue | Ask to the connector that an empty response is ok. | +| --display-description | Display virtual machine description. | +| --tools-notinstalled-status | Status if vmtools is not installed (default: critical). | +| --tools-notrunning-status | Status if vmtools is not running (default: critical). | +| --tools-notup2date-status | Status if vmtools is not upd2date (default: warning). | + + + + +Pour un mode, la liste de toutes les options disponibles et leur signification peut être +affichée en ajoutant le paramètre `--help` à la commande : + +```bash +/usr/lib/centreon/plugins/centreon_vmware_connector_client.pl \ + --plugin=apps::vmware::connector::plugin \ + --mode=swap-vm \ + --help +``` diff --git a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md index 934d17938fa6..9e21be1e9e83 100644 --- a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md +++ b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md @@ -5,76 +5,164 @@ title: VMware VM import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -## Overview +## Pack assets -VMware is an software compagny based in USA. VMware provides cloud computing and virtualization software and services. +### Templates -The Centreon Plugin and Monitoring Connectors rely on the Centreon VMWare Connector to request the vCenter SDK. +The Monitoring Connector **VMware VM** brings a host template: -## Monitoring Connector Assets +* **Virt-VMWare2-VM-custom** -### Monitored Objects +The connector brings the following service templates (sorted by the host template they are attached to): -* Virtual Machine + + -### Discovery Rules +| Service Alias | Service Template | Service Description | +|:--------------------|:------------------------------------------------|:------------------------------------------------------------------------| +| Vm-Limit | Virt-VMWare2-Vm-Limit-Generic-custom | Check limit definition | +| Vm-Snapshot | Virt-VMWare2-Vm-Snapshot-Generic-custom | Check snapshot age of a virtual machine | +| Vm-Status | Virt-VMWare2-Vm-Status-Generic-custom | Check global status of a virtual machine | +| Vm-Thinprovisioning | Virt-VMWare2-Vm-Thinprovisioning-Generic-custom | Check if a virtual machine has a disk in mode 'thinprovisioning' or not | +| Vm-Tools | Virt-VMWare2-Vm-Tools-Generic-custom | Check vmtools state of a virtual machine | - - +> The services listed above are created automatically when the **Virt-VMWare2-VM-custom** host template is used. + + + + +| Service Alias | Service Template | Service Description | +|:-------------------|:-----------------------------------------------|:------------------------------------------------------| +| Vm-Cpu | Virt-VMWare2-Vm-Cpu-Generic-custom | Check CPU usage of a virtual machine | +| Vm-Datastores-Iops | Virt-VMWare2-Vm-Datastores-Iops-Generic-custom | Check datastores IOPS linked to the virtual machine. | +| Vm-Device | Virt-VMWare2-Vm-Device-Generic-custom | Check CPU usage of a virtual machine | +| Vm-Memory | Virt-VMWare2-Vm-Memory-Generic-custom | Check memory usage of a virtual machine | +| Vm-Swap | Virt-VMWare2-Vm-Swap-Generic-custom | Check if a virtual machine is swapping | -| Rule name | Description | -| :----------------------------- | :------------------------------------------ | -| Virt-VMWare2-VM-HostDiscovery | Discover the VMs bound to a vCenter or ESXi | +> The services listed above are not created automatically when a host template is applied. To use them, [create a service manually](/docs/monitoring/basic-objects/services), then apply the service template you want. -### Collected Metrics +### Discovery rules -In addition to modes and metrics described here, it is also possible to monitor the following indicators: +#### Host discovery -* VM-Cpu: Advanced monitoring of the CPU (CPU ready) -* VM-Datastores-Iops: VM Iops usage on the Datastore -* VM-Swap: VM swap usage -* VM-Device: Check VM's devices status (e.g. VirtualCdrom) +| Rule name | Description | +|:----------------|:--------------------------------| +| VMWare VM | Discover VMWare Virtual Machine | + +More information about discovering hosts automatically is available on the [dedicated page](/docs/monitoring/discovery/hosts-discovery). + +### Collected metrics & status + +Here is the list of services for this connector, detailing all metrics linked to each service. - + -| Metric name | Description | Unit | -| :---------- | :------------------------------------------------------------- | :--- | -| status | Status of the VMware Tools (installed, running and up-to-date) | | +| Metric name | Unit | +|:----------------------------------------------|:------| +| *vm*~status | N/A | +| *vm*~vm.cpu.utilization.percentage | % | +| *vm*~vm.cpu.utilization.mhz | MHz | +| *vm*~vm.cpu.ready.percentage | % | +| *vm*~*cpu*#vm.core.cpu.utilization.percentage | MHz | + +> To obtain this new metric format, include **--use-new-perfdata** in the **EXTRAOPTIONS** service macro. - + + +| Metric name | Unit | +|:-----------------------------------------------|:------| +| *vm*~status | N/A | +| *vm*~vm.datastore.latency.max.milliseconds | ms | +| *vm*~*datastore*#vm.datastore.read.usage.iops | iops | +| *vm*~*datastore*#vm.datastore.write.usage.iops | iops | -| Metric name | Description | Unit | -| :---------- | :----------------------------------------- | :--- | -| status | Status of the Thinprovisoning virtualdisks | | +> To obtain this new metric format, include **--use-new-perfdata** in the **EXTRAOPTIONS** service macro. - + + +| Metric name | Unit | +|:--------------------------------|:------| +| vm.devices.connected.count | count | +| *vm*#status | N/A | +| *vm*#vm.devices.connected.count | count | + +> To obtain this new metric format, include **--use-new-perfdata** in the **EXTRAOPTIONS** service macro. + + + -| Metric name | Description | Unit | -| :------------ | :----------------------- | :--- | -| status | Overall status of the VM | | +| Metric name | Unit | +|:--------------|:------| +| cpu-status | N/A | +| memory-status | N/A | +| disk-status | N/A | + +> To obtain this new metric format, include **--use-new-perfdata** in the **EXTRAOPTIONS** service macro. + + + + +| Metric name | Unit | +|:------------------------------------|:------| +| *vm*~status | N/A | +| *vm*~vm.memory.consumed.usage.bytes | B | +| *vm*~vm.memory.active.usage.bytes | B | +| *vm*~vm.memory.overhead.bytes | B | +| *vm*~vm.memory.ballooning.bytes | B | +| *vm*~vm.memory.shared.bytes | B | + +> To obtain this new metric format, include **--use-new-perfdata** in the **EXTRAOPTIONS** service macro. -| Metric name | Description | Unit | -| :---------------------------------- | :------------------------------------------------------------ | :---- | -| vm.snapshots.warning.current.count | Number of VM's snapshot older than 3 days (default threshold) | Count | -| vm.snapshots.critical.current.count | Number of VM's snapshot older than 5 days (default threshold) | Count | +| Metric name | Unit | +|:------------------------------------|:------| +| vm.snapshots.warning.current.count | count | +| vm.snapshots.critical.current.count | count | - + + +| Metric name | Unit | +|:--------------------|:------| +| *vm*#status | N/A | +| *vm*#overall-status | N/A | + +> To obtain this new metric format, include **--use-new-perfdata** in the **EXTRAOPTIONS** service macro. + + + + +| Metric name | Unit | +|:--------------------------------------|:------| +| *vm*#status | N/A | +| *vm*#vm.swap.in.usage.bytespersecond | B/s | +| *vm*#vm.swap.out.usage.bytespersecond | B/s | + +> To obtain this new metric format, include **--use-new-perfdata** in the **EXTRAOPTIONS** service macro. + + + + +| Metric name | Description | Unit | +|:------------|:-------------------------------------------|:------| +| status | Status of the Thinprovisoning virtualdisks | | + + + -| Metric name | Description | Unit | -| :--------------------------- | :--------------------- | :---- | -| vm.limit.cpu.alerts.count | Alerts on CPU limit | Count | -| vm.limit.memory.alerts.count | Alerts on Memory limit | Count | -| vm.limit.disk.alerts.count | Alerts on Disk limit | Count | +| Metric name | Unit | +|:------------------------------------|:------| +| vm.tools.notupdated.current.count | count | +| vm.tools.notrunning.current.count | count | +| vm.tools.notinstalled.current.count | count | @@ -153,7 +241,7 @@ Make sure that the daemon configuration works fine by looking for errors in ### Tags and Custom Attributes -To discover Tags and Custom Attributes, you must : +To discover Tags and Custom Attributes, you must : * use version **3.2.5** of **centreon-vmware-daemon** * add **--tags** in the additional discovery options: go to the **Configuration > Hosts > Discovery** page, and to the 3rd step (**Set discovery parameters**), in the section **Additional parameters**, in the **Additional options** field, type **--tags**. @@ -164,124 +252,618 @@ The Poller with the Centreon VMware Connector installed need to access in TCP/44 The Pollers that request the Centreon VMWare Connector host need to access in TCP/5700 to the Centreon VMWare Connector host. -## Installation +## Installing the monitoring connector - - +### Pack -1. Install the Vmware2 Connector Centreon Plugin on every poller expected to monitor the devices: +1. If the platform uses an *online* license, you can skip the package installation +instruction below as it is not required to have the connector displayed within the +**Configuration > Monitoring Connectors Manager** menu. +If the platform uses an *offline* license, install the package on the **central server** +with the command corresponding to the operating system's package manager: + + + ```bash -yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin +dnf install centreon-pack-virtualization-vmware2-vm ``` -2. Install the 'Vmware VM' Centreon Monitoring Connector on the **Configuration > Monitoring Connector Manager** page - - + + +```bash +dnf install centreon-pack-virtualization-vmware2-vm +``` -1. Install the Vmware VM Centreon Plugin on every poller expected to monitor the devices: + + ```bash -yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin +apt install centreon-pack-virtualization-vmware2-vm ``` -2. Install the Centreon Monitoring Connector RPM: + + ```bash yum install centreon-pack-virtualization-vmware2-vm ``` -3. Install the 'Vmware VM' Centreon Monitoring Connector on the **Configuration > Monitoring Connector Manager** page - -## Configuration +2. Whatever the license type (*online* or *offline*), install the **VMware VM** connector through +the **Configuration > Monitoring Connectors Manager** menu. + +### Plugin + +Since Centreon 22.04, you can benefit from the 'Automatic plugin installation' feature. +When this feature is enabled, you can skip the installation part below. + +You still have to manually install the plugin on the poller(s) when: +- Automatic plugin installation is turned off +- You want to run a discovery job from a poller that doesn't monitor any resource of this kind yet + +> More information in the [Installing the plugin](/docs/monitoring/pluginpacks/#installing-the-plugin) section. -* Log into Centreon and add a new Host through "Configuration > Hosts". -* Apply the relevant Host Template "VVirt-VMWare2-Vm-custom", and configure the mandatory Macros: +Use the commands below according to your operating system's package manager: -| Mandatory | Name | Description | -| :---------- | :------------------------- | :----------------------------------------------------- | -| X | CENTREONVMWARECONTAINER | Name of your container in the file centreon_vmware.pm | -| X | CENTREONVMWAREHOST | The Centreon server that launches the connection | -| X | CENTREONVMWAREPORT | By default: 5700 | -| X | VMNAME | Name of the VM (defined in your VMWare infrastructure) | -| | VMUUID | Specify The VM UUID | -| | VMWAREEXTRAOPTIONS | Customize it with your own if needed | + + -## FAQ +```bash +dnf install centreon-plugin-Virtualization-Vmware2-Connector-Plugin +``` -### How do I run my plugin through the CLI and what do the main parameters stand for ? + + -Once you've installed the plugin, you can test it logging with centreon-engine user: +```bash +dnf install centreon-plugin-Virtualization-Vmware2-Connector-Plugin +``` + + + ```bash -/usr/lib/centreon/plugins//centreon_vmware_connector_client.pl - --plugin=apps::vmware::connector::plugin - --mode=tools-vm - --custommode=connector - --connector-hostname='localhost' - --connector-port='5700' - --container='vcenter01' - --vm-hostname='SRV-LIN-TLS' - --filter-uuid='' - --tools-notinstalled-status='critical' - --tools-notrunning-status='critical' - --tools-notup2date-status='warning' +apt install centreon-plugin-virtualization-vmware2-connector-plugin ``` -Expected command output is shown below: + + ```bash -OK: VMTools are OK +yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin ``` -This command above checks the status of the VMTools (```--plugin=apps::vmware::connector::plugin --mode=tools-vm```) of the VM **SRV-LIN-TLS** (```--vm-hostname='SRV-LIN-TLS'```). -It connects to the VMWare daemon on **localhost** (```--connector-hostname='localhost'```) on the port **5700** (```--connector-port='5700'```). -Then the command requests the container **vcenter01** (```--container='vcenter01'```) because the VM **SRV-LIN-TLS** is managed by **vcenter01**. + + + +## Using the monitoring connector + +### Using a host template provided by the connector + +1. Log into Centreon and add a new host through **Configuration > Hosts**. +2. Fill the **Name**, **Alias** & **IP Address/DNS** fields according to your ressource settings. +3. Apply the **Virt-VMWare2-VM-custom** template to the host. A list of macros appears. Macros allow you to define how the connector will connect to the resource, and to customize the connector's behavior. +4. Fill in the macros you want. Some macros are mandatory. + +| Macro | Description | Default value | Mandatory | +|:---------------------------|:------------------------------------------------------------------------------------------------------|:------------------|:-----------:| +| CENTREONVMWAREPORT | Connector port (default: 5700) | 5700 | | +| CENTREONVMWARECONTAINER | Container to use (it depends of the connector configuration) | default | | +| CENTREONVMWAREHOST | Connector hostname (required) | localhost | X | +| VMNAME | VM hostname to check. If not set, we check all VMs | | | +| VMUUID | Specify The VM UUID | | | +| CENTREONVMWAREEXTRAOPTIONS | Any extra option you may want to add to every command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | + +5. [Deploy the configuration](/docs/monitoring/monitoring-servers/deploying-a-configuration). The host appears in the list of hosts, and on the **Resources Status** page. The command that is sent by the connector is displayed in the details panel of the host: it shows the values of the macros. + +### Using a service template provided by the connector -It will trigger : -* WARNING alarm if the VMTools are not up-to-date (```--tools-notup2date-status='warning'```) -* CRITICAL alarm if the VMTools are not running or installed (```--tools-notinstalled-status='critical' --tools-notrunning-status='critical'```) +1. If you have used a host template and checked **Create Services linked to the Template too**, the services linked to the template have been created automatically, using the corresponding service templates. Otherwise, [create manually the services you want](/docs/monitoring/basic-objects/services) and apply a service template to them. +2. Fill in the macros you want (e.g. to change the thresholds for the alerts). Some macros are mandatory (see the table below). -All available modes with the plugin can be displayed with: + + + +| 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 | | +| 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} | | | +| WARNINGUSAGE | Warning threshold | 80 | | +| CRITICALUSAGE | Critical threshold | 90 | | +| WARNINGUSAGEMHZ | Warning threshold | | | +| CRITICALUSAGEMHZ | 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) | | | + + + + +| 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 | | +| 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} | | | +| 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 | | + + + + +| 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 | | +| 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} | | | +| 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) | | | + + + + +| 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} | | | +| 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 | | + + + + +| 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 | | +| WARNING | Warning threshold | | | +| CRITICAL | Critical threshold | | | +| WARNINGACTIVE | Warning threshold | | | +| CRITICALACTIVE | Critical threshold | | | +| WARNINGBALLOONING | Warning threshold | | | +| CRITICALBALLOONING | Critical threshold | | | +| WARNINGOVERHEAD | Warning threshold | | | +| 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} | | | +| EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | + + + + +| Macro | Description | Default value | Mandatory | +|:-------------|:----------------------------------------------------------------------------------------------------|:------------------|:-----------:| +| WARNING | Warning threshold for snapshot's age | 259200 | | +| CRITICAL | Critical threshold for snapshot's age | 432000 | | +| EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | + + + + +| 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} | | | +| 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 | | + + + + +| 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} | | | +| WARNINGSWAPIN | Warning threshold | | | +| CRITICALSWAPIN | Critical threshold | | | +| WARNINGSWAPOUT | Warning threshold | | | +| CRITICALSWAPOUT | 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) | | | + + + + +| Macro | Description | Default value | Mandatory | +|:-------------|:----------------------------------------------------------------------------------------------------|:------------------|:-----------:| +| STATUS | Thinprovisioning status (default: none) Example: 'active,CRITICAL' or 'notactive,WARNING' | active,WARNING | X | +| 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 | | + + + + +| Macro | Description | Default value | Mandatory | +|:-------------------|:----------------------------------------------------------------------------------------------------|:------------------|:-----------:| +| NOTINSTALLEDSTATUS | Status if vmtools is not installed (default: critical) | critical | X | +| NOTRUNNINGSTATUS | Status if vmtools is not running (default: critical) | critical | X | +| NOTUP2DATESTATUS | Status if vmtools is not upd2date (default: warning) | warning | | +| EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | + + + + +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. + +## How to check in the CLI that the configuration is OK and what are the main options for? + +Once the plugin is installed, log into your Centreon poller's CLI using the +**centreon-engine** user account (`su - centreon-engine`). Test that the connector +is able to monitor a resource using a command like this one (replace the sample values by yours): + +```bash +/usr/lib/centreon/plugins/centreon_vmware_connector_client.pl \ + --plugin=apps::vmware::connector::plugin \ + --mode=swap-vm \ + --custommode=connector \ + --connector-hostname='localhost' \ + --connector-port='5700' \ + --container='default' \ + --vm-hostname='' \ + --filter-uuid='' \ + --unknown-status='%{connection_state} !~ /^connected$/i or %{power_state} !~ /^poweredOn$/i' \ + --warning-status='' \ + --critical-status='' \ + --warning-swap-in='' \ + --critical-swap-in='' \ + --warning-swap-out='' \ + --critical-swap-out='' +``` + +The expected command output is shown below: ```bash -/usr/lib/centreon/plugins/./centreon_vmware_connector_client.pl \ - --plugin=apps::vmware::connector::plugin \ - --list-mode +OK: All virtual machines are ok | '*vm*#vm.swap.in.usage.bytespersecond'=B/s;;;0;'*vm*#vm.swap.out.usage.bytespersecond'=B/s;;;0; ``` -The available options for a mode can be displayed using the ```--help``` parameter: +### Troubleshooting + +Please find the [troubleshooting documentation](../getting-started/how-to-guides/troubleshooting-plugins.md) +for Centreon Plugins typical issues. + +### Available modes + +In most cases, a mode corresponds to a service template. The mode appears in the execution command for the connector. +In the Centreon interface, you don't need to specify a mode explicitly: its use is implied when you apply a service template. +However, you will need to specify the correct mode for the template if you want to test the execution command for the +connector in your terminal. + +All available modes can be displayed by adding the `--list-mode` parameter to +the command: ```bash -/usr/lib/centreon/plugins/./centreon_vmware_connector_client.pl \ - --plugin=apps::vmware::connector::plugin \ - --mode=tools-vm \ - --help +/usr/lib/centreon/plugins/centreon_vmware_connector_client.pl \ + --plugin=apps::vmware::connector::plugin \ + --list-mode ``` -### Why do I get the following error: +The plugin brings the following modes: + +| Mode | Linked service template | +|:---------------------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------| +| alarm-datacenter [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/alarmdatacenter.pm)] | Not used in this Monitoring Connector | +| alarm-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/alarmhost.pm)] | Not used in this Monitoring Connector | +| countvm-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/countvmhost.pm)] | Not used in this Monitoring Connector | +| cpu-cluster [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/cpucluster.pm)] | Not used in this Monitoring Connector | +| cpu-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/cpuhost.pm)] | Not used in this Monitoring Connector | +| cpu-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/cpuvm.pm)] | Virt-VMWare2-Vm-Cpu-Generic-custom | +| datastore-countvm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/datastorecountvm.pm)] | Not used in this Monitoring Connector | +| datastore-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/datastorehost.pm)] | Not used in this Monitoring Connector | +| datastore-io [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/datastoreio.pm)] | Not used in this Monitoring Connector | +| datastore-iops [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/datastoreiops.pm)] | Not used in this Monitoring Connector | +| datastore-snapshot [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/datastoresnapshot.pm)] | Not used in this Monitoring Connector | +| datastore-usage [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/datastoreusage.pm)] | Not used in this Monitoring Connector | +| datastore-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/datastorevm.pm)] | Virt-VMWare2-Vm-Datastores-Iops-Generic-custom | +| device-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/devicevm.pm)] | Virt-VMWare2-Vm-Device-Generic-custom | +| discovery [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/discovery.pm)] | Used for host discovery | +| getmap [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/getmap.pm)] | Not used in this Monitoring Connector | +| health-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/healthhost.pm)] | Not used in this Monitoring Connector | +| licenses [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/licenses.pm)] | Not used in this Monitoring Connector | +| limit-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/limitvm.pm)] | Virt-VMWare2-Vm-Limit-Generic-custom | +| list-clusters [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/listclusters.pm)] | Not used in this Monitoring Connector | +| list-datacenters [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/listdatacenters.pm)] | Not used in this Monitoring Connector | +| list-datastores [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/listdatastores.pm)] | Not used in this Monitoring Connector | +| list-nichost [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/listnichost.pm)] | Not used in this Monitoring Connector | +| maintenance-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/maintenancehost.pm)] | Not used in this Monitoring Connector | +| memory-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/memoryhost.pm)] | Not used in this Monitoring Connector | +| memory-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/memoryvm.pm)] | Virt-VMWare2-Vm-Memory-Generic-custom | +| net-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/nethost.pm)] | Not used in this Monitoring Connector | +| net-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/netvm.pm)] | Not used in this Monitoring Connector | +| service-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/servicehost.pm)] | Not used in this Monitoring Connector | +| snapshot-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/snapshotvm.pm)] | Virt-VMWare2-Vm-Snapshot-Generic-custom | +| stat-connectors [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/statconnectors.pm)] | Not used in this Monitoring Connector | +| status-cluster [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/statuscluster.pm)] | Not used in this Monitoring Connector | +| status-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/statushost.pm)] | Not used in this Monitoring Connector | +| status-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/statusvm.pm)] | Virt-VMWare2-Vm-Status-Generic-custom | +| storage-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/storagehost.pm)] | Not used in this Monitoring Connector | +| swap-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/swaphost.pm)] | Not used in this Monitoring Connector | +| swap-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/swapvm.pm)] | Virt-VMWare2-Vm-Swap-Generic-custom | +| thinprovisioning-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/thinprovisioningvm.pm)] | Virt-VMWare2-Vm-Thinprovisioning-Generic-custom | +| time-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/timehost.pm)] | Not used in this Monitoring Connector | +| tools-vm [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/toolsvm.pm)] | Virt-VMWare2-Vm-Tools-Generic-custom | +| uptime-host [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/uptimehost.pm)] | Not used in this Monitoring Connector | +| vmoperation-cluster [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/vmoperationcluster.pm)] | Not used in this Monitoring Connector | +| vsan-cluster-usage [[code](https://github.com/centreon/centreon-plugins/blob/develop/src/apps/vmware/connector/mode/vsanclusterusage.pm)] | Not used in this Monitoring Connector | + +### Available options + +#### Generic options + +All generic options are listed here: + +| Option | Description | +|:-------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --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. | +| --mode-version | Check minimal version of mode. If not, unknown error. | +| --version | Return the version of the plugin. | +| --custommode | When a plugin offers several ways (CLI, library, etc.) to get information the desired one must be defined with this option. | +| --list-custommode | List all available custom modes. | +| --multiple | Multiple custom mode objects. This may be required by some specific modes (advanced). | +| --pass-manager | Define the password manager you want to use. Supported managers are: environment, file, keepass, hashicorpvault and teampass. | +| --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. | +| --explode-perfdata-max | 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)' | +| --change-short-output --change-long-output | Modify the short/long output that is returned by the plugin. Syntax: --change-short-output=pattern~replacement~modifier Most commonly used modifiers are i (case insensitive) and g (replace all occurrences). Eg: adding --change-short-output='OK~Up~gi' will replace all occurrences of 'OK', 'ok', 'Ok' or 'oK' with 'Up' | +| --change-exit | Replace an exit code with one of your choice. Eg: adding --change-exit=unknown=critical will result in a CRITICAL state instead of an UNKNOWN state. | +| --range-perfdata | Rewrite the ranges displayed in the perfdata. Accepted values: 0: nothing is changed. 1: if the lower value of the range is equal to 0, it is removed. 2: remove the thresholds from the perfdata. | +| --filter-uom | Mask the units when they don't match the given regular expression. | +| --opt-exit | Replace the exit code in case of an execution error (i.e. wrong option provided, SSH connection refused, timeout, etc). Default: unknown. | +| --output-ignore-perfdata | Remove all the metrics from the service. The service will still have a status and an output. | +| --output-ignore-label | Remove the status label ("OK:", "WARNING:", "UNKNOWN:", CRITICAL:") from the beginning of the output. Eg: 'OK: Ram Total:...' will become 'Ram Total:...' | +| --output-xml | Return the output in XML format (to send to an XML API). | +| --output-json | Return the output in JSON format (to send to a JSON API). | +| --output-openmetrics | Return the output in OpenMetrics format (to send to a tool expecting this format). | +| --output-file | Write output in file (can be combined with json, xml and openmetrics options). E.g.: --output-file=/tmp/output.txt will write the output in /tmp/output.txt. | +| --disco-format | Applies only to modes beginning with 'list-'. Returns the list of available macros to configure a service discovery rule (formatted in XML). | +| --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'. | +| --connector-hostname | Connector hostname (required). | +| --connector-port | Connector port (default: 5700). | +| --container | Container to use (it depends of the connector configuration). | +| --vsphere-address | Address of vpshere/ESX to connect. | +| --vsphere-username | Username of vpshere/ESX connection (with --vsphere-address). | +| --vsphere-password | Password of vpshere/ESX connection (with --vsphere-address). | +| --timeout | Set global execution timeout (Default: 50) | +| --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}. | + +#### Modes options + +All available options for each service template are listed below: + + + + +| Option | Description | +|:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. Exemple : --vm-hostname='^((VM-PROD-*))' --filter | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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} | +| --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'. | + + + + +| Option | Description | +|:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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). | +| --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} | +| --warning-* --critical-* | Thresholds. Can be: 'max-total-latency', 'read', 'write'. | + + + + +| Option | Description | +|:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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). | +| --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} | +| --warning-* | Warning threshold. Can be: 'total-device-connected', 'device-connected'. | +| --critical-* | Critical threshold. Can be: 'total-device-connected', 'device-connected'. | + + + + +| Option | Description | +|:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --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} | + + + + +| Option | Description | +|:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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). | +| --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} | +| --units | Units of thresholds (Default: '%') ('%', 'B'). | +| --free | Thresholds are on free space left. | +| --warning-* | Warning threshold. Can be: 'consumed', 'active', 'overhead', 'ballooning', 'shared'. | +| --critical-* | Critical threshold. Can be: 'consumed', 'active', 'overhead', 'ballooning', 'shared'. | + + + + +| Option | Description | +|:----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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). | +| --display-description | Display virtual machine description. | +| --check-consolidation | Check if VM needs consolidation (since vsphere 5.0). | +| --disconnect-status | Status if VM disconnected (default: 'unknown'). | +| --nopoweredon-skip | Skip check if VM is not poweredOn. | +| --empty-continue | Ask to the connector that an empty response is ok. | +| --unit | Select the unit for 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 | Warning threshold for snapshot's age. | +| --critical | Critical threshold for snapshot's age. | + + + + +| Option | Description | +|:--------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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: Unknown container name 'default' | + + + +| Option | Description | +|:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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). | +| --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} | +| --warning-* | Warning threshold. Can be: 'swap-in', 'swap-out'. | +| --critical-* | Critical threshold. Can be: 'swap-in', 'swap-out'. | -This error message means that the container invoked in the command doesn't exist in your VMWare connector configuration. -Check your macro **CENTREONVMWARECONTAINER** on your host or check the file */etc/centreon/centreon_vmware.pm* + + -#### UNKNOWN: Cannot get response (timeout received) +| Option | Description | +|:--------------------------|:---------------------------------------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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). | +| --disconnect-status | Status if VM disconnected (default: 'unknown'). | +| --nopoweredon-skip | Skip check if VM is not poweredOn. | +| --display-description | Display virtual machine description. | +| --thinprovisioning-status | Thinprovisioning status (default: none) Example: 'active,CRITICAL' or 'notactive,WARNING' | -This error message means that the Plugin didn't get a response off the VMWare Daemon. -Check your connection parameters and the macros **CENTREONVMWAREHOST** and **CENTREONVMWAREPORT**. + + -#### UNKNOWN: Container connection problem | +| Option | Description | +|:----------------------------|:--------------------------------------------------------------| +| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --filter | VM hostname is a regexp. | +| --filter-description | Filter also virtual machines description (can be a regexp). | +| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --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). | +| --disconnect-status | Status if VM disconnected (default: 'unknown'). | +| --nopoweredon-skip | Skip check if VM is not poweredOn. | +| --empty-continue | Ask to the connector that an empty response is ok. | +| --display-description | Display virtual machine description. | +| --tools-notinstalled-status | Status if vmtools is not installed (default: critical). | +| --tools-notrunning-status | Status if vmtools is not running (default: critical). | +| --tools-notup2date-status | Status if vmtools is not upd2date (default: warning). | -This error message means that you have a issue with the credentials provided for your Container. -Check your credentials in */etc/centreon/centreon_vmware.pm*. -You can also take a look into the log for more information: */var/log/centreon/centreon_vmware.log* + + -#### UNKNOWN: Cannot find 'VirtualMachine' object | +All available options for a given mode can be displayed by adding the +`--help` parameter to the command: -This error message means that the Plugin didn't find the Virtual Machine. -Check the Virtual Machine name in the macro **HOSTVMNAME**, it's must fit the name defined in your VMWare infrastructure. +```bash +/usr/lib/centreon/plugins/centreon_vmware_connector_client.pl \ + --plugin=apps::vmware::connector::plugin \ + --mode=swap-vm \ + --help +``` From 18d751ba74f2d877685e0e088a3859e2985e1ba4 Mon Sep 17 00:00:00 2001 From: YanMeddour <83709929+YanMeddour@users.noreply.github.com> Date: Tue, 26 Dec 2023 15:09:34 +0100 Subject: [PATCH 02/14] add "Vue d'ensemble" part --- .../procedures/virtualization-vmware2-vm.md | 38 +++++++++++-------- 1 file changed, 22 insertions(+), 16 deletions(-) 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 4bc851f6d662..80b136cbb011 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 @@ -5,6 +5,12 @@ title: VMware VM import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +## Vue d'ensemble + +VMWare est une solution de Virtualisation et d'infrastructure de Cloud Computing. + +Le connecteur de supervision Centreon s'appuie sur le SDK VMWare pour requêter l'API du vCenter au travers d'un connecteur dédié. + ## Contenu du pack ### Modèles @@ -21,11 +27,11 @@ Le connecteur apporte les modèles de service suivants | Alias | Modèle de service | Description | |:--------------------|:------------------------------------------------|:-------------------------------------------------------------------------------------------------------------| -| Vm-Limit | Virt-VMWare2-Vm-Limit-Generic-custom | Contrôle permettant de vérifier la définition de limites | -| Vm-Snapshot | Virt-VMWare2-Vm-Snapshot-Generic-custom | Contrôle permettant de vérifier l'âge des snapshosts sur la machine virtuelle | -| Vm-Status | Virt-VMWare2-Vm-Status-Generic-custom | Contrôle permettant de vérifier l'état global d'une machine virtuelle | -| Vm-Thinprovisioning | Virt-VMWare2-Vm-Thinprovisioning-Generic-custom | Contrôle permettant de vérifier si une machine virtuelle possède un disque en mode 'thinprovisioning' ou non | -| Vm-Tools | Virt-VMWare2-Vm-Tools-Generic-custom | Contrôle permettant de vérifier l'état des vmtools d'une machine virtuelle | +| Vm-Limit | Virt-VMWare2-Vm-Limit-Generic-custom | Contrôle permettant de vérifier la définition de limites. | +| Vm-Snapshot | Virt-VMWare2-Vm-Snapshot-Generic-custom | Contrôle permettant de vérifier l'âge des snapshosts sur la machine virtuelle. | +| Vm-Status | Virt-VMWare2-Vm-Status-Generic-custom | Contrôle permettant de vérifier l'état global d'une machine virtuelle. | +| Vm-Thinprovisioning | Virt-VMWare2-Vm-Thinprovisioning-Generic-custom | Contrôle permettant de vérifier si une machine virtuelle possède un disque en mode 'thinprovisioning' ou non. | +| Vm-Tools | Virt-VMWare2-Vm-Tools-Generic-custom | Contrôle permettant de vérifier l'état des vmtools d'une machine virtuelle. | > Les services listés ci-dessus sont créés automatiquement lorsque le modèle d'hôte **Virt-VMWare2-VM-custom** est utilisé. @@ -34,11 +40,11 @@ Le connecteur apporte les modèles de service suivants | Alias | Modèle de service | Description | |:-------------------|:-----------------------------------------------|:----------------------------------------------------------------------------------------------------------| -| Vm-Cpu | Virt-VMWare2-Vm-Cpu-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation CPU d'une machine virtuelle | +| Vm-Cpu | Virt-VMWare2-Vm-Cpu-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation CPU d'une machine virtuelle. | | Vm-Datastores-Iops | Virt-VMWare2-Vm-Datastores-Iops-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation des datastores rattachées à une machine virtuelle. | -| Vm-Device | Virt-VMWare2-Vm-Device-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation CPU d'une machine virtuelle | -| Vm-Memory | Virt-VMWare2-Vm-Memory-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation mémoire d'une machine virtuelle | -| Vm-Swap | Virt-VMWare2-Vm-Swap-Generic-custom | Contrôle permettant de vérifier si une machine virtuelle swappe | +| Vm-Device | Virt-VMWare2-Vm-Device-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation CPU d'une machine virtuelle. | +| Vm-Memory | Virt-VMWare2-Vm-Memory-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation mémoire d'une machine virtuelle. | +| Vm-Swap | Virt-VMWare2-Vm-Swap-Generic-custom | Contrôle permettant de vérifier si une machine virtuelle swappe. | > Les services listés ci-dessus ne sont pas créés automatiquement lorsqu'un modèle d'hôte est appliqué. Pour les utiliser, [créez un service manuellement](/docs/monitoring/basic-objects/services) et appliquez le modèle de service souhaité. @@ -51,7 +57,7 @@ Le connecteur apporte les modèles de service suivants | Nom de la règle | Description | |:----------------|:--------------------------------| -| VMWare VM | Discover VMWare Virtual Machine | +| VMWare VM | Discover VMWare Virtual Machine. | Rendez-vous sur la [documentation dédiée](/docs/monitoring/discovery/hosts-discovery) pour en savoir plus sur la découverte automatique d'hôtes. @@ -348,11 +354,11 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------|:------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| CENTREONVMWAREPORT | Connector port (default: 5700) | 5700 | | -| CENTREONVMWARECONTAINER | Container to use (it depends of the connector configuration) | default | | -| CENTREONVMWAREHOST | Connector hostname (required) | localhost |X | -| VMNAME | VM hostname to check. If not set, we check all VMs | | | -| VMUUID | Specify The VM UUID | | | +| CENTREONVMWAREPORT | Connector port (default: 5700). | 5700 | | +| CENTREONVMWARECONTAINER | Container to use (it depends of the connector configuration). | default | | +| CENTREONVMWAREHOST | Connector hostname (required). | localhost |X | +| VMNAME | VM hostname to check. If not set, we check all VMs. | | | +| VMUUID | Specify The VM UUID. | | | | CENTREONVMWAREEXTRAOPTIONS | Any extra option you may want to add to every command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | 5. [Déployez la configuration](/docs/monitoring/monitoring-servers/deploying-a-configuration). L'hôte apparaît dans la liste des hôtes 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 de l'hôte : celle-ci montre les valeurs des macros. @@ -385,7 +391,7 @@ 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 | .* | | +| 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 | | | WARNINGMAXTOTALLATENCY | Thresholds | | | | CRITICALMAXTOTALLATENCY | Thresholds | | | From fa34bf3e8c551f6dbac4fee8c946d2f1a0329bf3 Mon Sep 17 00:00:00 2001 From: YanMeddour <83709929+YanMeddour@users.noreply.github.com> Date: Tue, 26 Dec 2023 15:11:55 +0100 Subject: [PATCH 03/14] Add "Overview" part --- .../procedures/virtualization-vmware2-vm.md | 24 ++++++++++++------- 1 file changed, 15 insertions(+), 9 deletions(-) diff --git a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md index 9e21be1e9e83..86ed9ee23ea4 100644 --- a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md +++ b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md @@ -5,6 +5,12 @@ title: VMware VM import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +## Overview + +VMware is an software compagny based in USA. VMware provides cloud computing and virtualization software and services. + +The Centreon Plugin and Monitoring Connectors rely on the Centreon VMWare Connector to request the vCenter SDK. + ## Pack assets ### Templates @@ -20,11 +26,11 @@ The connector brings the following service templates (sorted by the host templat | Service Alias | Service Template | Service Description | |:--------------------|:------------------------------------------------|:------------------------------------------------------------------------| -| Vm-Limit | Virt-VMWare2-Vm-Limit-Generic-custom | Check limit definition | -| Vm-Snapshot | Virt-VMWare2-Vm-Snapshot-Generic-custom | Check snapshot age of a virtual machine | -| Vm-Status | Virt-VMWare2-Vm-Status-Generic-custom | Check global status of a virtual machine | -| Vm-Thinprovisioning | Virt-VMWare2-Vm-Thinprovisioning-Generic-custom | Check if a virtual machine has a disk in mode 'thinprovisioning' or not | -| Vm-Tools | Virt-VMWare2-Vm-Tools-Generic-custom | Check vmtools state of a virtual machine | +| Vm-Limit | Virt-VMWare2-Vm-Limit-Generic-custom | Check limit definition. | +| Vm-Snapshot | Virt-VMWare2-Vm-Snapshot-Generic-custom | Check snapshot age of a virtual machine. | +| Vm-Status | Virt-VMWare2-Vm-Status-Generic-custom | Check global status of a virtual machine. | +| Vm-Thinprovisioning | Virt-VMWare2-Vm-Thinprovisioning-Generic-custom | Check if a virtual machine has a disk in mode 'thinprovisioning' or not. | +| Vm-Tools | Virt-VMWare2-Vm-Tools-Generic-custom | Check vmtools state of a virtual machine. | > The services listed above are created automatically when the **Virt-VMWare2-VM-custom** host template is used. @@ -33,11 +39,11 @@ The connector brings the following service templates (sorted by the host templat | Service Alias | Service Template | Service Description | |:-------------------|:-----------------------------------------------|:------------------------------------------------------| -| Vm-Cpu | Virt-VMWare2-Vm-Cpu-Generic-custom | Check CPU usage of a virtual machine | +| Vm-Cpu | Virt-VMWare2-Vm-Cpu-Generic-custom | Check CPU usage of a virtual machine. | | Vm-Datastores-Iops | Virt-VMWare2-Vm-Datastores-Iops-Generic-custom | Check datastores IOPS linked to the virtual machine. | -| Vm-Device | Virt-VMWare2-Vm-Device-Generic-custom | Check CPU usage of a virtual machine | -| Vm-Memory | Virt-VMWare2-Vm-Memory-Generic-custom | Check memory usage of a virtual machine | -| Vm-Swap | Virt-VMWare2-Vm-Swap-Generic-custom | Check if a virtual machine is swapping | +| Vm-Device | Virt-VMWare2-Vm-Device-Generic-custom | Check CPU usage of a virtual machine. | +| Vm-Memory | Virt-VMWare2-Vm-Memory-Generic-custom | Check memory usage of a virtual machine. | +| Vm-Swap | Virt-VMWare2-Vm-Swap-Generic-custom | Check if a virtual machine is swapping. | > The services listed above are not created automatically when a host template is applied. To use them, [create a service manually](/docs/monitoring/basic-objects/services), then apply the service template you want. From 7e6bef56791b554f3b10296a4c58ce2902827588 Mon Sep 17 00:00:00 2001 From: omercier <32134301+omercier@users.noreply.github.com> Date: Fri, 26 Jan 2024 18:54:20 +0100 Subject: [PATCH 04/14] Apply suggestions from code review Co-authored-by: cg-tw <83637804+cg-tw@users.noreply.github.com> --- .../procedures/virtualization-vmware2-vm.md | 140 ++++++++--------- .../procedures/virtualization-vmware2-vm.md | 142 +++++++++--------- 2 files changed, 141 insertions(+), 141 deletions(-) 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 80b136cbb011..c35c76b707a4 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 @@ -28,9 +28,9 @@ Le connecteur apporte les modèles de service suivants | Alias | Modèle de service | Description | |:--------------------|:------------------------------------------------|:-------------------------------------------------------------------------------------------------------------| | Vm-Limit | Virt-VMWare2-Vm-Limit-Generic-custom | Contrôle permettant de vérifier la définition de limites. | -| Vm-Snapshot | Virt-VMWare2-Vm-Snapshot-Generic-custom | Contrôle permettant de vérifier l'âge des snapshosts sur la machine virtuelle. | +| Vm-Snapshot | Virt-VMWare2-Vm-Snapshot-Generic-custom | Contrôle permettant de vérifier l'âge des snapshots sur la machine virtuelle. | | Vm-Status | Virt-VMWare2-Vm-Status-Generic-custom | Contrôle permettant de vérifier l'état global d'une machine virtuelle. | -| Vm-Thinprovisioning | Virt-VMWare2-Vm-Thinprovisioning-Generic-custom | Contrôle permettant de vérifier si une machine virtuelle possède un disque en mode 'thinprovisioning' ou non. | +| Vm-Thinprovisioning | Virt-VMWare2-Vm-Thinprovisioning-Generic-custom | Contrôle permettant de vérifier si une machine virtuelle possède un disque en mode 'thin provisioning' ou non. | | Vm-Tools | Virt-VMWare2-Vm-Tools-Generic-custom | Contrôle permettant de vérifier l'état des vmtools d'une machine virtuelle. | > Les services listés ci-dessus sont créés automatiquement lorsque le modèle d'hôte **Virt-VMWare2-VM-custom** est utilisé. @@ -41,7 +41,7 @@ Le connecteur apporte les modèles de service suivants | Alias | Modèle de service | Description | |:-------------------|:-----------------------------------------------|:----------------------------------------------------------------------------------------------------------| | Vm-Cpu | Virt-VMWare2-Vm-Cpu-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation CPU d'une machine virtuelle. | -| Vm-Datastores-Iops | Virt-VMWare2-Vm-Datastores-Iops-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation des datastores rattachées à une machine virtuelle. | +| Vm-Datastores-Iops | Virt-VMWare2-Vm-Datastores-Iops-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation des datastores rattachés à une machine virtuelle. | | Vm-Device | Virt-VMWare2-Vm-Device-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation CPU d'une machine virtuelle. | | Vm-Memory | Virt-VMWare2-Vm-Memory-Generic-custom | Contrôle permettant de vérifier le taux d'utilisation mémoire d'une machine virtuelle. | | Vm-Swap | Virt-VMWare2-Vm-Swap-Generic-custom | Contrôle permettant de vérifier si une machine virtuelle swappe. | @@ -57,7 +57,7 @@ Le connecteur apporte les modèles de service suivants | Nom de la règle | Description | |:----------------|:--------------------------------| -| VMWare VM | Discover VMWare Virtual Machine. | +| VMWare VM | Discover VMWare virtual machines. | Rendez-vous sur la [documentation dédiée](/docs/monitoring/discovery/hosts-discovery) pour en savoir plus sur la découverte automatique d'hôtes. @@ -160,7 +160,7 @@ Voici le tableau des services pour ce connecteur, détaillant les métriques rat | Métrique | Description | Unité | |:------------|:-------------------------------------------|:------| -| status | Status of the Thinprovisoning virtualdisks | | +| status | Status of the thin provisoning virtual disks | | @@ -255,7 +255,7 @@ Pour découvrir les balises et les attributs personnalisés, vous devez : Le Collecteur Centreon avec le connecteur VMWare d'installé doit accéder en HTTPS (TCP/443) au vCenter. -Les Collecteurs requêtant le Collecteur avec le connecteur VMWare doit accéder en TCP/5700 au Collecteur avec le Connecteur VMWare. +Les collecteurs requêtant le collecteur avec le connecteur VMWare doivent accéder en TCP/5700 au collecteur avec le connecteur VMWare. ## Installer le connecteur de supervision @@ -355,10 +355,10 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------|:------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | CENTREONVMWAREPORT | Connector port (default: 5700). | 5700 | | -| CENTREONVMWARECONTAINER | Container to use (it depends of the connector configuration). | default | | +| CENTREONVMWARECONTAINER | Container to use (it depends on the connector's configuration). | default | | | CENTREONVMWAREHOST | Connector hostname (required). | localhost |X | -| VMNAME | VM hostname to check. If not set, we check all VMs. | | | -| VMUUID | Specify The VM UUID. | | | +| VMNAME | Hostname of the VM to monitor. If not set, we check all VMs. | | | +| VMUUID | Specify the VM's UUID. | | | | CENTREONVMWAREEXTRAOPTIONS | Any extra option you may want to add to every command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | 5. [Déployez la configuration](/docs/monitoring/monitoring-servers/deploying-a-configuration). L'hôte apparaît dans la liste des hôtes 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 de l'hôte : celle-ci montre les valeurs des macros. @@ -409,7 +409,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'). You can use the following variables: %{connection\_state} | %{connection\_state} !~ /^connected$/i | | -| FILTERDEVICE | Device to check (Required) (Example: --device='VirtualCdrom') | | X | +| 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} | | | | WARNINGTOTALDEVICECONNECTED | Warning threshold | | | @@ -490,7 +490,7 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:-------------|:----------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| STATUS | Thinprovisioning status (default: none) Example: 'active,CRITICAL' or 'notactive,WARNING' | active,WARNING | X | +| STATUS | Thin provisioning status (default: none). Example: 'active,CRITICAL' or 'notactive,WARNING' | active,WARNING | X | | 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 | | @@ -500,7 +500,7 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:-------------------|:----------------------------------------------------------------------------------------------------|:------------------|:-----------:| | NOTINSTALLEDSTATUS | Status if vmtools is not installed (default: critical) | critical | X | | NOTRUNNINGSTATUS | Status if vmtools is not running (default: critical) | critical | X | -| NOTUP2DATESTATUS | Status if vmtools is not upd2date (default: warning) | warning | | +| NOTUP2DATESTATUS | Status if vmtools is not up to date (default: warning) | warning | | | 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) | | | @@ -629,13 +629,13 @@ Les options génériques sont listées ci-dessous : | --pass-manager | Define the password manager you want to use. Supported managers are: environment, file, keepass, hashicorpvault and teampass. | | --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 | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. | +| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. | | --explode-perfdata-max | 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)' | -| --change-short-output --change-long-output | Modify the short/long output that is returned by the plugin. Syntax: --change-short-output=pattern~replacement~modifier Most commonly used modifiers are i (case insensitive) and g (replace all occurrences). Eg: adding --change-short-output='OK~Up~gi' will replace all occurrences of 'OK', 'ok', 'Ok' or 'oK' with 'Up' | -| --change-exit | Replace an exit code with one of your choice. Eg: adding --change-exit=unknown=critical will result in a CRITICAL state instead of an UNKNOWN state. | +| --change-short-output --change-long-output | Modify the short/long output that is returned by the plugin. Syntax: --change-short-output=pattern~replacement~modifier Most commonly used modifiers are i (case insensitive) and g (replace all occurrences). Example: adding --change-short-output='OK~Up~gi' will replace all occurrences of 'OK', 'ok', 'Ok' or 'oK' with 'Up' | +| --change-exit | Replace an exit code with one of your choice. Example: adding --change-exit=unknown=critical will result in a CRITICAL state instead of an UNKNOWN state. | | --range-perfdata | Rewrite the ranges displayed in the perfdata. Accepted values: 0: nothing is changed. 1: if the lower value of the range is equal to 0, it is removed. 2: remove the thresholds from the perfdata. | | --filter-uom | Mask the units when they don't match the given regular expression. | | --opt-exit | Replace the exit code in case of an execution error (i.e. wrong option provided, SSH connection refused, timeout, etc). Default: unknown. | @@ -651,14 +651,14 @@ Les options génériques sont listées ci-dessous : | --source-encoding | Define the character encoding of the response sent by the monitored resource Default: 'UTF-8'. | | --connector-hostname | Connector hostname (required). | | --connector-port | Connector port (default: 5700). | -| --container | Container to use (it depends of the connector configuration). | -| --vsphere-address | Address of vpshere/ESX to connect. | -| --vsphere-username | Username of vpshere/ESX connection (with --vsphere-address). | -| --vsphere-password | Password of vpshere/ESX connection (with --vsphere-address). | +| --container | Container to use (it depends on the connector's configuration). | +| --vsphere-address | Address of the vpshere/ESX instance to connect to. | +| --vsphere-username | Username to use to connect to the vpshere/ESX instance (with --vsphere-address). | +| --vsphere-password | Password used to connect to the vpshere/ESX instance (with --vsphere-address). | | --timeout | Set global execution timeout (Default: 50) | -| --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. | +| --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}. | @@ -672,13 +672,13 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to monitor. If not set, we check all VMs. | | --filter | VM hostname is a regexp. Exemple : --vm-hostname='^((VM-PROD-*))' --filter | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | +| --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} | @@ -690,16 +690,16 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | +| --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). | | --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. | +| --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} | @@ -710,14 +710,14 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | -| --display-description | Display virtual machine description. | +| --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). | +| --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} | @@ -730,11 +730,11 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --display-description | Display virtual machine description. | +| --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} | @@ -748,14 +748,14 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | -| --display-description | Display virtual machine description. | +| --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). | +| --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} | @@ -769,16 +769,16 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | -| --display-description | Display virtual machine description. | +| --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). | +| --display-description | Display the description of the virtual machine. | | --check-consolidation | Check if VM needs consolidation (since vsphere 5.0). | -| --disconnect-status | Status if VM disconnected (default: 'unknown'). | +| --disconnect-status | Status if the VM is disconnected (default: 'unknown'). | | --nopoweredon-skip | Skip check if VM is not poweredOn. | | --empty-continue | Ask to the connector that an empty response is ok. | | --unit | Select the unit for performance data and thresholds. May be 's'for seconds, 'm' for minutes, 'h' for hours, 'd' for days, 'w' for weeks. Default is seconds | @@ -790,13 +790,13 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | +| --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} | @@ -809,14 +809,14 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | -| --display-description | Display virtual machine description. | +| --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). | +| --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} | @@ -828,34 +828,34 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | +| --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). | | --disconnect-status | Status if VM disconnected (default: 'unknown'). | | --nopoweredon-skip | Skip check if VM is not poweredOn. | -| --display-description | Display virtual machine description. | -| --thinprovisioning-status | Thinprovisioning status (default: none) Example: 'active,CRITICAL' or 'notactive,WARNING' | +| --display-description | Display the description of the virtual machine. | +| --thinprovisioning-status | Thin provisioning status (default: none) Example: 'active,CRITICAL' or 'notactive,WARNING' | | Option | Description | |:----------------------------|:--------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | +| --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). | | --disconnect-status | Status if VM disconnected (default: 'unknown'). | | --nopoweredon-skip | Skip check if VM is not poweredOn. | | --empty-continue | Ask to the connector that an empty response is ok. | -| --display-description | Display virtual machine description. | +| --display-description | Display the description of the virtual machine. | | --tools-notinstalled-status | Status if vmtools is not installed (default: critical). | | --tools-notrunning-status | Status if vmtools is not running (default: critical). | | --tools-notup2date-status | Status if vmtools is not upd2date (default: warning). | diff --git a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md index 86ed9ee23ea4..2117b0a82e59 100644 --- a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md +++ b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md @@ -27,10 +27,10 @@ The connector brings the following service templates (sorted by the host templat | Service Alias | Service Template | Service Description | |:--------------------|:------------------------------------------------|:------------------------------------------------------------------------| | Vm-Limit | Virt-VMWare2-Vm-Limit-Generic-custom | Check limit definition. | -| Vm-Snapshot | Virt-VMWare2-Vm-Snapshot-Generic-custom | Check snapshot age of a virtual machine. | +| Vm-Snapshot | Virt-VMWare2-Vm-Snapshot-Generic-custom | Check the age of the snapshot for a virtual machine. | | Vm-Status | Virt-VMWare2-Vm-Status-Generic-custom | Check global status of a virtual machine. | -| Vm-Thinprovisioning | Virt-VMWare2-Vm-Thinprovisioning-Generic-custom | Check if a virtual machine has a disk in mode 'thinprovisioning' or not. | -| Vm-Tools | Virt-VMWare2-Vm-Tools-Generic-custom | Check vmtools state of a virtual machine. | +| Vm-Thinprovisioning | Virt-VMWare2-Vm-Thinprovisioning-Generic-custom | Check if a virtual machine has a disk in mode 'thin provisioning' or not. | +| Vm-Tools | Virt-VMWare2-Vm-Tools-Generic-custom | Check the state of vmtools for a virtual machine. | > The services listed above are created automatically when the **Virt-VMWare2-VM-custom** host template is used. @@ -39,10 +39,10 @@ The connector brings the following service templates (sorted by the host templat | Service Alias | Service Template | Service Description | |:-------------------|:-----------------------------------------------|:------------------------------------------------------| -| Vm-Cpu | Virt-VMWare2-Vm-Cpu-Generic-custom | Check CPU usage of a virtual machine. | +| Vm-Cpu | Virt-VMWare2-Vm-Cpu-Generic-custom | Check CPU usage for a virtual machine. | | Vm-Datastores-Iops | Virt-VMWare2-Vm-Datastores-Iops-Generic-custom | Check datastores IOPS linked to the virtual machine. | -| Vm-Device | Virt-VMWare2-Vm-Device-Generic-custom | Check CPU usage of a virtual machine. | -| Vm-Memory | Virt-VMWare2-Vm-Memory-Generic-custom | Check memory usage of a virtual machine. | +| Vm-Device | Virt-VMWare2-Vm-Device-Generic-custom | Check CPU usage for a virtual machine. | +| Vm-Memory | Virt-VMWare2-Vm-Memory-Generic-custom | Check memory usage for a virtual machine. | | Vm-Swap | Virt-VMWare2-Vm-Swap-Generic-custom | Check if a virtual machine is swapping. | > The services listed above are not created automatically when a host template is applied. To use them, [create a service manually](/docs/monitoring/basic-objects/services), then apply the service template you want. @@ -56,7 +56,7 @@ The connector brings the following service templates (sorted by the host templat | Rule name | Description | |:----------------|:--------------------------------| -| VMWare VM | Discover VMWare Virtual Machine | +| VMWare VM | Discover VMWare virtual machines | More information about discovering hosts automatically is available on the [dedicated page](/docs/monitoring/discovery/hosts-discovery). @@ -159,7 +159,7 @@ Here is the list of services for this connector, detailing all metrics linked to | Metric name | Description | Unit | |:------------|:-------------------------------------------|:------| -| status | Status of the Thinprovisoning virtualdisks | | +| status | Status of the thin provisoning virtual disks | | @@ -358,10 +358,10 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:---------------------------|:------------------------------------------------------------------------------------------------------|:------------------|:-----------:| | CENTREONVMWAREPORT | Connector port (default: 5700) | 5700 | | -| CENTREONVMWARECONTAINER | Container to use (it depends of the connector configuration) | default | | +| CENTREONVMWARECONTAINER | Container to use (it depends on the connector's configuration) | default | | | CENTREONVMWAREHOST | Connector hostname (required) | localhost | X | -| VMNAME | VM hostname to check. If not set, we check all VMs | | | -| VMUUID | Specify The VM UUID | | | +| VMNAME | Hostname of the VM to check. If not set, we check all VMs | | | +| VMUUID | Specify the VM's UUID | | | | CENTREONVMWAREEXTRAOPTIONS | Any extra option you may want to add to every command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | 5. [Deploy the configuration](/docs/monitoring/monitoring-servers/deploying-a-configuration). The host appears in the list of hosts, and on the **Resources Status** page. The command that is sent by the connector is displayed in the details panel of the host: it shows the values of the macros. @@ -412,7 +412,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'). You can use the following variables: %{connection\_state} | %{connection\_state} !~ /^connected$/i | | -| FILTERDEVICE | Device to check (Required) (Example: --device='VirtualCdrom') | | X | +| 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} | | | | WARNINGTOTALDEVICECONNECTED | Warning threshold | | | @@ -493,7 +493,7 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:-------------|:----------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| STATUS | Thinprovisioning status (default: none) Example: 'active,CRITICAL' or 'notactive,WARNING' | active,WARNING | X | +| STATUS | Thin provisioning status (default: none). Example: 'active,CRITICAL' or 'notactive,WARNING' | active,WARNING | X | | 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 | | @@ -630,13 +630,13 @@ All generic options are listed here: | --pass-manager | Define the password manager you want to use. Supported managers are: environment, file, keepass, hashicorpvault and teampass. | | --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 | 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. | | --explode-perfdata-max | 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)' | | --change-short-output --change-long-output | Modify the short/long output that is returned by the plugin. Syntax: --change-short-output=pattern~replacement~modifier Most commonly used modifiers are i (case insensitive) and g (replace all occurrences). Eg: adding --change-short-output='OK~Up~gi' will replace all occurrences of 'OK', 'ok', 'Ok' or 'oK' with 'Up' | -| --change-exit | Replace an exit code with one of your choice. Eg: adding --change-exit=unknown=critical will result in a CRITICAL state instead of an UNKNOWN state. | +| --change-exit | Replace an exit code with one of your choice. Example: adding --change-exit=unknown=critical will result in a CRITICAL state instead of an UNKNOWN state. | | --range-perfdata | Rewrite the ranges displayed in the perfdata. Accepted values: 0: nothing is changed. 1: if the lower value of the range is equal to 0, it is removed. 2: remove the thresholds from the perfdata. | | --filter-uom | Mask the units when they don't match the given regular expression. | | --opt-exit | Replace the exit code in case of an execution error (i.e. wrong option provided, SSH connection refused, timeout, etc). Default: unknown. | @@ -649,17 +649,17 @@ All generic options are listed here: | --disco-format | Applies only to modes beginning with 'list-'. Returns the list of available macros to configure a service discovery rule (formatted in XML). | | --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'. | +| --source-encoding | Define the character encoding of the response sent by the monitored resource. Default: 'UTF-8'. | | --connector-hostname | Connector hostname (required). | | --connector-port | Connector port (default: 5700). | -| --container | Container to use (it depends of the connector configuration). | -| --vsphere-address | Address of vpshere/ESX to connect. | -| --vsphere-username | Username of vpshere/ESX connection (with --vsphere-address). | -| --vsphere-password | Password of vpshere/ESX connection (with --vsphere-address). | +| --container | Container to use (it depends on the connector's configuration). | +| --vsphere-address | Address of the vpshere/ESX instance to connect to. | +| --vsphere-username | Username to use to connect to the vpshere/ESX instance (with --vsphere-address). | +| --vsphere-password | Password used to connect to the vpshere/ESX instance (with --vsphere-address). | | --timeout | Set global execution timeout (Default: 50) | -| --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. | +| --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}. | @@ -673,13 +673,13 @@ All available options for each service template are listed below: | Option | Description | |:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. Exemple : --vm-hostname='^((VM-PROD-*))' --filter | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | +| --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} | @@ -691,16 +691,16 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | +| --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). | | --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. | +| --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} | @@ -711,15 +711,15 @@ All available options for each service template are listed below: | Option | Description | |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | -| --display-description | Display virtual machine description. | -| --device | Device to check (Required) (Example: --device='VirtualCdrom'). | +| --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). | +| --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} | @@ -731,11 +731,11 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --display-description | Display virtual machine description. | +| --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} | @@ -749,19 +749,19 @@ All available options for each service template are listed below: | Option | Description | |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | -| --display-description | Display virtual machine description. | +| --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). | +| --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} | | --units | Units of thresholds (Default: '%') ('%', 'B'). | -| --free | Thresholds are on free space left. | +| --free | Thresholds are applied on free space left. | | --warning-* | Warning threshold. Can be: 'consumed', 'active', 'overhead', 'ballooning', 'shared'. | | --critical-* | Critical threshold. Can be: 'consumed', 'active', 'overhead', 'ballooning', 'shared'. | @@ -770,14 +770,14 @@ All available options for each service template are listed below: | Option | Description | |:----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | -| --display-description | Display virtual machine description. | +| --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). | +| --display-description | Display the description of the virtual machine. | | --check-consolidation | Check if VM needs consolidation (since vsphere 5.0). | | --disconnect-status | Status if VM disconnected (default: 'unknown'). | | --nopoweredon-skip | Skip check if VM is not poweredOn. | @@ -791,13 +791,13 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | +| --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} | @@ -810,14 +810,14 @@ All available options for each service template are listed below: | Option | Description | |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | -| --display-description | Display virtual machine description. | +| --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). | +| --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} | @@ -829,34 +829,34 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | +| --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). | | --disconnect-status | Status if VM disconnected (default: 'unknown'). | | --nopoweredon-skip | Skip check if VM is not poweredOn. | -| --display-description | Display virtual machine description. | -| --thinprovisioning-status | Thinprovisioning status (default: none) Example: 'active,CRITICAL' or 'notactive,WARNING' | +| --display-description | Display the description of the virtual machine. | +| --thinprovisioning-status | Thin provisioning status (default: none). Example: 'active,CRITICAL' or 'notactive,WARNING' | | Option | Description | |:----------------------------|:--------------------------------------------------------------| -| --vm-hostname | VM hostname to check. If not set, we check all VMs. | +| --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | | --filter | VM hostname is a regexp. | | --filter-description | Filter also virtual machines description (can be a regexp). | | --filter-os | Filter also virtual machines OS name (can be a regexp). | -| --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). | +| --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). | | --disconnect-status | Status if VM disconnected (default: 'unknown'). | | --nopoweredon-skip | Skip check if VM is not poweredOn. | | --empty-continue | Ask to the connector that an empty response is ok. | -| --display-description | Display virtual machine description. | +| --display-description | Display the description of the virtual machine. | | --tools-notinstalled-status | Status if vmtools is not installed (default: critical). | | --tools-notrunning-status | Status if vmtools is not running (default: critical). | | --tools-notup2date-status | Status if vmtools is not upd2date (default: warning). | From 7a1f736261844d670b238177143217f2dc4602e4 Mon Sep 17 00:00:00 2001 From: YanMeddour Date: Mon, 26 Feb 2024 15:03:12 +0100 Subject: [PATCH 05/14] Add the apt install commands for Debian OS and update of several descriptions --- .../procedures/virtualization-vmware2-vm.md | 17 +++++++++++++++-- .../procedures/virtualization-vmware2-vm.md | 18 ++++++++++++++++-- 2 files changed, 31 insertions(+), 4 deletions(-) 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 c35c76b707a4..2e5c8c2a1269 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 @@ -182,10 +182,23 @@ Pour la supervision VMWare, centreon utlise un daemon pour se connecter et requ Installer le daemon sur tous les pollers : + + + +```bash +apt install centreon-plugin-virtualization-vmware-daemon ``` + + + + +```bash yum install centreon-plugin-Virtualization-VMWare-daemon ``` + + + Pour configurer les accès à votre infrastructure, éditer le fichier "/etc/centreon/centreon\_vmware.pm" : @@ -853,12 +866,12 @@ 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). | | --disconnect-status | Status if VM disconnected (default: 'unknown'). | -| --nopoweredon-skip | Skip check if VM is not poweredOn. | +| --nopoweredon-skip | Skip check if VM is not powered on. | | --empty-continue | Ask to the connector that an empty response is ok. | | --display-description | Display the description of the virtual machine. | | --tools-notinstalled-status | Status if vmtools is not installed (default: critical). | | --tools-notrunning-status | Status if vmtools is not running (default: critical). | -| --tools-notup2date-status | Status if vmtools is not upd2date (default: warning). | +| --tools-notup2date-status | Status if vmtools is not up to date (default: warning). | diff --git a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md index 2117b0a82e59..3226861c7e7e 100644 --- a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md +++ b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md @@ -181,10 +181,24 @@ For the VMWare monitoring, Centreon use daemon to connect and request the vCente Install this daemon on each needed poller: + + + +```bash +apt install centreon-plugin-virtualization-vmware-daemon ``` + + + + +```bash yum install centreon-plugin-Virtualization-VMWare-daemon ``` + + + + To configure the access to your infrastructure, edit the "/etc/centreon/centreon\_vmware.pm" configuration file: @@ -503,7 +517,7 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin |:-------------------|:----------------------------------------------------------------------------------------------------|:------------------|:-----------:| | NOTINSTALLEDSTATUS | Status if vmtools is not installed (default: critical) | critical | X | | NOTRUNNINGSTATUS | Status if vmtools is not running (default: critical) | critical | X | -| NOTUP2DATESTATUS | Status if vmtools is not upd2date (default: warning) | warning | | +| NOTUP2DATESTATUS | Status if vmtools is not up to date (default: warning) | warning | | | EXTRAOPTIONS | Any extra option you may want to add to the command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | @@ -780,7 +794,7 @@ All available options for each service template are listed below: | --display-description | Display the description of the virtual machine. | | --check-consolidation | Check if VM needs consolidation (since vsphere 5.0). | | --disconnect-status | Status if VM disconnected (default: 'unknown'). | -| --nopoweredon-skip | Skip check if VM is not poweredOn. | +| --nopoweredon-skip | Skip check if VM is not powered on. | | --empty-continue | Ask to the connector that an empty response is ok. | | --unit | Select the unit for 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 | Warning threshold for snapshot's age. | From 7de7e1e4370c6258c13a0435903a91298d46300d Mon Sep 17 00:00:00 2001 From: YanMeddour <83709929+YanMeddour@users.noreply.github.com> Date: Wed, 28 Feb 2024 17:40:45 +0100 Subject: [PATCH 06/14] Update virtualization-vmware2-vm.md --- .../plugin-packs/procedures/virtualization-vmware2-vm.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md index 3226861c7e7e..b9e7fa30a069 100644 --- a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md +++ b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md @@ -794,7 +794,7 @@ All available options for each service template are listed below: | --display-description | Display the description of the virtual machine. | | --check-consolidation | Check if VM needs consolidation (since vsphere 5.0). | | --disconnect-status | Status if VM disconnected (default: 'unknown'). | -| --nopoweredon-skip | Skip check if VM is not powered on. | +| --nopoweredon-skip | Skip check if VM is not poweredOn. | | --empty-continue | Ask to the connector that an empty response is ok. | | --unit | Select the unit for 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 | Warning threshold for snapshot's age. | @@ -873,7 +873,7 @@ All available options for each service template are listed below: | --display-description | Display the description of the virtual machine. | | --tools-notinstalled-status | Status if vmtools is not installed (default: critical). | | --tools-notrunning-status | Status if vmtools is not running (default: critical). | -| --tools-notup2date-status | Status if vmtools is not upd2date (default: warning). | +| --tools-notup2date-status | Status if vmtools is not up to date (default: warning). | From c890b59eca6c9d98e7f1419e4a83fac7912f087c Mon Sep 17 00:00:00 2001 From: YanMeddour <83709929+YanMeddour@users.noreply.github.com> Date: Wed, 28 Feb 2024 17:41:31 +0100 Subject: [PATCH 07/14] Update i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md to i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/virtualization-vmware2-vm.md --- .../plugin-packs/{procedures => }/virtualization-vmware2-vm.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/{procedures => }/virtualization-vmware2-vm.md (100%) 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/virtualization-vmware2-vm.md similarity index 100% rename from i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md rename to i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/virtualization-vmware2-vm.md From 85e39b56591c98fcc8f011910ce2da0a053f2330 Mon Sep 17 00:00:00 2001 From: YanMeddour <83709929+YanMeddour@users.noreply.github.com> Date: Fri, 1 Mar 2024 17:18:03 +0100 Subject: [PATCH 08/14] Update virtualization-vmware2-vm.md --- .../procedures/virtualization-vmware2-vm.md | 68 +++++++++---------- 1 file changed, 34 insertions(+), 34 deletions(-) diff --git a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md index b9e7fa30a069..bcf6075af029 100644 --- a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md +++ b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md @@ -270,7 +270,7 @@ To discover Tags and Custom Attributes, you must : The Poller with the Centreon VMware Connector installed need to access in TCP/443 HTTPS to the Vcenter. -The Pollers that request the Centreon VMWare Connector host need to access in TCP/5700 to the Centreon VMWare Connector host. +Pollers requesting data from the Centreon VMware Connector must establish TCP connections on port 5700 to communicate with the Connector's host. ## Installing the monitoring connector @@ -688,9 +688,9 @@ All available options for each service template are listed below: | Option | Description | |:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. Exemple : --vm-hostname='^((VM-PROD-*))' --filter | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on their names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | @@ -706,14 +706,14 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on their names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | | --datastore-name | Datastore to check. If not set, we check all datastores. | -| --filter-datastore | Datastore name is a regexp. | +| --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} | @@ -726,9 +726,9 @@ All available options for each service template are listed below: | Option | Description | |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on the devices' names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | @@ -746,9 +746,9 @@ All available options for each service template are listed below: | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on their names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --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} | @@ -764,9 +764,9 @@ All available options for each service template are listed below: | Option | Description | |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on their names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | @@ -785,9 +785,9 @@ All available options for each service template are listed below: | Option | Description | |:----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on their names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | @@ -795,7 +795,7 @@ All available options for each service template are listed below: | --check-consolidation | Check if VM needs consolidation (since vsphere 5.0). | | --disconnect-status | Status if VM disconnected (default: 'unknown'). | | --nopoweredon-skip | Skip check if VM is not poweredOn. | -| --empty-continue | Ask to the connector that an empty response is ok. | +| --empty-continue | Instructs the connector to proceed without error when no VMs match the specified criteria. | | --unit | Select the unit for 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 | Warning threshold for snapshot's age. | | --critical | Critical threshold for snapshot's age. | @@ -806,9 +806,9 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on their names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | @@ -825,9 +825,9 @@ All available options for each service template are listed below: | Option | Description | |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on their names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | @@ -844,9 +844,9 @@ All available options for each service template are listed below: | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on their names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | @@ -861,15 +861,15 @@ All available options for each service template are listed below: | Option | Description | |:----------------------------|:--------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on their names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | | --disconnect-status | Status if VM disconnected (default: 'unknown'). | | --nopoweredon-skip | Skip check if VM is not poweredOn. | -| --empty-continue | Ask to the connector that an empty response is ok. | +| --empty-continue | Instructs the connector to proceed without error when no VMs match the specified criteria. | | --display-description | Display the description of the virtual machine. | | --tools-notinstalled-status | Status if vmtools is not installed (default: critical). | | --tools-notrunning-status | Status if vmtools is not running (default: critical). | From 449ca4aba902536e2ff3e6e2abdcecc35a952192 Mon Sep 17 00:00:00 2001 From: YanMeddour <83709929+YanMeddour@users.noreply.github.com> Date: Fri, 1 Mar 2024 17:18:10 +0100 Subject: [PATCH 09/14] Update virtualization-vmware2-vm.md --- .../procedures/virtualization-vmware2-vm.md | 62 +++++++++---------- 1 file changed, 31 insertions(+), 31 deletions(-) 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 2e5c8c2a1269..2da37bab4821 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 @@ -686,9 +686,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:---------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to monitor. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. Exemple : --vm-hostname='^((VM-PROD-*))' --filter | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on the devices' names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | @@ -704,14 +704,14 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on their names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | | --datastore-name | Datastore to check. If not set, we check all datastores. | -| --filter-datastore | Datastore name is a regexp. | +| --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} | @@ -724,9 +724,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on the devices' names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | @@ -744,9 +744,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:-------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on the devices' names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --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} | @@ -762,9 +762,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on the devices' names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | @@ -783,9 +783,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on the devices' names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | @@ -804,9 +804,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on the devices' names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | @@ -823,9 +823,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on the devices' names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | @@ -842,9 +842,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:--------------------------|:---------------------------------------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on the devices' names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | @@ -859,9 +859,9 @@ Les options disponibles pour chaque modèle de services sont listées ci-dessous | Option | Description | |:----------------------------|:--------------------------------------------------------------| | --vm-hostname | Hostname of the VM to check. If not set, we check all VMs. | -| --filter | VM hostname is a regexp. | -| --filter-description | Filter also virtual machines description (can be a regexp). | -| --filter-os | Filter also virtual machines OS name (can be a regexp). | +| --filter | Define which VMs should be monitored based on the devices' names. This option will be treated as a regular expression. | +| --filter-description | Define which VMs should be monitored based on their description. This option will be treated as a regular expression. | +| --filter-os | Define which VMs should be monitored based on their OS. This option will be treated as a regular expression. | | --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). | From 30df7ea7865a0292844dc63c643310e0aad8f2e7 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 1 Mar 2024 17:51:22 +0100 Subject: [PATCH 10/14] Update virtualization-vmware2-vm.md --- .../procedures/virtualization-vmware2-vm.md | 32 +++++++++---------- 1 file changed, 16 insertions(+), 16 deletions(-) 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 2da37bab4821..9792f7150fc4 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 @@ -176,9 +176,9 @@ Voici le tableau des services pour ce connecteur, détaillant les métriques rat ## Prérequis -### Configuration du connecteur Centreon VMWare +### Configuration du daemon Centreon VMware -Pour la supervision VMWare, centreon utlise un daemon pour se connecter et requêter le vCenter. +Pour la supervision VMware, Centreon utilise un daemon pour se connecter et requêter le vCenter (ou les ESX, mais il est recommandé de passer par le vCenter). Installer le daemon sur tous les pollers : @@ -199,7 +199,7 @@ yum install centreon-plugin-Virtualization-VMWare-daemon -Pour configurer les accès à votre infrastructure, éditer le fichier +Pour configurer les accès à votre infrastructure, éditez le fichier "/etc/centreon/centreon\_vmware.pm" : ``` perl @@ -216,10 +216,10 @@ Pour configurer les accès à votre infrastructure, éditer le fichier 1; ``` -Assurez vous d'avoir remplacé toutes les variables avec les informations nécessaires : +Assurez-vous d'avoir remplacé toutes les variables avec les informations nécessaires : -- _ip\_hostname_: Adresse IP ou nom d'hôte du vCenter ou de l'ESX (Si il est en mode standalone), -- _username_: utilisateur avec un accès "lecture seul" au vCenter ou à l'ESX (Vous pouvez utilisez un utilisateur du domaine), +- _ip\_hostname_: Adresse IP ou nom d'hôte du vCenter ou de l'ESX (s'il est en mode standalone), +- _username_: utilisateur avec un accès "lecture seule" au vCenter ou à l'ESX (vous pouvez utiliser un utilisateur du domaine), - _password_: le mot de passe de l'utilisateur. Vous pouvez configurer plusieurs connexions à différents vCenter ou ESX @@ -245,7 +245,7 @@ en utilisant cette structure: 1; ``` -Chaque entrée est un **container**. +Chaque entrée est appelée un **container** (il correspond à la macro d'hôte `$_HOSTCENTREONVMWARECONTAINER$`). Pour démarrer le daemon et l'activer au démarrage : @@ -257,7 +257,7 @@ systemctl enable centreon_vmware Vous pouvez vérifiez que votre configuration est fonctionelle en consultant les journaux dans : "/var/log/centreon/centreon\_vmware.log". -### Balises et Attributs personnalisés +### Balises et attributs personnalisés Pour découvrir les balises et les attributs personnalisés, vous devez : @@ -266,9 +266,9 @@ Pour découvrir les balises et les attributs personnalisés, vous devez : ### Flux réseau -Le Collecteur Centreon avec le connecteur VMWare d'installé doit accéder en HTTPS (TCP/443) au vCenter. +Le collecteur Centreon (avec le daemon VMWare installé dessus) doit accéder en HTTPS (TCP/443) au vCenter. -Les collecteurs requêtant le collecteur avec le connecteur VMWare doivent accéder en TCP/5700 au collecteur avec le connecteur VMWare. +Si plusieurs collecteurs de supervision utilisent un même daemon, alors ceux-ci doivent accéder en TCP/5700 au collecteur équipé du daemon VMware. ## Installer le connecteur de supervision @@ -367,10 +367,10 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Valeur par défaut | Obligatoire | |:---------------------------|:------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| CENTREONVMWAREPORT | Connector port (default: 5700). | 5700 | | -| CENTREONVMWARECONTAINER | Container to use (it depends on the connector's configuration). | default | | -| CENTREONVMWAREHOST | Connector hostname (required). | localhost |X | -| VMNAME | Hostname of the VM to monitor. If not set, we check all VMs. | | | +| CENTREONVMWAREPORT | Port of the daemon (default: 5700). | 5700 | | +| CENTREONVMWARECONTAINER | Container to use (it depends on the daemon's configuration). | default | | +| CENTREONVMWAREHOST | Hostname of the server on which the daemon is installed (required). | localhost |X | +| VMNAME | Name of the VM to monitor. If not set, we check all VMs. | | | | VMUUID | Specify the VM's UUID. | | | | CENTREONVMWAREEXTRAOPTIONS | Any extra option you may want to add to every command (e.g. a --verbose flag). Toutes les options sont listées [ici](#options-disponibles) | | | @@ -662,8 +662,8 @@ Les options génériques 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'. | -| --connector-hostname | Connector hostname (required). | -| --connector-port | Connector port (default: 5700). | +| --connector-hostname | Hostname of the server on which the daemon is installed (required). | +| --connector-port | Port on which the daemon is listening (default: 5700). | | --container | Container to use (it depends on the connector's configuration). | | --vsphere-address | Address of the vpshere/ESX instance to connect to. | | --vsphere-username | Username to use to connect to the vpshere/ESX instance (with --vsphere-address). | From 999f38a2ad6963659bd037e523e7feb853da3038 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 1 Mar 2024 17:55:12 +0100 Subject: [PATCH 11/14] Update i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md --- .../plugin-packs/procedures/virtualization-vmware2-vm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 9792f7150fc4..4dfa02dd2348 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 @@ -7,7 +7,7 @@ import TabItem from '@theme/TabItem'; ## Vue d'ensemble -VMWare est une solution de Virtualisation et d'infrastructure de Cloud Computing. +VMware est une solution de virtualisation et d'infrastructure de Cloud Computing. Le connecteur de supervision Centreon s'appuie sur le SDK VMWare pour requêter l'API du vCenter au travers d'un connecteur dédié. From 08a3468e6e97b7f244cd82441f998ad814712469 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 1 Mar 2024 17:55:58 +0100 Subject: [PATCH 12/14] Update i18n/fr/docusaurus-plugin-content-docs-pp/current/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md --- .../plugin-packs/procedures/virtualization-vmware2-vm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 4dfa02dd2348..f354639da564 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 @@ -9,7 +9,7 @@ import TabItem from '@theme/TabItem'; VMware est une solution de virtualisation et d'infrastructure de Cloud Computing. -Le connecteur de supervision Centreon s'appuie sur le SDK VMWare pour requêter l'API du vCenter au travers d'un connecteur dédié. +Le connecteur de supervision Centreon s'appuie sur un connecteur dédié (centreon-vmware-daemon) utilisant le SDK VMware pour requêter l'API du vCenter. Il permet de superviser des machines virtuelles VMware. ## Contenu du pack From 339394e3f34dd37f51e23c540ed3df5ba02657e4 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 1 Mar 2024 18:09:06 +0100 Subject: [PATCH 13/14] Update virtualization-vmware2-vm.md --- .../procedures/virtualization-vmware2-vm.md | 34 +++++++++---------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md index bcf6075af029..18f649de3a9c 100644 --- a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md +++ b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md @@ -7,9 +7,9 @@ import TabItem from '@theme/TabItem'; ## Overview -VMware is an software compagny based in USA. VMware provides cloud computing and virtualization software and services. +VMware provides cloud computing and virtualization software. -The Centreon Plugin and Monitoring Connectors rely on the Centreon VMWare Connector to request the vCenter SDK. +The Centreon **VMware VM** Monitoring Connector relies on a dedicated connector (centreon-vmware-daemon) that uses the VMware SDK to send requests to the vCenter's API. It allows you to monitor VMware virtual machines. ## Pack assets @@ -175,9 +175,9 @@ Here is the list of services for this connector, detailing all metrics linked to ## Prerequisites -### Centreon VMWare Connector +### Centreon VMware daemon -For the VMWare monitoring, Centreon use daemon to connect and request the vCenter. +To monitor VMWare resources, Centreon uses a daemon to connect to and send requests to the vCenter (or the ESX, but it is recommended to use the vCenter). Install this daemon on each needed poller: @@ -216,11 +216,11 @@ To configure the access to your infrastructure, edit the 1; ``` -Make sure to replace variables with needed information: +Make sure to replace the variables with the necessary information: - _ip\_hostname_: IP address or hostname of the vCenter or ESX (if standalone), -- _username_: username with at least "read only" access to the vCenter or ESX (you can use domain user), -- _password_: password of the username. +- _username_: username with at least "read only" access to the vCenter or ESX (you can use a domain user), +- _password_: password for this user. You can configure multiple vCenter or ESXi connections using this structure: @@ -245,9 +245,9 @@ structure: 1; ``` -Each entry is called a **container**. +Each entry is called a **container** (it corresponds to the `$_HOSTCENTREONVMWARECONTAINER$` host macro). -> You can also define the "port" attribute to change listening port. +> You can also define the "port" attribute to change the listening port. Then start the daemon and make sure it is configured to start at server boot: @@ -259,18 +259,18 @@ systemctl enable centreon_vmware Make sure that the daemon configuration works fine by looking for errors in "/var/log/centreon/centreon\_vmware.log". -### Tags and Custom Attributes +### Tags and custom attributes -To discover Tags and Custom Attributes, you must : +To discover tags and custom attributes, you must : * use version **3.2.5** of **centreon-vmware-daemon** * add **--tags** in the additional discovery options: go to the **Configuration > Hosts > Discovery** page, and to the 3rd step (**Set discovery parameters**), in the section **Additional parameters**, in the **Additional options** field, type **--tags**. ### Network flows -The Poller with the Centreon VMware Connector installed need to access in TCP/443 HTTPS to the Vcenter. +The Centreon poller (with the VMWare daemon installed on it) needs to access the vCenter using HTTPS (TCP/443). -Pollers requesting data from the Centreon VMware Connector must establish TCP connections on port 5700 to communicate with the Connector's host. +If several pollers use the same daemon, then they must access the poller that has the VMware daemon installed on it using TCP/5700. ## Installing the monitoring connector @@ -371,10 +371,10 @@ yum install centreon-plugin-Virtualization-Vmware2-Connector-Plugin | Macro | Description | Default value | Mandatory | |:---------------------------|:------------------------------------------------------------------------------------------------------|:------------------|:-----------:| -| CENTREONVMWAREPORT | Connector port (default: 5700) | 5700 | | -| CENTREONVMWARECONTAINER | Container to use (it depends on the connector's configuration) | default | | -| CENTREONVMWAREHOST | Connector hostname (required) | localhost | X | -| VMNAME | Hostname of the VM to check. If not set, we check all VMs | | | +| CENTREONVMWAREPORT | Port of the daemon (default: 5700) | 5700 | | +| CENTREONVMWARECONTAINER | Container to use (it depends on the daemon's configuration) | default | | +| CENTREONVMWAREHOST | Hostname of the server on which the daemon is installed (required) | localhost | X | +| VMNAME | Name of the VM to check. If not defined, all VMs will be checked. | | | | VMUUID | Specify the VM's UUID | | | | CENTREONVMWAREEXTRAOPTIONS | Any extra option you may want to add to every command (e.g. a --verbose flag). All options are listed [here](#available-options) | | | From e251118489b040e1f97eb0b6a0ab3bb683d0a123 Mon Sep 17 00:00:00 2001 From: omercier <32134301+omercier@users.noreply.github.com> Date: Tue, 5 Mar 2024 17:42:18 +0100 Subject: [PATCH 14/14] Apply suggestions from code review --- .../plugin-packs/procedures/virtualization-vmware2-vm.md | 2 -- .../plugin-packs/procedures/virtualization-vmware2-vm.md | 2 -- 2 files changed, 4 deletions(-) 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 f354639da564..a0c2105ac63b 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 @@ -5,8 +5,6 @@ title: VMware VM import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -## Vue d'ensemble - VMware est une solution de virtualisation et d'infrastructure de Cloud Computing. Le connecteur de supervision Centreon s'appuie sur un connecteur dédié (centreon-vmware-daemon) utilisant le SDK VMware pour requêter l'API du vCenter. Il permet de superviser des machines virtuelles VMware. diff --git a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md index 18f649de3a9c..5411d41d8f3a 100644 --- a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md +++ b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm.md @@ -5,8 +5,6 @@ title: VMware VM import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -## Overview - VMware provides cloud computing and virtualization software. The Centreon **VMware VM** Monitoring Connector relies on a dedicated connector (centreon-vmware-daemon) that uses the VMware SDK to send requests to the vCenter's API. It allows you to monitor VMware virtual machines.