Login Audit Report

Hi Yagyadeepak-
Have a look over this component: forum.appian.com/.../summary

This will return the similar data elements you want to show in your report - you can have the process created using the above smart service that will populate your data elements/information in your database and use that database to map your entities with and pull the information out to create the desired tempo reports on Appian.

Hope this helps.

Thanks siddharth , but the approach suggested will be dependent on a batch process to populate the login table with the login information as a result which will not be real time. The aim for this report is business activity monitoring and it not being real time will not justify its purpose.

@yagyadeepk An alternate is the plugin at forum.appian.com/.../summary

@yagyadeepk Refer the post at /search?q=OriginalPostID-222173 as the plugin mentioned by me has some issues.

While reading log files you will obtain the uuid of user instead of username and the post at /search?q=OriginalPostID-203272 should help you on this. Also, I have found that the plugin mentioned by me has sorting issues.

In case if you want to customise the plugin implementation, then the post at /search?q=OriginalPostID-232737 might give you an idea.

To capture real time data, we need to capture the login details as soon as some user tries to log into the Appian Instance and store that information in a database table. I am not sure if Appian exposes any such event that we can capture. Parsing the log files seems to be the best possible approach here. As the login data for all past days won't change, it makes sense to read the login-audit file once a day after the completion of that day. But if you can do with almost real time data, then parsing the current day login file after every few hours might be a viable option.

Hi Yagyadeep - We have already built this kind report as part of ugliman. If intereseted please reach me.

Hi Yagyadeep, You can refer the attached document. This will help you a lot.

Login Details.docx