We need to build a static list of all severities supported by Notifications. That list will eventually be exposed to users through the User Preferences page after RHCLOUD-41540 and the corresponding UI work are done.

A few tenants (OCM, Errata, Inventory...) are already including a severity in their payloads. They most likely each have their own static list of severities. We need to determine a static list of severities in Notifications which needs to be compatible somehow with the severities from tenants.

If the tenant severities are not compatible out of the box, we can consider a mapping approach similar to the Quarkus log levels (see Table 1. The mapping between the levels).

Acceptance criteria:

• Retrieve the static list of severities from all tenants which currently include severities in the events sent to Notifications. There might be more tenants than just OCM, Errata and Inventory. Double check this with the stage and prod databases.
• If necessary, using a mapping approach as described above.
• Post in a comment in this ticket the final static list of severities from Notifications, with the mapping to the tenants severities when relevant.