Administrators have the ability to view various types of processes occurring within the system. Grid results are displayed in various tabs.

Events

The Events grid is filtered to the last 200 application events.  The types of events currently monitored by this option include:

• Slow Metric Events: 
• Recent repository events: database access, including queries, updates, creates, etc.
• Slow Queries:  queries that take longer than one second to complete.  
• Lifecycle events:  startup, shutdown, importing, etc.
• Recent exceptions
• Recent Auditable events:  Module installation, rules reloading, payroll posting, etc.
• Recent metric events:  elapsed time for events of interest

The admin can change the type of event displayed in the grid by utilizing the drop down box on the 'Event' display tab.

Status

The 'Status' display grid looks slightly different.  

The Status tab displays information about the status of the application, jobs, and installed modules.  Each job that runs during the import and post import process, along with the various modules that are installed are listed here along with their value.

Metrics

USXS Redesign applications have some built-in monitoring statistics.  A useful one for performance is Metrics.  For further details, please refer to Using System Monitor in the Technical Documentation

Logging

The Logging tab displays the name of each object in the application that has logging enabled.  This grid shows the effective logging level and also allows you to update that level to a higher, more detailed level of logging.  This is useful when attempting to track down a problem.  It's important to note that if a logging level is modified, once the problem has been determined the logging level should be set back to its original value.  Failure to do so will result in larger logs as there could be a significant amount of additional information being logged as a result.

The Logging Tab allows the overriding of logging levels in the app.  This is used by SSDT when debugging. 

The Toggle SQL button turns on/off logging for all queries.  This allows each database query to be logged for debugging.  Again if this is turned on it should be turned off when no longer needed.

Note: Debug Logs are included in the server logs when sent to SSDT. 

For further details, please refer to Authentication Troubleshooting in the Technical Documentation.

App Log

Server logs can be cleared when an app instance is restarted.  This makes the logs hit or miss if a district’s app is restarted to correct a problem.  The App Logs are a solution to this problem.  We store the logs in a database table so they are not lost on start.  This menu option is used by SSDT to debug issues, but it also stores Auditable Events and logging info that can be useful to ITC / users.  The Highlight Viewer can display the stack trace and errors.

Threads

Admin Logs

This tab contains the Classic Import Log.

This log should be reviewed as part of the Post Import Procedures. For more information on common exceptions see the USAS-R Common Import Errors and Warnings page.

Info 

The Info tab displays environment variables defined in the docker files, JVM information and also contains details about configuration files.

Security Logs

The security log grid will display all authentication events being saved to the database when users log in and out of the application.  The grid may be filtered and a report may be generated using the report button.  For further details, please refer to Authentication Troubleshooting in the Technical Documentation.

Server Logs

There are various logs generated by the application that can be downloaded by clicking the button under the Server Logs tab.

Application server log:     app-usas.web-docker.current.json.log 

Tomcat logs:

• • Catalina - tomcat server log
  • Localhost - tomcat access log
  • Manager - tomcat log (not currently being used)
  • Localhost_access_log - tomcat log to show all get and post request methods
  • Juli - internal logging for apache tomcat

Security logs:

• • example:   To download the Security logs for the current day security logging, click on:

To send a server log to the SSDT, go to the HELP menu and select ABOUT.  Scroll down to the bottom of the ABOUT page and click on the 'Send Server Log to the SSDT'.