Hey Rajasekhar,
Based on your last statement, i'm assuming you've tried the above context variables and an entry isn't showing up in the Policy Manager's Audit Viewer ?
By default, Our Auditing System has a 'Message Threshold' of 'INFO', so any 'Audits' that are 'INFO' or lower won't get picked up. if you wish to see this info in the Audit viewer, you can manaully change the Severity of the audit in the 'add audit details' assertion you use to 'WARNING', which will breach the threshold and force an Audit.
a lot of people confuse our Auditing system as a Logging system and i just want to caution you of this. Audits are a Synchronous transaction to the database and can add a lot of overhead to the transaction latency and db. Auditing is meant to show you problems and issues. It's meant to be used in Error scenarios or Failure logic.
for development environments, this is okay, as many customer like our audit viewer dashboard, but moving beyond that with lots of auditing is a bad practice. I'd suggest firing these off to a 'Log Sink' or off box it to something like Splunk or the ELK stack.
hope this helps