Uploaded image for project: 'Hybrid Cloud Console'
  1. Hybrid Cloud Console
  2. RHCLOUD-41537

Add a severity transformer in notifications-backend

XMLWordPrintable

    • Product / Portfolio Work
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • Unset
    • None

      This ticket depends on RHCLOUD-41535.

      We're introducing the severity in Notifications events in a non-breaking way:

      1. After RHCLOUD-41535 is done, if an incoming event contains a top level severity value, we will use this value as the event severity.
      2. Else if a tenant provides a severity as part of their event payload (this already exists, see comments below), we'll use this value as the event severity.
      3. Else we'll leave the event severity empty for now. We might have a default value (most likely "info" or similar) later, to be confirmed with PM.

      Acceptance criteria:

      • A new transformer bean is introduced in notifications-backend and used with all incoming events. It determines each event severity based on the description above.
      • The new transformer contains logic dedicated to a few tenants (see comments below). This is temporary. We'll help them migrate to the new severity field at a later stage.
      • The payload examples in the comments are not an exhaustive list. Identify all events that already contain a severity in the database, or ask tenants.
      • The new transformer is tested with unit tests.

              rh-ee-jrodri Jessica Rodriguez
              glepage@redhat.com Gwenneg Lepage
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: