How the Hazelcast Exporter can be deployed with zeebe cluster using helm?

Sargastico · July 17, 2020, 9:59pm

Hi, I’m a begginer.

I was trying to deploy zeebe with the hazelcast exporter and connect it with the zeeqs on GCP kubernetes, but it didn’t work.

Both zeebe-cluster and zeeqs have helm charts… But how can I set the hazelcast exporter (from zeebe-cluster helm) to communicate with the hazelcast (deployed by zeeqs helm)?

I tried the “dynamic exporters to zeebe brokers” from zeebe-cluster-helm but it’s not working. Looking to zeebe logs, I can only see logs from the elasticsearch exporter, nothing from hazelcast. I think Hazelcast exporter is not working.

Could someone guide me to deploy both of helm charts and make them work together?

What I did before deploy with helm:

I created a file named “exporters.yaml” with “Adding dynamic exporters to Zeebe Brokers” content, to use with helm command:

helm install zeebe-cluster zeebe/zeebe-cluster --namespace zeebe -f exporters.yaml

I added hazelcast exporter environment variables on zeebe-cluster YAML file:

Thank you.

korthout · July 22, 2020, 1:05pm

Hi @Sargastico and welcome to the Zeebe forums

I’m really not familiar with the helm charts for either zeebe and zeeqs, so I won’t be able to help you out yet. However, I’d like to point out that both have a BETA warning in the top of their readme’s.

Having said that, I do think both zeebe and zeeqs should be deployable to GCP k8s using helm. Perhaps @salaboy can help out here.

salaboy · July 22, 2020, 7:59pm

hi @Sargastico great question… and yes… it is possible … but it is not as trivial as it should be. I’ve been working on this lately… I am updating the full chart to make sure that this works out of the box, but it is not still done.
Can you share your exporters file and how is that failing?
I would love to get that working this week so we can publish some tutorials around that…

Cheers

Sargastico · July 23, 2020, 4:53pm

Thanks for the quick response @korthout and @salaboy.

The exporter is not truly failing. The JAR is copied to the “/exporters/” directory on zeebe pods, but do not seems to be load or working as it should be. I haven’t changed any settings other than the ones I said on the last post.

Checking the logs, I can’t see any erros related to hazelcast exporter, it looks like the exporter is there, but it’s not exporting anything at all.

When trying to use zeeqs, I added the env variable to point the exporter to the hazelcast cluster deployed by zeeqs helm. I didn’t get errors too, but when querying with graphiql, it always returns empty results (I deployed some workflows and instances to test). Maybe I’m just missing some config point to communicate the exporter to the hzCluster.

It will be useful to have a helm chart to deploy all components from both of these charts together
(“zeebe cluster helm” + “zeeqs helm”)

@salaboy I hope you can make it work soon o/

Cheers

smolina74 · July 29, 2020, 2:04am

hi @salaboy, I’m trying to use Simple Monitor with Zeebe in a Kubernetes cluster. Now, Simple Monitor needs to point to the service exposed by hazecast exporter, the question is, which service does need to expose hazelcast port? the Zeebe Gateway service or the Zeebe broker service?

thanks

salaboy · July 29, 2020, 7:40am

@Sargastico thanks for the details… but I need more to understand how things are failing… you mention: “The JAR is copied to the “/exporters/” directory on zeebe pods” how are you doing that?
Which version of the charts are you using… and can you check the version of the brokers? Are you overriding any of those things?

salaboy · July 29, 2020, 7:40am

@smolina74 can you please open a different entry for this… Simple monitor will not be added to Helm charts as we consider ZeeQS the way to go.

Sargastico · July 31, 2020, 1:50pm

@salaboy thanks for the response. The JAR is copied by the code inside extraInitContainers from zeebe-cluster-helm repo as showed on the " Adding dynamic exporters to Zeebe Brokers" readme section.

I save this code in a exporters.yaml file, and used it with helm using the -f flag when installing zeebe with this command:

helm install zeebe-cluster zeebe/zeebe-cluster --namespace zeebe -f exporters.yaml

It seems to work partially, the JAR is deployed inside the /exporters/ folder, but it doesn’t seem to work as it should as I said in previous posts.

This is the output of the command “helm show chart”, maybe it answer about the version.
chart_version

I’m not overriding anything, just adding the extraInitContainers

salaboy · August 4, 2020, 8:27am

@Sargastico I am super busy over here… but I will investigate, can you try this profile in the meantime?

github.com

zeebe-io/zeebe-helm-profiles/blob/master/zeebe-dev-with-zeeqs-profile.yaml

zeebe:
    clusterSize: 1
    partitionCount: 1
    replicationFactor: 1
    extraInitContainers: |
    - name: init-exporters-hazelcast
      image: busybox:1.28
      command: ['/bin/sh', '-c']
      args: ['wget --no-check-certificate https://repo1.maven.org/maven2/io/zeebe/hazelcast/zeebe-hazelcast-exporter/0.8.0-alpha1/zeebe-hazelcast-exporter-0.9.0-alpha1-jar-with-dependencies.jar -O /exporters/zeebe-hazelcast-exporter.jar; ls -al']
      volumeMounts:
      - name: exporters
        mountPath: /exporters/
    zeebeCfg: |- 
      [[exporters]]
      id = "elasticsearch"
      className = "io.zeebe.exporter.ElasticsearchExporter"
        [exporters.args]
        url = "http://elasticsearch-master:9200"
        [exporters.args.bulk]
        delay = 5

This file has been truncated. show original

That is what I am working on to get it working.

Sargastico · August 4, 2020, 4:50pm

Thank you salaboy, I will test it as soon as possible and come back to give a feedback.

Cheers!

system · January 31, 2024, 10:06am