Operate not showing running instances processes list

Operate not showing up running instances processes list. we are using 8.1.0 version Camunda.

optimize showing up running process.

Anything needs to be added in operate override?

thanks
Raju

Hi @ramaraju and welcome to the forum,

What setup are you using (Docker, Helm-Charts, or local)?
If you’re using the local setup, make sure that you run Zeebe with an activated Elasticsearch exporter.

I am using Helm-Chart based,

Thanks
Raju

Have you checked logs of operate? Are there any errors? Does operate show historic instances?

Hi StephanHaarmann,

I did not see errors in the operate pod logs. I checked on Elasticsearch index (operate-list-view-8.1.0_) and no docs and empty. Looks like operate not writing onto Elasticsearch index.

optimism showing up the processes…but not operate.

Thanks
Raju

Hi,

Operate does not write to Elasticsearch, it only reads.
Zeebe is responsible for writing to Elasticsearch via a so-called exporter.
Make sure that the property elasticsearch.disableExporter is set to false.
Also check the logs of Elasticsearch and Zeebe.

Hi,

I think I figured out the root cause…

When we set “Client security configuration”. operate operations not working properly… After removing client security Operate showing up processes and able to perform “cancel” etc…

Question is we need to have “client security configuration” to connect Zeebe-gateway with secure from client ( zbctl)… is there way to configure client security without impacting operate operations…??

zeebe-gateway:
env:

  • name: ZEEBE_GATEWAY_SECURITY_ENABLED
    value: “true”
  • name: ZEEBE_GATEWAY_SECURITY_CERTIFICATECHAINPATH
    value: /usr/local/tls.crt
  • name: ZEEBE_GATEWAY_SECURITY_PRIVATEKEYPATH
    value: /usr/local/tls.key