Pandora FMS Community

module_min_warning and module_max_warning in pandora_agent.conf

neuroticimbecile · 17 may 2013, 15:17 · 8 mensajes · 54 visitas

  1. Inicio del debate

    Hi All, On the monitored server, I have: CentOS release 6.2 pandorafms_agent_unix-4.0.3-130118.noarch In /etc/pandora/pandora_agent.conf I have: ========== module_begin module_name Mail queue - Axigen module_type generic_data module_exec find /var/opt/axigen/queue/ -name "S*" -exec /opt/axigen/bin/mqview {} ; 2>/dev/null| grep -A1 'RCPT information for'| gre module_description Total messages in Axigen mail queue module_min_warning 500 module_max_warning 999 module_min_critical 1000 module_max_critical 99999 module_end ========== The new monitor shows up in the Pandora FMS web console (Pandora FMS v4.0.3 - Build PC130421), and the proper data values are displayed, but the status does not change to "warning" when the data becomes greater than 500.

  2. HI From 4.0.3 version, when you set max and min warning/critical in pandora_agent.conf after module is created in Console, this changes not affect to module configuration. Try to change this values in Pandora Console and chech if it is working. At the beginning of this release, there was a bug about this, but if you have updated Pandora Console this bug have to be resolved. Regards

  3. Hi, Pandora Console has already been upgraded to version "Pandora FMS v4.1 - Build PC130519". Some of the min and max warning/critical values in pandora_agent.conf were set before the modules were created in the Console, and yet these min and max values were also not detected by the Console.  Is there a way to make the Console re-scan the min and max values from the agents? Even the min/max warning/critical values of the built-in sample modules (e.g. "cpu_user", "Cache mem free", and "proctotal") in pandorafms_agent_unix are not detected by the Console. We have updated Pandora to the latest versions available via yum: pandorafms_agent_unix-4.1-130518.noarch pandorafms_console-4.1-130518.noarch pandorafms_server-4.1-130518.noarch BTW, setting the min/max warning/critical values using the Pandora Console works. But I was hoping this could be done from the agent's side. Thank you for your help.

  4. Thanks a lot! We're going to review it.

  5. Just updating this thread. We upgraded the console to version Pandora FMS v4.1 - Build PC130519 and the issue still has not been solved. The console is still not able to detect the following values from any of the software agents (in the file /etc/pandora/pandora_agent.conf):

    • module_min_warning
    • module_max_warning
    • module_min_critical
    • module_max_critical
  6. Hello Cesar I am testing with this module in this version and it is working fine. module_begin module_name Test module_type generic_data module_exec echo 50 module_min_warning 30 module_max_warning 60 module_min_critical 61 module_max_critical 100 module_end Check this module. Regards

  7. Hi Mario, Thank you for your reply. Upon testing, the web console now detects the warning and critical values from software agents if:

    • the software agent is deleted from the web console and then re-detected
    • the module is deleted from the web console and then re-detected

    The disadvantage is that all the data previously collected by the agent or module are deleted.

  8. Hi Yes, this is normal operation from version 4.0.3. From 4.0.3, Max-min critical and warning values in pandora_agent.conf are only configured the first time you create the modules. If you want to change these values​​, once the module is created, you have to change them in Pandora Console. Regards

Entra en tu cuenta para publicar.