Bizagi Diagnostics is a toolkit that provides monitoring options for Automation Server operations in a test or production environment.
A system administrator can use Bizagi Diagnostics, to run health checks on Automation Server components and the overall environment, while identifying issues that are affecting operations of the Bizagi project (e.g, performance issues, service downtime), to analyze and resolve them promptly.
Bizagi Diagnostics does not add significant overhead in runtime. It:
•Lets you work with logs all stored in one place.
•Provides business-oriented analysis and other options which use contextualized information.
•Relies on modern technologies while providing data analysis flexibility.
The image above illustrates the underlying concept of how Bizagi Diagnostics works and how you could set it up.
We recommend that Bizagi Diagnostics run on a separate server (not where Automation Server operates).
Before you start
Bizagi Diagnostics displays information based on server events as reported by each of the Automation Server components (i.e, Work portal, Scheduler service) in the underlying project.
You will need to make sure that Automation Server components are constantly reporting such events into logs.
Further information on how to configure this reporting is specified in the chapters below.
The system administrator must know the expected SLAs of the Bizagi project, including service thresholds involving external systems integrated with by the project.
Refer to the following articles for next steps: