Archiving of Camunda BPM Process Instances

Question

What is the best possible approach to archive the Camunda Process instances ? Is there a recommended setup to move or separate the historic processes from running processes.

Regards,

Phani

Answer 1

Camunda already separates runtime information (act_ru_* tables) and historic information (act_hi_* tables). If you would set your history level to "none", no historic information will be written at all, which shows that the engine works without historic tables.

So it is completely up to you, you can delete/archive/move historic information at will.

Typically, you would want to keep the historic information of running and recently finished instances for error analysis, and the management will be interested in historic reports, so there is more to it in deed.

What we do:

1. archive all historic information of finished processes that have been finished for at least a month.
2. provide relevant reporting data on a daily basis, so reporting is not done on the act_hi_ tables but a different, custom, schema

hope that helps.