Great! Thanks for confirming the solution. Also we are trying several different methods to try and get the exact solution that is needed in Phase 2 Security Log Solution Targeting on the frontend of the site so that it is logged with the exact solution in the Security Log, but we keep running into a website performance problem. A website performance decrease of even .1 (point 1) seconds is not acceptable so it is looking like the backend troubleshooting tool is going to be the only way to go.
– The Security Log searched by Event Code. Phase 2 development is looking at using the Event Codes in a troubleshooting tool that will extract log entries and automatically generate the solution. Since this is a user initiated processing tool in the protected backend of a site it does not have the potentional of being abused if this was automated on the frontend of the site by the Security Logging mechanisms/processing.
-
This reply was modified 8 hours, 8 minutes ago by
![Avatar of AITpro Admin]()
AITpro Admin.
-
This reply was modified 8 hours, 6 minutes ago by
![Avatar of AITpro Admin]()
AITpro Admin.
