Monitor your KPIs!!! Camunda BPM Process Engine Plugin providing Prometheus Monitoring, Metric classes for various BPMN use, Grafana Annotations, and HTTPServer data export: Used to generate Prometheus metrics anywhere in the Engine, including BPMN, CMN, and DMN engines and instances.
Tracking various use cases for testing and brevity
Microservice Orchestration with Service Activities and External Task Activitys
Service Task Actvities Delegation Code performance tracking
Variable value monitoring to provide aggregated values
Job Executor performance tracking
Groups of Activity Durations that make up a "performance" metric: Ability to track total durations without using Intermediate Events as markers.
Reducing Camunda History levels to very minimal collection and minimal history storage TTL, in efforts to increase engine performance; tracking the throughput of performance heavy activities and job executor activities that are penalizing the overall throughput
Tracking job executor throughput and identifying problem activities or processes.
Identity Timer Definitions that are stacking up instances (often due to looping conditionals gateways)
DMN throughput
Monitoring of Incidents
Multi-Engine Tracking
Multi-Container monitoring when they are the same
Alerting about performance or any sort of metric
New Deployment alerting and tracking
Variable Size Tracking: Tracking which variables are starting to eat up the most bytes in the DB and possibly clean those up.
Which Messages and Receive Tasks are stacking or processing the most
Mulit-Instance that is stacking up LARGE number of instances to block the job executor
Tracking Locks and Concurrency issues
Tracking specific errors
Down Time monitoring
Server version roll outs: Which instances of the servers have the specific updates rolled out to them in a cluster setup
Cluster monitoring
PLugin Activation: which plugins are active on which clusters
Extend a ProcessEngineError class with a custom handler allowing errors throughout the system to be counted: Example: The number of specific errors occurring from a Process Instance cannot start due to a roll back.
certain number of active instances that contain a variable of a certain value (use case explanation: being able to generate alerts based on number of instances with that variable value. This can be easily implemented with Gauges and listeners to update the gauge on every change or using conditional events. But this becomes a annoyance of having to update the BPMN. Need to find the way to implement this as a internal listener without having to continually update the BPMN.)
what periods they expect the most processes instances started for a specific process.
how durations of task and process instances are related to process variables and task workers: Adding the Variables creates a much more complex set of dimensions that creates a exponential increase in timeseries tracking.
Tracking various use cases for testing and brevity
Microservice Orchestration with Service Activities and External Task Activitys
Service Task Actvities Delegation Code performance tracking
Variable value monitoring to provide aggregated values
Job Executor performance tracking
Groups of Activity Durations that make up a "performance" metric: Ability to track total durations without using Intermediate Events as markers.
Reducing Camunda History levels to very minimal collection and minimal history storage TTL, in efforts to increase engine performance; tracking the throughput of performance heavy activities and job executor activities that are penalizing the overall throughput
Tracking job executor throughput and identifying problem activities or processes.
Identity Timer Definitions that are stacking up instances (often due to looping conditionals gateways)
DMN throughput
Monitoring of Incidents
Multi-Engine Tracking
Multi-Container monitoring when they are the same
Alerting about performance or any sort of metric
New Deployment alerting and tracking
Variable Size Tracking: Tracking which variables are starting to eat up the most bytes in the DB and possibly clean those up.
Which Messages and Receive Tasks are stacking or processing the most
Mulit-Instance that is stacking up LARGE number of instances to block the job executor
Tracking Locks and Concurrency issues
Tracking specific errors
Down Time monitoring
Server version roll outs: Which instances of the servers have the specific updates rolled out to them in a cluster setup
Cluster monitoring
PLugin Activation: which plugins are active on which clusters
Extend a ProcessEngineError class with a custom handler allowing errors throughout the system to be counted: Example: The number of specific errors occurring from a Process Instance cannot start due to a roll back.
certain number of active instances that contain a variable of a certain value (use case explanation: being able to generate alerts based on number of instances with that variable value. This can be easily implemented with Gauges and listeners to update the gauge on every change or using conditional events. But this becomes a annoyance of having to update the BPMN. Need to find the way to implement this as a internal listener without having to continually update the BPMN.)
what periods they expect the most processes instances started for a specific process.
how durations of task and process instances are related to process variables and task workers: Adding the Variables creates a much more complex set of dimensions that creates a exponential increase in timeseries tracking.