Skip to content

docs(self-managed): Clarify Operate data flow in 8.8 exporter section #7717

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zaycodes merged 3 commits into from
Jan 14, 2026
Merged

docs(self-managed): Clarify Operate data flow in 8.8 exporter section #7717

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ae6b153
docs(self-managed): Clarify Operate data flow in 8.8 exporter section
zaycodes Jan 12, 2026
b63dbac
Merge branch 'main' into operate-data-flow-clarification
zaycodes Jan 12, 2026
62b8134
Apply suggestions from doc review
zaycodes Jan 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 8 additions & 7 deletions .../self-managed/components/orchestration-cluster/operate/operate-configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,17 +30,18 @@ See the [secondary storage documentation](/self-managed/components/orchestration

## Zeebe Elasticsearch or OpenSearch exporter

:::note
**Version 8.8+:** The Importer is required only for **migration scenarios** (upgrades from 8.7). Keep it enabled until all remaining 8.7 records have been imported. After that, the [Camunda Exporter](/self-managed/components/orchestration-cluster/zeebe/exporters/camunda-exporter.md) takes over and writes directly to the Operate indices. The Importer can then be safely disabled for subsequent restarts or deployments.
In 8.8+ installations, Operate reads data from Operate indices written by the
[Camunda Exporter](/self-managed/components/orchestration-cluster/zeebe/exporters/camunda-exporter.md).

New 8.8+ installations do **not** need to enable or configure the Importer. Its only purpose is to temporarily support migrations from 8.7 data.
:::note
The Operate Importer is used only during 8.7 → 8.8 migrations.
New 8.8+ installations do not require it.
:::

For Elasticsearch, Operate imports data from indices created and filled in by the [Zeebe Elasticsearch exporter](../zeebe/exporters/elasticsearch-exporter.md).

For OpenSearch, Operate imports data from indices created and filled in by the [Zeebe OpenSearch exporter](../zeebe/exporters/opensearch-exporter.md).
During 8.7 → 8.8 migrations, Operate imports remaining historical data from indices created by the [Zeebe Elasticsearch exporter](../zeebe/exporters/elasticsearch-exporter.md)
or the [Zeebe OpenSearch exporter](../zeebe/exporters/opensearch-exporter.md).

Therefore, settings for this Elasticsearch or OpenSearch connection must be defined and must correspond to the settings on the Zeebe side.
In both cases, the Elasticsearch or OpenSearch connection settings must match the exporter configuration used by Zeebe.

### Settings to connect and import

Expand Down
Loading