{"id":353716,"date":"2024-08-20T06:23:38","date_gmt":"2024-08-20T06:23:38","guid":{"rendered":"https:\/\/www.ninjaone.com\/script-hub\/monitoraggio-dello-stato-dei-cluster-proxmox-in-linux\/"},"modified":"2024-10-13T19:06:50","modified_gmt":"2024-10-13T19:06:50","slug":"monitoraggio-dello-stato-dei-cluster-proxmox-in-linux","status":"publish","type":"script_hub","link":"https:\/\/www.ninjaone.com\/it\/script-hub\/monitoraggio-dello-stato-dei-cluster-proxmox-in-linux\/","title":{"rendered":"Guida completa per il monitoraggio dello stato dei cluster Proxmox in Linux"},"content":{"rendered":"

Il mantenimento della stabilit\u00e0 e delle prestazioni di un cluster Proxmox \u00e8 fondamentale per i professionisti IT e i fornitori di servizi gestiti (MSP)<\/a>. Un cluster Proxmox offre numerosi vantaggi, tra cui alta disponibilit\u00e0, gestione efficiente delle risorse e virtualizzazione completa. Tuttavia, il monitoraggio del suo stato \u00e8 essenziale per garantire un funzionamento regolare.<\/p>\n

In questo articolo analizzeremo uno script Bash progettato per ottenere lo stato del cluster Proxmox<\/strong> e salvarlo in un campo personalizzato. Esploreremo le funzionalit\u00e0 dello script, i potenziali casi d’uso, i confronti, le domande frequenti, le implicazioni e le best practice.<\/p>\n

Background<\/h2>\n

Proxmox Virtual Environment (VE) \u00e8 una soluzione open-source per la gestione della virtualizzazione dei server che consente ai professionisti IT di distribuire e gestire virtual machine e container. Il clustering in Proxmox \u00e8 una caratteristica fondamentale che consente a pi\u00f9 nodi Proxmox VE di lavorare insieme, fornendo alta disponibilit\u00e0 e bilanciamento del carico. Il monitoraggio dello stato del cluster \u00e8 fondamentale per mantenere l’integrit\u00e0 e le prestazioni dell’ambiente virtuale.<\/p>\n

Questo script \u00e8 pensato per i professionisti IT che hanno bisogno di un modo efficiente per monitorare i cluster Proxmox. Recupera lo stato del cluster e salva le informazioni in un campo personalizzato multilinea o in un campo personalizzato WYSIWYG, facilitando la gestione e la revisione dello stato di integrit\u00e0 del cluster.<\/p>\n

Lo script per monitorare lo stato dei cluster Proxmox<\/h2>\n
#!\/usr\/bin\/env bash\r\n\r\n# Description: Get the Proxmox Cluster Status and save it to a multiline and\/or WYSIWYG custom field\r\n#\r\n# Release Notes: Fixed 10% width bug.\r\n# By using this script, you indicate your acceptance of the following legal terms as well as our Terms of Use at https:\/\/www.ninjaone.com\/terms-of-use.\r\n# Ownership Rights: NinjaOne owns and will continue to own all right, title, and interest in and to the script (including the copyright). NinjaOne is giving you a limited license to use the script in accordance with these legal terms. \r\n# Use Limitation: You may only use the script for your legitimate personal or internal business purposes, and you may not share the script with another party. \r\n# Republication Prohibition: Under no circumstances are you permitted to re-publish the script in any script library or website belonging to or under the control of any other software provider. \r\n# Warranty Disclaimer: The script is provided \u201cas is\u201d and \u201cas available\u201d, without warranty of any kind. NinjaOne makes no promise or guarantee that the script will be free from defects or that it will meet your specific needs or expectations. \r\n# Assumption of Risk: Your use of the script is at your own risk. You acknowledge that there are certain inherent risks in using the script, and you understand and assume each of those risks. \r\n# Waiver and Release: You will not hold NinjaOne responsible for any adverse or unintended consequences resulting from your use of the script, and you waive any legal or equitable rights or remedies you may have against NinjaOne relating to your use of the script. \r\n# EULA: If you are a NinjaOne customer, your use of the script is subject to the End User License Agreement applicable to you (EULA).\r\n\r\n# Command line arguments, swap the numbers if you want the multiline custom field to be the second argument\r\nmultiline_custom_field=$1 # First argument is the multiline custom field name\r\nwysiwyg_custom_field=$2   # Second argument is the WYSIWYG custom field name\r\n\r\nif [[ -n \"${multilineCustomField}\" && \"${multilineCustomField}\" != \"null\" ]]; then\r\n    multiline_custom_field=$multilineCustomField\r\nfi\r\nif [[ -n \"${wysiwygCustomField}\" && \"${wysiwygCustomField}\" != \"null\" ]]; then\r\n    wysiwyg_custom_field=$wysiwygCustomField\r\nfi\r\n\r\nif [[ -n \"${multiline_custom_field}\" && \"${multiline_custom_field}\" == \"${wysiwyg_custom_field}\" ]]; then\r\n    echo \"[Error] multilineCustomField and wysiwygCustomField cannot be the same custom field.\"\r\n    exit 1\r\nfi\r\n\r\nif [[ -z \"${multiline_custom_field}\" ]]; then\r\n    echo \"[Info] multilineCustomField is not set.\"\r\nfi\r\nif [[ -z \"${wysiwyg_custom_field}\" ]]; then\r\n    echo \"[Info] wysiwygCustomField is not set.\"\r\nfi\r\n\r\n# Check that we have the required tools\r\nif ! command -v pvecm &>\/dev\/null; then\r\n    echo \"[Error] The Proxmox VE API tool 'pvecm' is required.\"\r\n    exit 1\r\nfi\r\n\r\n# Check that we are running as root\r\nif [[ $EUID -ne 0 ]]; then\r\n    echo \"[Error] This script must be run as root.\"\r\n    exit 1\r\nfi\r\n\r\n# Check if ninjarmm-cli command exists\r\nninjarmm_cli=\"\/opt\/NinjaRMMAgent\/programdata\/ninjarmm-cli\"\r\nif [[ -z $ninjarmm_cli ]]; then\r\n    echo \"[Error] The ninjarmm-cli command does not exist in the default path. Please ensure the NinjaRMM agent is installed before running this script.\"\r\n    exit 1\r\nelse\r\n    # ninjarmm-cli command exists in the default path\r\n    echo -n\r\nfi\r\n\r\n# Run the pvecm command to get the status information\r\nif ! pvecm_status_output=$(pvecm status); then\r\n    echo \"[Error] Failed to get the Proxmox Cluster Status.\"\r\n    echo \"$pvecm_status_output\"\r\n    exit 1\r\nfi\r\n# Example Output:\r\n# Cluster information\r\n# -------------------\r\n# Name:             cluster1\r\n# Config Version:   4\r\n# Transport:        knet\r\n# Secure auth:      on\r\n#\r\n# Quorum information\r\n# ------------------\r\n# Date:             Mon Apr  8 10:33:16 2024\r\n# Quorum provider:  corosync_votequorum\r\n# Nodes:            4\r\n# Node ID:          0x00000004\r\n# Ring ID:          1.631\r\n# Quorate:          Yes\r\n#\r\n# Votequorum information\r\n# ----------------------\r\n# Expected votes:   4\r\n# Highest expected: 4\r\n# Total votes:      4\r\n# Quorum:           3\r\n# Flags:            Quorate\r\n#\r\n# Membership information\r\n# ----------------------\r\n#     Nodeid      Votes Name\r\n# 0x00000001          1 10.10.10.17\r\n# 0x00000002          1 10.10.10.18\r\n# 0x00000003          1 10.10.10.19\r\n# 0x00000004          1 10.10.10.20 (local)\r\n\r\n# Cluster Table\r\n# Get the cluster name\r\ncluster_name=$(echo \"$pvecm_status_output\" | grep -oP 'Name:\\s+\\K\\w+' | head -n 1)\r\n# Get the Config Version\r\nconfig_version=$(echo \"$pvecm_status_output\" | grep -oP 'Config Version:\\s+\\K\\d+' | head -n 1)\r\n# Get the Transport\r\ntransport=$(echo \"$pvecm_status_output\" | grep -oP 'Transport:\\s+\\K\\w+' | head -n 1)\r\n# Get the Secure auth\r\nsecure_auth=$(echo \"$pvecm_status_output\" | grep -oP 'Secure auth:\\s+\\K\\w+' | head -n 1)\r\n\r\n# Create Cluster Status label\r\ncluster_table=\"<h2>Cluster Status<\/h2>\"\r\n# Create the Cluster Status table\r\ncluster_table+=\"<table style='white-space:nowrap;'><tr><th>Cluster Name<\/th><th>Config Version<\/th><th>Transport<\/th><th>Secure Auth<\/th><\/tr>\"\r\ncluster_table+=\"<tr><td>$cluster_name<\/td><td>$config_version<\/td><td>$transport<\/td><td>$secure_auth<\/td><\/tr><\/table>\"\r\n\r\n# Quorum Table\r\n# Get the Quorum Date\r\nquorum_date=$(echo \"$pvecm_status_output\" | grep -oP 'Date:\\s+\\K.*' | head -n 1)\r\n# Get the Quorum provider\r\nquorum_provider=$(echo \"$pvecm_status_output\" | grep -oP 'Quorum provider:\\s+\\K\\w+' | head -n 1)\r\n# Get the Nodes\r\nnodes=$(echo \"$pvecm_status_output\" | grep -oP 'Nodes:\\s+\\K\\d+' | head -n 1)\r\n# Get the Node ID\r\nnode_id=$(echo \"$pvecm_status_output\" | grep -oP 'Node ID:\\s+\\K\\w+' | head -n 1)\r\n# Get the Ring ID\r\nring_id=$(echo \"$pvecm_status_output\" | grep -oP 'Ring ID:\\s+\\K[\\d.]+')\r\n# Get the Quorate\r\nquorate=$(echo \"$pvecm_status_output\" | grep -oP 'Quorate:\\s+\\K\\w+')\r\n\r\n# Create Quorum Status label\r\nquorum_table=\"<h2>Quorum Status<\/h2>\"\r\n# Create the Quorum Status table\r\nquorum_table+=\"<table style='white-space:nowrap;'><tr><th>Quorum Date<\/th><th>Quorum Provider<\/th><th>Nodes<\/th><th>Node ID<\/th><th>Ring ID<\/th><th>Quorate<\/th><\/tr>\"\r\nquorum_table+=\"<tr><td>$quorum_date<\/td><td>$quorum_provider<\/td><td>$nodes<\/td><td>$node_id<\/td><td>$ring_id<\/td><td>$quorate<\/td><\/tr><\/table>\"\r\n\r\n# Votequorum Table\r\n# Get the Expected votes\r\nexpected_votes=$(echo \"$pvecm_status_output\" | grep -oP 'Expected votes:\\s+\\K\\d+')\r\n# Get the Highest expected\r\nhighest_expected=$(echo \"$pvecm_status_output\" | grep -oP 'Highest expected:\\s+\\K\\d+')\r\n# Get the Total votes\r\ntotal_votes=$(echo \"$pvecm_status_output\" | grep -oP 'Total votes:\\s+\\K\\d+')\r\n# Get the Quorum\r\nquorum=$(echo \"$pvecm_status_output\" | grep -oP 'Quorum:\\s+\\K\\d+')\r\n# Get the Flags\r\nflags=$(echo \"$pvecm_status_output\" | grep -oP 'Flags:\\s+\\K\\w+')\r\n\r\n# Create Votequorum Status label\r\nvotequorum_table=\"<h2>Votequorum Status<\/h2>\"\r\n# Create the Votequorum Status table\r\nvotequorum_table+=\"<table style='white-space:nowrap;'><tr><th>Expected Votes<\/th><th>Highest Expected<\/th><th>Total Votes<\/th><th>Quorum<\/th><th>Flags<\/th><\/tr>\"\r\nvotequorum_table+=\"<tr><td>$expected_votes<\/td><td>$highest_expected<\/td><td>$total_votes<\/td><td>$quorum<\/td><td>$flags<\/td><\/tr><\/table>\"\r\n\r\n# Get the Membership information table\r\nmemberships=$(echo \"$pvecm_status_output\" | grep -oP '0x000000\\d+\\s+\\d+\\s+\\d+\\.\\d+\\.\\d+\\.\\d+')\r\n# Split memberships into an array\r\nOLDIFS=$IFS\r\nIFS=$'\\n' read -r -d '' -a membership_array <<<\"$memberships\"\r\nIFS=$OLDIFS\r\n\r\n# Membership Table\r\n# Create Membership Status label\r\nmembership_table=\"<h2>Membership Status<\/h2>\"\r\n# Create the Membership Status table\r\nmembership_table+=\"<table style='white-space:nowrap;'><tr><th>Node ID<\/th><th>Votes<\/th><th>Name<\/th><\/tr>\"\r\nfor membership in \"${membership_array[@]}\"; do\r\n    node_id=$(echo \"$membership\" | grep -oP '0x000000\\d+')\r\n    votes=$(echo \"$membership\" | grep -oP '\\d+\\s+(?=\\d+\\.\\d+\\.\\d+\\.\\d+)')\r\n    name=$(echo \"$membership\" | grep -oP '\\d+\\.\\d+\\.\\d+\\.\\d+')\r\n    membership_table+=\"<tr><td>$node_id<\/td><td>$votes<\/td><td>$name<\/td><\/tr>\"\r\ndone\r\nmembership_table+=\"<\/table>\"\r\n\r\n# Combine all tables into one\r\nresult_table=\"$cluster_table<\/br>$quorum_table<\/br>$votequorum_table<\/br>$membership_table\"\r\n\r\n# Save the result to the custom field\r\n_exit_code=0\r\nif [[ -n \"$multiline_custom_field\" ]]; then\r\n    if [[ -x \"$ninjarmm_cli\" ]]; then\r\n        if hideOutput=$(\"$ninjarmm_cli\" set \"$multiline_custom_field\" \"$pvecm_status_output\" 2>&1); then\r\n            echo \"[Info] Successfully set custom field: $multiline_custom_field\"\r\n        else\r\n            echo \"[Error] Failed to set custom field: $multiline_custom_field. Custom Field does not exit or does not have write permissions.\"\r\n            _exit_code=1\r\n        fi\r\n    else\r\n        echo \"[Error] NinjaRMM CLI not found or not executable\"\r\n        _exit_code=1\r\n    fi\r\nfi\r\n\r\nif [[ -n \"$wysiwyg_custom_field\" ]]; then\r\n    if [[ -x \"$ninjarmm_cli\" ]]; then\r\n        if hideOutput=$(\"$ninjarmm_cli\" set \"$wysiwyg_custom_field\" \"$result_table\" 2>&1); then\r\n            echo \"[Info] Successfully set custom field: $wysiwyg_custom_field\"\r\n        else\r\n            echo \"[Error] Failed to set custom field: $wysiwyg_custom_field. Custom Field does not exit or does not have write permissions.\"\r\n            _exit_code=1\r\n        fi\r\n    else\r\n        echo \"[Error] NinjaRMM CLI not found or not executable\"\r\n        _exit_code=1\r\n    fi\r\nfi\r\n\r\n# Error out after checking both custom fields\r\nif [[ $_exit_code -ne 0 ]]; then\r\n    exit 1\r\nfi\r\n\r\n# Output the result if no custom fields are set\r\nif [[ -z \"${wysiwyg_custom_field}\" ]] && [[ -z \"${multiline_custom_field}\" ]]; then\r\n    echo \"${pvecm_status_output}\"\r\nfi<\/pre>\n
 <\/p>\n\n
<\/h2>
<\/p><\/div>
<\/a><\/div><\/div>\n
Analisi dettagliata<\/h2>\n
Analizziamo passo per passo lo script per monitorare lo stato dei cluster Proxmox per comprenderne il funzionamento e la logica.<\/p>\n
    \n
  1. Inizializzazione e argomenti della riga di comando: <\/strong>Lo script per monitorare lo stato dei cluster Proxmox inizia con due argomenti della riga di comando: i nomi dei campi personalizzati multilinea e WYSIWYG.<\/li>\n
  2. Convalida e configurazione: <\/strong>Convalida e assegna i valori ai campi personalizzati, assicurandosi che non siano nulli o identici.<\/li>\n
  3. Verifica della disponibilit\u00e0 degli strumenti e delle autorizzazioni: <\/strong>Lo script per monitorare lo stato dei cluster Proxmox controlla se gli strumenti necessari, come pvecm e ninjarmm-cli, sono disponibili e assicura che lo script venga eseguito con i privilegi di root.<\/li>\n
  4. Recupero e analisi dello stato del cluster: <\/strong>Esegue il comando pvecm status per recuperare lo stato del cluster e memorizza l’output in una variabile.<\/li>\n
  5. Estrazione delle informazioni rilevanti: <\/strong>Lo script per monitorare lo stato dei cluster Proxmox utilizza grep e le espressioni regolari per analizzare ed estrarre le informazioni rilevanti, come il nome del cluster, la versione della configurazione, il metodo di trasporto, lo stato dell’autenticazione sicura, le informazioni sul quorum e i dettagli dei membri.<\/li>\n
  6. Creazione di tabelle HTML: <\/strong>Lo script per monitorare lo stato dei cluster Proxmox formatta i dati estratti in tabelle HTML per una migliore leggibilit\u00e0 e organizzazione.<\/li>\n
  7. Salvataggio dei risultati in campi personalizzati: <\/strong>A seconda della disponibilit\u00e0 dei campi personalizzati, lo script per monitorare lo stato dei cluster Proxmox salva i risultati grezzi e formattati nei campi personalizzati specificati usando il comando ninjarmm-cli.<\/li>\n<\/ol>\n
    Casi d’uso potenziali<\/h2>\n
    Immagina un MSP che gestisce pi\u00f9 cluster Proxmox per vari clienti. Controllare e registrare regolarmente lo stato dei cluster pu\u00f2 richiedere molto tempo. Questo script automatizza il processo per monitorare lo stato dei cluster Proxmox, assicurando che le informazioni aggiornate sullo stato siano sempre disponibili in un formato strutturato. Per esempio, un professionista IT pu\u00f2 utilizzare questo script per:<\/p>\n