Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-3184

[DOC] [Kiali] Integration config (Prometheus, Jaeger, Grafana)

    XMLWordPrintable

Details

    Description

      As an administrator, I need to ensure that Kiali can reach integrated services that it is dependent on for data to ensure that my users have access to the data they need.

       Pull in upstream content for how to configure Kiali to communicate with other integrated programs.

      https://kiali.io/docs/configuration/p8s-jaeger-grafana/

      From OSSM-566:

      Questions to be answered:

      • How are customers deploying production-grade prometheus and grafana instances together with OSSM today?
        • We received regular questions around integrating OSSM with OpenShift's Prometheus
        • Customers also ask to integrate with AlertManager - OpenShift provides this.
      • Advantages/Disadvantages of different implementation options, e.g.:
        • Extending our existing charts with more options
        • Improve integration with external deployments (central deployments vs federated deployments)
        • Integrate closely with OpenShift monitoring tooling

       

       

      Attachments

        Issue Links

          documents

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OSSM-566 Supported integration with OpenShift Monitoring and BYO Prometheus

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is blocked by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OSSM-1352 Bring your own Prometheus

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Task - Represents a small unit of work that is not end-user facing. OSSM-3102 Determine what to do with unused tutorial files

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. OSSM-2808 New feature checklist for OSSM 2.3 release

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              gmonahan Gwynne Monahan
              jstickler Julie Stickler (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: