Forum Discussion
Martin_Vlasko
Jul 02, 2014Altocumulus
Kevin, you are right.
It works fine when I remove the iRule Event object from APM policy and instead trigger the iRule directly in LTM with CLIENT_ACCEPTED event.
This solved my issue.
On the other hand it would be great to have the iRule triggered via APM policy, to have everything in one place. Let's see whether F5 comes back with the bug fix.
Now when I don't access APM variables in my iRule ([ACCESS::session data get session.user.sessionid]), what would be the best solution for pairing the LTM and APM logs of each particular session? Until now I was relying on APM session ID but I am not sure I could get it in the current iRule.