Operate UI not showing running instance with standalone gateway

Camunda 8 Topics Discussion & Questions
1

We recently upgrade zeebe version to 0.23.3 using the zeebe cluster helm chart and along with that the standalone gateway was supported. But the operate UI no longer showing the running instances.

The older installation without standalone gateway running zeebe version 0.22.3 had no issues. Anyone knows how to troubleshoot this issue?

see this log message from operate:
No index found for alias zeebe-record-variable-document

I can see the indices like zeebe-record_variable* in elasticseach.

zeebe cluster application yaml:

application.yaml: |
zeebe:
cluster:
clusterSize: 3
partitionCount: 3
replicationFactor: 3
gateway:
enabled: false
network:
host: 0.0.0.0
threads:
cpuThreadCount: 4
ioThreadCount: 4

The follow config is for operate:

camunda.operate:
elasticsearch:
clusterName: elasticsearch
host: elasticsearch-master
port: 9200
zeebe:
brokerContactPoint: zeebe-gateway:26500
zeebeElasticsearch:
clusterName: elasticsearch
host: elasticsearch-master
port: 9200
prefix: zeebe-record
logging:
level:
ROOT: INFO
org.camunda.operate: DEBUG

management.endpoints.web.exposure.include: health,info,conditions,configprops,prometheus

2

If Operate is not showing the instances, then either Zeebe is not correctly exporting to ElasticSearch, or Operate is not reading from it.

The pathway looks like this:

ElasticSearch running in cluster.

ElasticSearch exporter loaded and operating in Zeebe brokers -> Connection to ElasticSearch for export.

ElasticSearch -> Operate connected and reading.

1 Like
3