This is a quick-reference guide outlining typical monitoring best practices for a Semarchy deployment. As with any monitoring effort, the ideal is to preemptively find problems before they effect a production environment.
Third-party infrastructure:
...
- Semarchy
- Reach App Server and successfully login (This is a simple test that can tell you the app server is running, the DB is running and they can talk to each other).
- Login successfully
- This is one step beyond connectivity and ensures a proper level of configuration between the app server, DB and authentication provider.
- Viewing golden record
- This forces other queries into the DB.
- Monitor Semarchy task staus
- This can be monitored in the UI, via Admin Console -> Execution Engine Console. This will show both the status of the execution engine AND what is currently running and/or queued up.
- In addition, the all jobs are logged in the database in “Repo_Schema”.MTA_JOB_LOG which can be directly queried for errors or suspensions. Here is a list of possible Job statuses (MTA_JOB_LOG.STATUS: RUNNING, SUSPENDED, DONE, ERROR
- This can be monitored in the UI, via Admin Console -> Execution Engine Console. This will show both the status of the execution engine AND what is currently running and/or queued up.