Overview
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.
Major features
Bizagi Diagnostics does not add significant overhead in runtime. It:
•Lets you work with logs that are 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 you run Bizagi Diagnostics on a separate server (not where Automation Server operates).
Before you start
Bizagi Diagnostics displays information based on server events, reported by each of the Automation Server components (i.e, Work Portal, Scheduler service) from the underlying project.
Make sure that Automation Server components are constantly reporting events into logs.
Further information on how to configure Diagnostics 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 the project.
What is installed with Bizagi Diagnostics?
Bizagi Diagnostics is based on four main components: ELK stack, with LogStash for log transformation and loading, ElasticSearch for storage and data operations and Grafana for data display.
A strong knowledge of Grafana will help you customize the information displayed by Bizagi Diagnostics.
Further information
Refer to the following articles for further steps: