What is a one sentence summary of your feature request?
Allow IHM login information to be logged at the INF verbosity level to enable connection reporting without requiring higher log levels in production.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
Hello,
As part of a request from our client, they would like to enhance the logging of IHM (NIM) login activity.
Historically, a connection report was generated using a script that parsed application logs, specifically extracting the “SubjectId” information. The script identified and processed relevant log lines to track user login activity.
This report is no longer operational, and a manual review of the logs confirmed that the previously available lines are no longer present.
However, some potentially useful information is still available at higher verbosity levels:
[DBG]: GetFilter User=SXXXX Permission=/Jobs/Job/Query EntityType=Job […] Decision=(Allowed)
[VRB]: SqlReader […] @PID Parameters [{“Name”:“@PID”,“Type”:“System.String”,“Value”:“PXXXX”}]
To meet the client’s need, would it be possible:
-
To also include this information at the INF log level;
-
Or alternatively, to log explicit IHM login activity at this verbosity level?
This would allow the client to restore their connection reporting without relying on higher log verbosity in production.
How do you currently solve the challenges you have by not having this feature?
Not solved currently