What's new with Bonita 7.10: Monitoring of Bonita server

antoine.mottier's picture
Blog Categories: 

When you have a service running on a server, monitoring is key to guarantee high availability to end users.

Monitoring will help you properly size and tune your production environment to make sure you get the performance you expect. Monitoring need to be done at various levels:

  • Hardware / OS: CPU usage, memory usage, disk IO
  • Container (e.g. Docker): logs JVM: heap, threads
  • Application server: database connection pool
  • Database: connections, transactions, size
  • And finally the application itself: response time, workload

Bonita offers various features to monitor the health of the platform, including some new ones in Bonita 7.10.

The first one is available directly from Bonita Portal and is called Process monitoring. You get access to information such as number of open cases, cases in failed state, and more. You can learn more about it from the documentation.

But if you want to go deeper into Bonita monitoring, you need to monitor the activity at the level of the Bonita Engine. You want, for example, to monitor what we call "work," a unitary piece of code that need to be executed as part of a process instance execution.

Bonita Engine provides various metrics such as:

  • currently running works
  • pending works (queue)
  • number of connector works, and more.

The full list is available in the documentation.

Metrics information are available in log files and can also be accessed using a JMX client. Additionally, if you are a user of Enterprise Edition, metrics can be published to Prometheus and can be viewed using a tool such as Grafana.

To get more details about monitoring I recommend taking a look at the dedicated documentation page. Also the documentation page regarding performance troubleshooting and cluster can really be helpful.