Zeebe Exporters best practice

Hi,

In case of incident raised under workflow engine I need to create an alert to local monitoring system.

How to achieve this?

  • Create an exporter with incident record filtering, log record data to Zeebe log. After a separate service will analyze log by key word pattern, contact local monitoring system.
  • Same approach, but instead of logging data, send it directly to monitoring system (http request).
  • Do not use an exporter! Elasticsearch API to get information about raised incidents, contact monitoring tool.

Under Zeebe documentation written that exporters can impact cluster performance and in worst scenario completely block a thread.

Any best practice of using exporters? Under 3 broker nodes cluster environment it need to be connect to each broker?

Check the blog, there is a Zeebe Incident Alerter Exporter on there that calls a REST webhook: https://zeebe.io/blog/2020/02/incident-exporter/

Hi Josh Wulf,

Thank you for your answer! I saw your article – it’s highly informative.

I am wondering if someone already using custom exporters under production environment and have some experience. Maybe lessons learned, which ones impacts cluster performance and how to avoid such situation in future.

Regards,
Andrej

@Andrej You can try this exporters https://github.com/zeebe-io/zeebe-hazelcast-exporter, connect to hazelcast and register a listener in your local monitoring system.