• Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • telemetry-operator
    • None
    • Improve alarming
    • 13
    • False
    • Hide

      None

      Show
      None
    • False
    • OBSDA-973Enhance metrics collected by RHOSO for FR2
    • Not Selected
    • Proposed
    • Proposed
    • To Do
    • OBSDA-973 - Enhance metrics collected by RHOSO for FR2
    • Proposed
    • Proposed
    • 100% To Do, 0% In Progress, 0% Done

      Currently, in RHOSO, the user can configure alarms into aodh and that will query Prometheus every minute checking if the configured metrics go over the configured threshold.

      If that goes above the threshold, aodh will trigger a webhook on Heat to start an autoscaling operator, so the alarming is currently tied very specifically to autoscaling.

      The user could also configure alarms on alertmanager, but we might want something more OSP integrated, and thats why this epic exists.

      The first question to answer is if we want to re-enable events to get better and quicker alarms, as well as expand aodh capabilities so the user can configure multiple alarms and they will always have the tenancy incorporated.

      Also, we need to build some system to show the alarms to the user.

            rhn-engineering-jlarriba Juan Larriba
            rhn-engineering-jlarriba Juan Larriba
            rhos-dfg-cloudops
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: