Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-7631

[RHACS]: Streaming API endpoint for v1/alerts

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • rhacs
    • Future Sustainability
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None

      1. Proposed title of this feature request

      Streaming API endpoint for v1/alerts

      2. What is the nature and description of the request?

      Customer is using extensively the API endpoint for alerts (violations) where the data is very dynamic, changing very frequently and from query to query they might see different results.

      In addition, in v1/alerts, some of the data is missing (e.g which container made the violations). So, they end up performing calls for each alert in order to get all the data they require (v1/alerts/<alert_id>).

      They are requesting using the same streaming endpoint which is used for Deployments, which they have very good experience, but for alerts/violations data as well.

      3. Why does the customer need this? (List the business requirements here)

      Customer states that getting streaming endpoint for v1/alerts will make the data queries much more consistent and accurate.

      4. List any affected packages or components.

      RHACS Cloud Service Online

              bmichael@redhat.com Boaz Michaely
              rhn-support-faldana Fabio Aldana
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                None
                None