Falko Menge

@daniel-ewing pointed out that the name of the corresponding environment variables may be hard to guess: ```yaml zeebe: env: - name: ZEEBE_BROKER_EXPORTERS_ELASTICSEARCH_ARGS_INDEX_NUMBEROFSHARDS value: "1" ``` ~ZEEBE_BROKER_EXPORTERS_ELASTICSEARCH_ARGS_INDEX_NUMBER_OF_SHARDS~ does not work.

It may also be work documenting that the sharding configuration can be checked with an Elasticsearch query like: ```sh curl --location 'http://127.0.0.1:9200/_cat/indices/zeebe*?v=true&s=index&pretty' ```

@jothikiruthika and I discovered that the [Elasticsearch Exporter creates indices with inconsistent number of shards](https://github.com/camunda/zeebe/issues/18181). Getting this wrong in the beginning may cause difficult migrations later. Therefore, this topic should...

This feature should be built in the same for escalation events, which BPMN has introduced as a potentially non-interrupting alternative to error events.

This feature should be built in the same for escalation events, which BPMN has introduced as a potentially non-interrupting alternative to error events.

I would have needed this for a prospect. In my case it was lexicographic order was just for cosmetics though. I worked around it with sting `length()`

There has been discussion that most the time we start the Spring Boot app using Maven for local development.

Also there is the question how to build the image. I'd suggest leveraging `./mvnw spring-boot:build-image` (see: https://www.baeldung.com/spring-boot-docker-images#buildpacks)

However, letting `docker-compose` kick off the entire Maven and Docker build also has it's convenience. And sometimes a Dockerfile is needed when some addition files should be included.

The project has been developed on Java 8. Since you're using Java 11, you're missing the JAXB libraries in the default classpath. For a solution see: https://stackoverflow.com/questions/52502189/java-11-package-javax-xml-bind-does-not-exist Feel free to...