I would like to build custom tracking mechanism for all processes that are running in process engine.
What I mean? I want to store in the custom database all information about process instances status change. When the process started, what is the process instance key, what is the current node.
This mechanism should allow to catch all process instance changes and it should not have big impact on the process engine performance.
I want to build it for self-managed Camunda 8. It would be ideal if I could catch some kind on event in the Spring-boot application. I couldn’t find that option.
Is there any good way to do that?
Thank you in advance.
Hi!
Yes, it’s definitely possible to catch events related to process instance changes during execution in Camunda 8, especially in a self-managed setup. This can be achieved using the concept of exporters in Camunda. Exporters can be configured to capture various events without significantly impacting the process engine’s performance.
You can find multiple implementations of Camunda exporters created by the community in Java on GitHub. These exporters can help you track changes in your process instances efficiently. To help you get started, here’s the link to the Camunda documentation on exporters: Camunda Exporters Documentation.
Additionally, I recently wrote an article on how exporters can be used to send events from Camunda to RabbitMQ. It includes a practical guide and links to the GitHub code: Exporting Events from Camunda to RabbitMQ.
I hope this helps! Feel free to reach out if this isn’t quite what you’re looking for or if you have further questions.
1 Like
Hello @Dominik_Mazurowski ,
the exporter concept does work here, but requires an implementation inside camunda.
My recommendation would be to use the Orchestration cluster API as the process instance state is already available from there.
Any query here would not impact the process engine performance as it already exported the records to the underlying Elasticsearch.
Best regards,
Jonathan
1 Like