Uploaded image for project: 'Observability UI'
  1. Observability UI
  2. OU-922

[perses/operator] Provide better error handling and status conditions

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • COO 1.4.0
    • None
    • perses-upstream
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • 2
    • None
    • Sprint 280

      Description

      After a PersesDashboard or PersesDatasource has been successfully created (there is no validator error) the status on the CR is set to Available. Errors preventing the Dashboard and Datasources from being created in the backend can be seen in the operator logs. However it would be best to have the status of the CR's be tied to them being applied to the backends, and have the error messages be able to be viewable from the CR's so that a user doesn't need to go to the operator logs to debug.

       

              rh-ee-pyurkovi Peter Yurkovich
              rh-ee-pyurkovi Peter Yurkovich
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: