irules logs

iRules will generally log to /var/log/ltm

 

-Seth

 

If a runtime exception is thrown from an iRule, it will go to /var/log/ltm (unless you changed the syslog-ng configuration). If you use the

log

command, the destination will depend on two things: 1. the declared facility; and 2. the syslog-ng config. By default, if you don't declare a facility (e.g., you say log "this is a message", then the facility is local0. Otherwise, you can (and really, should) declare the facility (e.g., log local2. "This is a message"). Where the message goes depends on the syslog-ng configuration. Most people don't mess with that (and generally, it's not a good idea). Assuming you have not, then this solution article explains the defaults:

• SOL13317: Configuring the level of information that syslog-ng sends to log files (11.x - 12.x)

If you are logging non-debug message from an iRule, you should strongly consider using High-Speed Logging instead of the

log

command:

• High Speed Logging

If a runtime exception is thrown from an iRule, it will go to /var/log/ltm (unless you changed the syslog-ng configuration). If you use the

log

command, the destination will depend on two things: 1. the declared facility; and 2. the syslog-ng config. By default, if you don't declare a facility (e.g., you say log "this is a message", then the facility is local0. Otherwise, you can (and really, should) declare the facility (e.g., log local2. "This is a message"). Where the message goes depends on the syslog-ng configuration. Most people don't mess with that (and generally, it's not a good idea). Assuming you have not, then this solution article explains the defaults:

• SOL13317: Configuring the level of information that syslog-ng sends to log files (11.x - 12.x)

If you are logging non-debug message from an iRule, you should strongly consider using High-Speed Logging instead of the

log

command:

• High Speed Logging