Skip to main content
Version: 8.9 (unreleased)

Optimize on Self-Managed

All distributions of Optimize come with a predefined set of configuration options that can be overwritten by the user, based on current environment requirements. To do that, have a look into the folder named config. There are two files, one called environment-config.yaml with values that override the default Optimize properties and another called environment-logback.xml, which sets the logging configuration.

You can see all supported values and read about logging configuration here.

Optimize web container configuration​

Refer to the configuration section on container settings for more information on how to adjust the Optimize web container configuration.

Elasticsearch/OpenSearch configuration​

You can customize the Elasticsearch/OpenSearch connection settings as well as the index settings.

Camunda 8 specific configuration​

For Camunda 8, Optimize imports process data from Zeebe records exported by the Elasticsearch exporter or OpenSearch exporter from the same cluster that Optimize uses to store its own data. For the relevant Optimize import options and version support, refer to the Camunda 8 system configuration.

Starting with Camunda 8.9, you can optionally reduce the amount of data exported for Optimize by configuring exporter-side filters (for example, by variable name, variable type, or BPMN process ID) in the Elasticsearch/OpenSearch exporters. Use the Elasticsearch exporter and OpenSearch exporter documentation for the exact configuration options, and see the Camunda 8 system configuration for their implications on Optimize imports and supported versions.

Adjust Optimize heap size​

By default, Optimize is configured with 1GB JVM heap memory. Depending on your setup and actual data, you might still encounter situations where you need more than this default for a seamless operation of Optimize. To increase the maximum heap size, you can set the environment variable OPTIMIZE_JAVA_OPTS and provide the desired JVM system properties; for example, for 2GB of Heap:

OPTIMIZE_JAVA_OPTS=-Xmx2048m