Monitoring for Spring zeebe

I want to monitor the workflow so how should I integrate spring monitor with spring-zeebe-broker?

Hi @regojoyson,

thanks for trying out Zeebe.

Just to clarify with spring monitor you mean simple-monitor right?
The simple monitor is a standalone application so you don’t have to integrate it with spring-zeebe.

Hope this helps.


For monitoring workflows you can use Operate, or Simple Monitor, or both (slow, but insightful).

Simple Monitor shows details of message subscriptions, which is useful for debugging message correlation. Operate doesn’t show that.

You can use these docker-compose configurations here:

Hi @Zelldon @jwulf ,

Thanks for the quick respsonse. I wanted to export data to elastic and also to simple monitor. so i want to know how to implement/connect exporter in spring zeebe broker project. beacause i got the implementation for Zeebe broker project but not for spring zeebe broker .

I tried to add POM dependency and un-commented exporter line in zeebe.cfg file but no luck

if any examples or samples in git for this it will be very helpful for all.

Embedded broker?

@zelldon is this still a thing? Or is it deprecated?

Hey @jwulf,

yes it is out of date and needs to be updated. I think it is often used for demo purposes.


1 Like

Hey @regojoyson,

the spring project is currently out of date and needs to be updated.

Nevertheless it should be possible to configure both exporters in the zeebe.cfg.toml.
The exporter section in the config could look like this:

id = "elasticsearch"
className = "io.zeebe.exporter.ElasticsearchExporter"

  url = "http://localhost:9200"

  delay = 5
  size = 1_000

  username = elastic
  password = changeme

  prefix = "zeebe-record"
  createTemplate = true

 id = "simple-monitor"
 className = "io.zeebe.monitor.SimpleMonitorExporter"
 id = "hazelcast"
 className = "io.zeebe.hazelcast.exporter.HazelcastExporter"
1 Like

Thanks @Zelldon @jwulf for the update.

Can I use spring-zeebe-starter client with zeebe-broker instead of spring-zeebe broker ? is there any problems?
@Zelldon @jwulf


Hi @jwulf,
I want to use new zeebe 0.18.0 version and also new version of monitor. so i tried with given git project by changing the version of zeebe,monitor and updated the 2 jars (monitor and hazelcast exporter ) ,But its giving error in simple monitor for creating element instance table in db .

this is the below project link, which i tried to fork.


Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [element_instance]

Can you Please create one more project for latest zeebe 0.18.0 with latest monitor

Hi @regojoyson - this is the one you want:

1 Like

THANKS @jwulf. can I use simple monitor or operate for production…? Is there any performance impact? Is there any charges or pricing model.?

Hi @jwulf, I am getting errors while running the operator-simple-monitor in docker. here is the error in simple-monitor

git url :

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2019-06-14 12:54:53.892 ERROR 1 --- [           main] o.s.boot.SpringApplication               : Application run failed

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaConfiguration.class]: Invocation of init method failed; nested exception is javax.persistence.PersistenceException: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested exception is org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [element_instance]
        at ~[spring-beans-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at ~[spring-beans-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at ~[spring-beans-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at$doGetBean$0( ~[spring-beans-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at ~[spring-beans-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at ~[spring-beans-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at ~[spring-beans-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at ~[spring-context-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at ~[spring-context-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at ~[spring-context-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh( ~[spring-boot-2.1.2.RELEASE.jar!/:2.1.2.RELEASE]
        at org.springframework.boot.SpringApplication.refresh( [spring-boot-2.1.2.RELEASE.jar!/:2.1.2.RELEASE]
        at org.springframework.boot.SpringApplication.refreshContext( [spring-boot-2.1.2.RELEASE.jar!/:2.1.2.RELEASE]
        at [spring-boot-2.1.2.RELEASE.jar!/:2.1.2.RELEASE]
        at [spring-boot-2.1.2.RELEASE.jar!/:2.1.2.RELEASE]
        at [spring-boot-2.1.2.RELEASE.jar!/:2.1.2.RELEASE]
        at io.zeebe.monitor.ZeebeSimpleMonitorApp.main( [classes!/:0.14.0]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_212]
        at sun.reflect.NativeMethodAccessorImpl.invoke( ~[na:1.8.0_212]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke( ~[na:1.8.0_212]
        at java.lang.reflect.Method.invoke( ~[na:1.8.0_212]
        at [zeebe-simple-monitor.jar:0.14.0]
        at org.springframework.boot.loader.Launcher.launch( [zeebe-simple-monitor.jar:0.14.0]
        at org.springframework.boot.loader.Launcher.launch( [zeebe-simple-monitor.jar:0.14.0]
        at org.springframework.boot.loader.JarLauncher.main( [zeebe-simple-monitor.jar:0.14.0]
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested exception is org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [element_instance]
        at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.buildNativeEntityManagerFactory( ~[spring-orm-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet( ~[spring-orm-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.afterPropertiesSet( ~[spring-orm-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at ~[spring-beans-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at ~[spring-beans-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        ... 24 common frames omitted
Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [element_instance]
        at org.hibernate.tool.schema.internal.AbstractSchemaValidator.validateTable( ~[hibernate-core-5.3.7.Final.jar!/:5.3.7.Final]
        at org.hibernate.tool.schema.internal.GroupedSchemaValidatorImpl.validateTables( ~[hibernate-core-5.3.7.Final.jar!/:5.3.7.Final]
        at org.hibernate.tool.schema.internal.AbstractSchemaValidator.performValidation( ~[hibernate-core-5.3.7.Final.jar!/:5.3.7.Final]
        at org.hibernate.tool.schema.internal.AbstractSchemaValidator.doValidation( ~[hibernate-core-5.3.7.Final.jar!/:5.3.7.Final]
        at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction( ~[hibernate-core-5.3.7.Final.jar!/:5.3.7.Final]
        at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process( ~[hibernate-core-5.3.7.Final.jar!/:5.3.7.Final]
        at org.hibernate.internal.SessionFactoryImpl.<init>( ~[hibernate-core-5.3.7.Final.jar!/:5.3.7.Final]
        at ~[hibernate-core-5.3.7.Final.jar!/:5.3.7.Final]
        at ~[hibernate-core-5.3.7.Final.jar!/:5.3.7.Final]
        at org.springframework.orm.jpa.vendor.SpringHibernateJpaPersistenceProvider.createContainerEntityManagerFactory( ~[spring-orm-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory( ~[spring-orm-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.buildNativeEntityManagerFactory( ~[spring-orm-5.1.4.RELEASE.jar!/:5.1.4.RELEASE]
        ... 28 common frames omitted

Hi @regojoyson, I understand that you see errors in the startup logs. Here’s my question: does it work?

It should start the simple monitor on port 8082 of localhost.

See this link for an explanation of these errors:

1 Like

Don’t use Simple Monitor in production with the H2 database. It is too slow.

You can use it with Operate. That uses an Elastic Search exporter.

1 Like

Thanks @jwulf for the quick response. I am using the monitor and operator with the clustered zeebe…so it’s not working. It’s retrying every time but not starting…I waited for 20 mins. But for single instance of zeebe and monitor it’s worked for me

Can you please create one docker-compose for clustered zeebe with operate and monitor? It will very helpful for all

The operate is having free trail license I can use it in production right without any charges?