Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-4509

Set severity for over usage notifications

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • subs-swatch-lightning

      Available and default severity for notification can be set through the internal console (stage: https://internal.console.stage.redhat.com/api/notifications/internal/, ask notification team for production).

      (Then click on the pencil on the right)

      This should be set to the severity identified in this card (both available and default).

      The stage severity could already be set for testing purposes (nothing automated, so should not be changed once set).

      There is also the possibility of overriding the default severity by specifying one among the selected one and send it with the event payload. The message sent to platform.notifications.ingress Kafka topic must contain the severity field. Refer to the payload sample here.

      So logic that make a notification more severe based on the utilization percentage could be realized.

      Acceptance criteria:

      • If needed the payload is updated
        • All tests are updated
      • The new emails reflect the change

              Unassigned Unassigned
              rh-ee-tlencion Tommaso Lencioni
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: