Jaeger UI SPM spanmetrics not working in 0.95.0

[PaulKushch]

Component(s)

No response

What happened?

Description

I find it hard to make jaeger SPM to work. I followed #26712 but still no success. Still I see traces in the other tab (so tracing works).

Steps to Reproduce

My SPM page have no data.

Expected Result

I expect to see metrics in SPM.

Actual Result

To see metrics for traces in SPM.

Collector version

0.95.0

Environment information

Environment

Ubuntu 22.04

OpenTelemetry Collector configuration

apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
  name: demo
spec:
  config: |
    receivers:
      jaeger:
        protocols:
          thrift_http:
            endpoint: "0.0.0.0:14278"

      otlp:
        protocols:
          grpc:
          http:

    exporters:
      prometheusremotewrite:
        endpoint: http://prometheus-server:80/api/v1/write
        target_info:
           enabled: true

      otlp:
        endpoint: http://jaeger-spm-collector:4317
        tls:
          insecure: true

    connectors:
      spanmetrics:
        exemplars:
          enabled: true

    service:
      pipelines:
        traces:
          receivers: [otlp, jaeger]
          processors: []
          exporters: [spanmetrics, otlp]
        metrics:
          receivers: [spanmetrics]
          exporters: [prometheusremotewrite]

Log output

If I `curl -X POST http://prometheus-server.apm.svc.cluster.local:80/api/v1/write -v` from another pod I get "remote write receiver needs to be enabled with --web.enable-remote-write-receiver" (only issue I can think of)...
So I enabled it in prometheus helm chart by setting `web.enable-remote-write-receiver` in `extraFlags` in values.yaml

Additional context

My Jaeger config

apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
  name: jaeger-spm
spec:
  strategy: allInOne
  allInOne:
    image: jaegertracing/all-in-one:latest
    options:
      log-level: debug
      query:
        base-path: /jaeger
      prometheus:
        server-url: http://prometheus-server:80
        query:
          support-spanmetrics-connector: true
    metricsStorage:
      type: prometheus
  storage:
    options:
      memory:
        max-traces: 100000

[github-actions]

Pinging code owners for connector/spanmetrics: @portertech. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

Pinging code owners for exporter/prometheusremotewrite: @Aneurysm9 @rapphil. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[portertech]

@PaulKushch This seems like a Prometheus remote write issue, can you confirm the remote-write-receiver extension is now working? Do you see the metric series on the Prometheus instance? This Prometheus extension has been deprecated, I wouldn't use it. Have you considered the otlp-write-receiver?

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• exporter/prometheusremotewrite: @Aneurysm9 @rapphil
• connector/spanmetrics: @portertech @Frapschen

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.