Camunda Optimize: History cleanup is not being triggered

Camunda 8 Topics
1

Hello.
I’m using Camunda 8 self managed service in version 8.7.2, helmchart camunda-platform-12.0.2 and i have issue with history cleanup not being started.
My configuration for Optimize is:


optimize:
  enabled: true
  extraConfiguration:
    application.yaml: |
      historyCleanup:
        processDataCleanup.enabled: true
        decisionDataCleanup.enabled: true
        ingestedEventCleanup.enabled: true
        cronTrigger: '*/5 * * * *'
        ttl: 'P1W'

which results in creation of /optimize/config/application.yaml file that looks like that:
image

However the cleanup never happens, and all i can find in logs regarding cleanup is:

image
image1112×47 2.49 KB

What’s wrong with my setup? How can i make it work?

2

Hi Pawel1,

Welcome to the forums!

From the documentation your application.yaml file doesn’t look right.

It looks like your file would need to look like:

camunda.optimize:
      historyCleanup:
        processDataCleanup.enabled: true
        decisionDataCleanup.enabled: true
        ingestedEventCleanup.enabled: true
        cronTrigger: '*/5 * * * *'
        ttl: 'P1W'

But I can’t find anywhere in the documentation that talks about historyCleanup.
Perhaps you mean the dataArchiver?

3

I’m reffering to the Camunda Optimize History Cleanup feature, which is documented here: Overview | Camunda 8 Docs
My application.yaml looks like in examples that are shown here: History cleanup | Camunda 8 Docs

4

Hi Pawel1,
Looking at the section above the one you linked to, it looks like those YAML values need to be put in the environment-config.yaml rather than into an application.yaml