Uploaded image for project: 'Couchbase Monitoring and Observability Stack'
  1. Couchbase Monitoring and Observability Stack
  2. CMOS-90

Provide a HTTP Service Discovery source

    XMLWordPrintable

Details

    • New Feature
    • Resolution: Unresolved
    • Major
    • 1.0
    • None
    • cluster-monitor, cmos
    • None

    Description

      Currently the only way to tell Prometheus about your cluster (unless you're in k8s) is to use file service discovery. This isn't a trivial process for people unfamiliar with containers.

      I created a PoC of using cbmultimanager's cluster list as the source of truth for Prometheus, and it's promising.

      Outstanding questions:

      • Do we keep around cbmm's existing Prometheus discovery?
        • IMO yes, customers may want to use Prometheus' other SD mechanisms and we can't support them all
      • If ^, what happens if you create a SD cycle?
        • No problem, Prometheus handles the same cluster being exposed both by file and by HTTP without any issues.
      • How do we handle OSS builds? (Not including cbmm will mean Prometheus tries to HTTP-SD a nonexisting port - it'll still function, but logs will be flooded with errors, which is not ideal)

      Attachments

        Issue Links

          For Gerrit Dashboard: CMOS-90
          # Subject Branch Project Status CR V

          Activity

            People

              Unassigned Unassigned
              marks.polakovs Marks Polakovs (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty