Uploaded image for project: 'Cluster Observability Operator'
  1. Cluster Observability Operator
  2. COO-1016

enableOtlpHttpReceiver not being set in resulting Prometheus configuration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 1.2.0
    • monitoring-stack
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When creating a monitoringStack object there's an option to enable to OTLP Http receiver, which injects the following into the object definition

      spec:
        prometheusConfig:
          enableOtlpHttpReceiver: true

      However, after Prometheus has come up, attempts to perform a HTTP post to the OTLP endpoint (/api/v1/otlp/v1/metrics) will result in a 404 with the response body:

      otlp write receiver needs to be enabled with --web.enable-otlp-receiver

      To recreate:

      • Install COO (1.2.0)
      • Create a new MonitoringStack Object
        • Enable the OTLP HTTP Receiver under Prometheus Config
      • Create a route to the Prometheus instance
      • Attempt to HTTP Post to the OLTP ingester (<prometheus-route>/api/v1/oltp/v1/metrics

              mariofer@redhat.com Mario Fernandez Herrero (Inactive)
              rh-ee-dholder David Holder
              None
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: