Forum Discussion

Amit585731's avatar
Amit585731
Icon for Nimbostratus rankNimbostratus
Apr 30, 2015

Regarding alert.conf

Hi,

 

It seems alert.conf files have many alerts configured which I think is not required for F5 LTM. Is there any link which can help me identify which will be correct alert required for LTM only. Or can I go ahead and configure all alert?

 

Or is it fine I can ignore those and configure these pre configured syslog alert:

 

alert BIGIP_LOG_EMERG "^[0-9a-f]{8}:0: (.)" { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.29" } alert BIGIP_LOG_ALERT "^[0-9a-f]{8}:1: (.)" { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.30" } alert BIGIP_LOG_CRIT "^[0-9a-f]{8}:2: (.*)" { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.31" } alert BIGIP_LOG_ERR "^[0-9a-f]{8}:3: (.)" { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.32" } alert BIGIP_LOG_WARNING "^[0-9a-f]{8}:4: (.)" { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.33" }

 

Thanks

 

application delivery
deployment
LTM

1 Reply

  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    May 02, 2015

    i may be confused but i understand alertd is based on log. you shouldn't get alert about module you are not using (because there is no log), should you?

     

    by the way, you can check all the logs alertd monitors in /var/run/bigip_error_maps.dat.

     

    sol6420: The /var/run/bigip_error_maps.dat file maps the alertd process input from the syslog-ng utility to an alert name

     

    https://support.f5.com/kb/en-us/solutions/public/6000/400/sol6420.html