Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-56938

[BP 7.2.1] - XDCR No XDCR Metrics for Status of a Replication

    XMLWordPrintable

Details

    • 1

    Description

      To effectively implement alerting around XDCR the status of a replication needs to be known.  The ns_server REST APIs return a status of "running", "paused", "error".  If this value is exposed, I can create an alert on whether or not the replication has been paused as an example a customer may wish to alert on the fact a replication has been paused for more than 1 days time.  

       

      Prometheus metrics must be a number:

      xdcr_status{status="running"} 1

      xdcr_status{status="paused"} 0
      xdcr_status{status="error"} 0

      or

      xdcr_status{status="running"} 0

      xdcr_status{status="paused"} 1
      xdcr_status{status="error"} 2

       

      Issue Resolution
      Prometheus stats did not include a pipeline’s status. The pipeline status is now provided as part of a prometheus stat.

      Attachments

        Issue Links

          For Gerrit Dashboard: MB-56938
          # Subject Branch Project Status CR V

          Activity

            People

              ayush.nayyar Ayush Nayyar
              neil.huang Neil Huang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty