-
Type:
Sub-task
-
Resolution: Done
-
Priority:
L3 - Default
-
Affects Version/s: None
-
Component/s: backend
-
Not defined
The Optimize documentation should explain in either/both the context of event process mapping and event history cleanup, that the event counts listed for Camunda events might not be accurate. This is because the sequences/traces do not get updated on history clean up
ATs:
- The documentation explains clearly what the event count number represents
- It can be wrong for following reasons
- It doesn't reflect version/tenancy configuration. Instead it is the number of events for all versions/tenants for the given definition
- If history cleanup has ever been applied, the counts aren't corrected so will appear higher than might be expected