Request Logging Other (APM) Information

I think there isn't any way to get your request logging profile into your APM module.

When the log is done, you can make a log filter and forward it to your log publisher.

The request logging profile is a little odd with an APM profile, as it generally triggers on every request, even the ones that should be hidden inside the APM access session evaluation. That said, you could technically create a set of HTTP headers that the request logging profile can consume, and then delete them just before sending the traffic off to the server.

when ACCESS_ACL_ALLOWED {
    HTTP::header insert "USER" [ACCESS::session data get session.logon.last.username]
}
when HTTP_REQUEST_RELEASE {
    HTTP::header remove "USER"
}

And then in the request logging profile, you'd just capture ${USER}. I think though, for the complexity of this, that you're probably better off doing HSL in an iRule to capture what you want.

Hi,

I had the same need and the first solution I found was to configure ACL with log "packet" and create a log filter to send cal log to HSL pool.

the problem with ACL log is there is no username information but session ID and I needed to create a correlation tool to match username / session ID / ACL.

After reading the Kevin's irule, I modified it to log RESPONSE instead of REQUEST to get response code.

The new irule is :

when CLIENT_ACCEPTED {
    set user "-"
}

when ACCESS_ACL_ALLOWED {
    set user [ACCESS::session data get session.logon.last.username]
}

when HTTP_RESPONSE {
    HTTP::header insert "USER" $user
}

when HTTP_RESPONSE_RELEASE {
    HTTP::header remove "USER"
}

The "-" default value is to replace username by - if request is not authenticated. I configured RESPONSE Template with:

$CLIENT_IP - ${USER} $DATE_NCSA $HTTP_REQUEST $HTTP_STATCODE $RESPONSE_SIZE $Referer 0 $Cookie

This is the NCSA_COMBINED template with the second "-" replaced by ${USER}