{"id":353778,"date":"2024-09-03T13:55:03","date_gmt":"2024-09-03T13:55:03","guid":{"rendered":"https:\/\/www.ninjaone.com\/script-hub\/monitorizar-el-estado-del-nodo-proxmox\/"},"modified":"2024-10-13T19:06:24","modified_gmt":"2024-10-13T19:06:24","slug":"monitorizar-el-estado-del-nodo-proxmox","status":"publish","type":"script_hub","link":"https:\/\/www.ninjaone.com\/es\/script-hub\/monitorizar-el-estado-del-nodo-proxmox\/","title":{"rendered":"C\u00f3mo monitorizar el estado del nodo Proxmox con un script Bash automatizado"},"content":{"rendered":"

La gesti\u00f3n eficiente de la infraestructura inform\u00e1tica es crucial para mantener la estabilidad y el rendimiento del entorno digital de una organizaci\u00f3n. Una de las tareas esenciales para los profesionales de TI y los proveedores de servicios gestionados (MSP)<\/a> es monitorizar el estado del nodo Proxmox Virtual Environment (PVE). El script proporcionado ofrece una soluci\u00f3n s\u00f3lida para automatizar este proceso, garantizando que la informaci\u00f3n sobre el estado de los nodos est\u00e9 disponible y actualizada.<\/p>\n

Background<\/h2>\n

Proxmox VE es un entorno de virtualizaci\u00f3n de servidores de c\u00f3digo abierto utilizado por muchos profesionales de TI para gestionar m\u00e1quinas virtuales, contenedores y almacenamiento. La supervisi\u00f3n del estado de los nodos dentro de un cl\u00faster Proxmox es fundamental para el mantenimiento proactivo y la soluci\u00f3n de problemas.<\/p>\n

Este script para monitorizar el estado del nodo Proxmox simplifica el proceso recuperando informaci\u00f3n sobre el estado de los nodos y guard\u00e1ndola en campos personalizados para facilitar el acceso y el an\u00e1lisis. Esta automatizaci\u00f3n es especialmente valiosa para los MSP que gestionan entornos de m\u00faltiples clientes, ya que reduce el esfuerzo manual y minimiza el riesgo de supervisi\u00f3n.<\/p>\n

El script para monitorizar el estado del nodo Proxmox<\/h2>\n
#!\/usr\/bin\/env bash\r\n\r\n# Description: Get the Proxmox Node 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\n# Check if the custom fields are set to null\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\n# Check if the custom fields are the same\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\n# Check if the custom fields are not set\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 pvesh &>\/dev\/null; then\r\n    echo \"[Error] The Proxmox VE API tool 'pvesh' 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# Get the version of proxmox-ve\r\n_version=$(pveversion --verbose | grep \"proxmox-ve\" | awk '{print $2}')\r\n\r\n# Check if the version\r\nif [[ \"$(echo \"${_version}\" | awk -F. '{print $1}')\" -eq 7 ]]; then\r\n    echo \"[Info] Proxmox VE $_version is greater than or equal to 8.\"\r\nelse\r\n    echo \"[Warn] Proxmox VE $_version is less than 8. Some data may not be formatted as expected. See: https:\/\/pve.proxmox.com\/pve-docs\/chapter-pve-faq.html#faq-support-table\"\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 pvesh command to get the status information\r\nif ! pvesh_status_output=$(pvesh get \/cluster\/status --noborder); then\r\n    echo \"[Error] Failed to get the Proxmox Node Status.\"\r\n    echo \"$pvesh_status_output\"\r\n    exit 1\r\nfi\r\n# Example Output from: pvesh get \/cluster\/status --noborder\r\n# id        name     type    ip            level local nodeid nodes online quorate version\r\n# cluster   cluster1 cluster                                      4        1       4\r\n# node\/pve1 pve1     node    192.168.1.10  c     0          1       1\r\n# node\/pve2 pve2     node    192.168.1.20  c     0          2       1\r\n# node\/pve3 pve3     node    192.168.1.30  c     0          3       1\r\n# node\/pve4 pve4     node    192.168.1.40  c     1          4       1\r\n\r\n# Exclude the cluster information then skip the first line\r\nnode_status=$(echo \"$pvesh_status_output\" | grep -v \"cluster\" | tail -n +2)\r\n\r\n# Create a table with the node status information with only the columns named id, name, ip, and online\r\nif [[ \"$(echo \"${_version}\" | awk -F. '{print $1}')\" -ge 8 ]]; then\r\n    data_table=$(echo \"$node_status\" | awk '{print $7, $2, $4, $8}' | column -t)\r\nelse\r\n    data_table=$(echo \"$node_status\" | awk '{print $7, $2, $4, $7}' | column -t)\r\nfi\r\n\r\n# Convert the table to an HTML table with headers\r\nresult_table=$(echo \"$data_table\" | awk 'BEGIN {print \"<table style=\\\"white-space:nowrap;\\\"><tr><th>Node ID<\/th><th>Node Name<\/th><th>IP Address<\/th><th>Online Status<\/th><th>Votes<\/th><\/tr>\"} {print \"<tr>\"; for(i=1;i<=NF;i++) print \"<td>\" $i \"<\/td>\"; print \"<td>1<\/td><\/tr>\"} END {print \"<\/table>\"}')\r\n\r\n# Save the result to the WYSIWYG custom field\r\nif [[ -n \"$wysiwyg_custom_field\" ]]; then\r\n    # Check if the NinjaRMM CLI exists and is executable\r\n    if [[ -x \"$ninjarmm_cli\" ]]; then\r\n        # Save the result to the custom field\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# Format the output for the multiline custom field\r\npvesh_status_output=$(\r\n    # Exclude the cluster information then skip the first line\r\n    echo \"$data_table\" | awk '{if (NR == 1) print \"--------\"; print \"Node ID: \" $1 \"\\nNode Name: \" $2 \"\\nIP Address: \" $3 \"\\nOnline Status: \" $4 \"\\nVotes: 1\\n\"; if (NR != NF) print \"--------\"}'\r\n)\r\n\r\n# Save the result to the multiline 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\" \"$pvesh_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\n# Output the result\r\necho \"${pvesh_status_output}\"\r\n\r\nexit $_exit_code<\/pre>\n
 <\/p>\n\n
<\/div>\n
An\u00e1lisis detallado<\/h2>\n
El script est\u00e1 dise\u00f1ado para monitorizar el estado del nodo Proxmox y guardar la informaci\u00f3n en un campo personalizado multil\u00ednea o en un campo personalizado WYSIWYG. Desglosemos su funcionalidad paso a paso:<\/p>\n
1. Argumentos de la l\u00ednea de comandos<\/strong><\/p>\n