Pandora FMS Community

[Solved] Windows Eventlog Monitoring problem

JeeSee · 12 nov 2009, 17:07 · 5 mensajes · 56 visitas

  1. Inicio del debate

    Pandora FMS version: 2.1 Windows Agent 2.1 In the Windows Agent pandora_agent.conf I've added the following lines to monitor the Windows System Eventlog and Application Eventlog for Error or Warnings:

    
    #Windows System Eventlog Error Messages monitoring
    module_begin
    module_name log_system_err
    module_type generic_data_string
    module_description System errors
    module_logevent
    module_source System
    module_eventtype error
    module_end
    
    #Windows System Eventlog Warning Messages monitoring
    module_begin
    module_name log_system_wrn
    module_type generic_data_string
    module_description System warnings
    module_logevent
    module_source System
    module_eventtype warning
    module_end
    
    #Windows Application Eventlog Error Messages monitoring
    module_begin
    module_name log_app_err
    module_type generic_data_string
    module_description Application errors
    module_logevent
    module_source Application
    module_eventtype error
    module_end
    
    #Windows Application Eventlog Warning Messages monitoring
    module_begin
    module_name log_app_wrn
    module_type generic_data_string
    module_description Application warnings
    module_logevent
    module_source Application
    module_eventtype warning
    module_end
    

    After that I restarted the Pandora Agent service and deleted the Agent in the Pandora FMS Webconsole. After a little time the Agent is found by Pandora FMS Webconsole, including some modules I configured in the pandora_agent.conf file, but the logevent modules aren't shown. When I send a testevent to the machine, to log an ERROR-event, it is shown in the application Eventlog on the Windows system, but not in Pandora FMS Console. What's wrong with the above configuration? We only need to monitor Errors/Warning from the Eventlogs from our Windows Agents. Any help would be welcome

  2. Eventlog module is initialized after an Event occurs. When there are no events, the module stays uninitialized till there's an Event.

  3. Eventlog module is initialized after an Event occurs. When there are no events, the module stays uninitialized till there's an Event.

    Exactly, that's the standard behaviour.

  4. I add the same code as below and only application is working .. the system is not initialized module: #Windows System Eventlog Error Messages monitoring module_begin module_name log_system_err module_type generic_data_string module_description System errors module_logevent module_source System module_eventtype error module_end #Windows System Eventlog Warning Messages monitoring module_begin module_name log_system_wrn module_type generic_data_string module_description System warnings module_logevent module_source System module_eventtype warning module_end #Windows Application Eventlog Error Messages monitoring module_begin module_name log_app_err module_type generic_data_string module_description Application errors module_logevent module_source Application module_eventtype error module_end #Windows Application Eventlog Warning Messages monitoring module_begin module_name log_app_wrn module_type generic_data_string module_description Application warnings module_logevent module_source Application module_eventtype warning module_end

  5. Btw did you ever tried to receive alerts ie email for this modules ?

Entra en tu cuenta para publicar.