Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-4550 Provide more accurate event frequency indicator in the events table in the FE EBP view
  3. OPT-4732

Prevent use of 'camunda' as ingested event source

XMLWordPrintable

    • Not defined

      In order to differentiate between event types, we need to know internally whether or not an event came from externally or from Camunda. Using the properties of an event alone doesn't provide this option. We should therefore use the source field to determine this. Camunda events already use the value camunda for this field, so we should also prevent this being used for ingested external events.

      Hint: If any existing events have been ingested with that value, we might need to assist with helping customers update their values (would also be part of various other indices, so could be complex)

      ATs:

      • Ingested events cannot use camunda as the value of the source field
      • The upgrade documentation mentions this breaking change

       

        This is the controller panel for Smart Panels app

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

                Created:
                Updated:
                Resolved: