Request: Deployment Example about zeebe-dev-monitor HOT 4 CLOSED

Totally! I'd love to see it too

from zeebe-dev-monitor.

@lorrod @valid-var the main goal of the Zeebe Dev Monitor is to support local development. It is use in https://github.com/quarkiverse/quarkus-zeebe as dev-services to support local development.

I would recommend to you for your case to try https://github.com/camunda-community-hub/zeebe-simple-monitor or https://docs.camunda.io/docs/components/operate/operate-introduction/

However, you are free to review the Quarkus-Zeebe source code and set up your own Docker-Compose. All components are open source.
https://github.com/quarkiverse/quarkus-zeebe/blob/main/deployment/src/main/java/io/quarkiverse/zeebe/devservices/ZeebeDevMonitorProcessor.java#L192

I currently don't have time to follow this path for this project.

from zeebe-dev-monitor.

I personally encounter challenges with Zeebe-simple-monitor; occasionally, processes/instances vanish from the monitor and then reappear. Another reason I'm keen on contributing to Zeebe-dev-monitor is its use of Vite under the hood, which makes it easier for me to integrate with Keycloak authentication.

Operate is paid solution unfortunately.

I'm currently unsure about the correct setup for the debug exporter, but I'll give it my best shot unless you have a local development setup that you can share.

Lastly, could you clarify why you believe this solution is exclusively apt for local development?

from zeebe-dev-monitor.

The main goal of the Zeebe Dev Monitor is to support Quarkus Zeebe local development.

I would recommend to you for your case to try
https://github.com/camunda-community-hub/zeebe-simple-monitor or https://docs.camunda.io/docs/components/operate/operate-introduction/

from zeebe-dev-monitor.