Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-2719 Optimize can be used for all E2E processes - First Iteration
  3. OPT-3036

Persist the last processed timestamp for event count/trace processing

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.7.0
    • Component/s: backend
    • Labels:
      None

      Description

      As part of event processing to store event traces and sequence counts, we need to maintain a record of the ingestion timestamp of the most recently processed event in order to page through events. We currently store this in memory, so the timestamp is lost on restart and we need to process all events ever ingested to get back to where it was when it was left off. We should instead persist this last ingested timestamp so that we can resume from where we left off after restart. See discussion and original PR: https://github.com/camunda/camunda-optimize/pull/1369#discussion_r354862470

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            joshua.windels Joshua Windels
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: