Note: Thumbnails are clickable for larger screenshots.
Samples of some monitoring and reporting tools I built primarily for internal use.
Browser logging by user to help troubleshoot any issues that may be caused by untested or unsupported (older) browser versions:
Active users session count to see how many users would be affected by server/services restart:
Users can be disabled in the system, this report lists users marked as enabled but who have not logged in within the last 12 months:
Internal report to see login history of users over a range of time, to determine average peak load times and estimate when user support will be higher than normal:
Internal report that shows user logins of all browser types / versions (as compared to only the newest browser version in report above):
Internal report of the browser versions spread. It is simplified since internet explorer is the only supported version for the system.
When diagnosing system issues for clients, I kept a list of scripts for specific issues. If the issue occurred more than a couple times, I sometimes built an internal use tool to troubleshoot more quickly since the client often had deadlines to meet and our response time was important. The client originally used a hand written checklist each time they went through the process. They later asked us to give them access to our tool that shows what steps in the process they missed, since the original system design did not enforce all of them. This was built as a simple solution because they did not want us to revise the system process to properly enforce prerequisites.
