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

Supported integration with OpenShift Monitoring and BYO Prometheus

    XMLWordPrintable

Details

    • Improve Prometheus, Grafana integration for Production
    • False
    • False
    • doc_ack
    • Documentation (Ref Guide, User Guide, etc.), Release Notes, Compatibility/Configuration
    • To Do
    • 100
    • 100% 100%
    • undefined

    Description

      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

          is documented by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OSSM-3661 [DOC] Document configuring OSSM with OpenShift (or external) 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

          Task - Represents a small unit of work that is not end-user facing. OSSM-3184 [DOC] [Kiali] Integration config (Prometheus, Jaeger, Grafana)

          • 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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OSSM-316 [RFE] Enable persistent volume for prometheus deployed with servicemesh

          • 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

          Bug - A problem that impairs or prevents the functions of the product. OSSM-2126 Grafana storage capacity configured in SMCP isn't honored

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Spike - Represents a research-related task. OSSM-415 RFE: Support federating prometheus metrics through the monitoring instance of prometheus

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OSSM-571 Improve Kiali on Prometheus Production scenarios

          • 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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OSSM-898 [TP] Cluster Wide Mesh

          • 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

              jewertow@redhat.com Jacek Ewertowski
              dgrimm@redhat.com Daniel Grimm
              Dylan Monroe (Inactive)
              Votes:
              12 Vote for this issue
              Watchers:
              35 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: