Jaeger Monitor not compatible with current spanmetrics setup

[elbakerino]

Bug Report

Which version of the demo you are using?

471204eec5031dffcb241c143822d7e4905abc75

Symptom

Jaeger Monitor does not show metrics: "No data yet! Please see these instructions on how to set up your span metrics."

Reproduce

Clone the mentioned version, start all up, open Jaeger Monitor and you won't see metrics.

Additional Context

It seems that Jaeger requires the setup of the spanmetrics PROCESSOR, but the e.g. Grafana Dashboard here requires the format of the spanmetrics CONNECTOR.

See this SO post for other context.

With adding the deprecated PROCESSOR, the Monitor tab works again.

What would be the correct fix or what other options would be the "reference setup" here?

With this config, an additional PROCESSOR is added - and the Monitor tab works again, but now data is of course written twice to Prometheus.

receivers:
    otlp:
        protocols:
            grpc:

exporters:
    otlp:
        endpoint: "jaeger:4317"
        tls:
            insecure: true
    logging:
    prometheus:
        # this prometheus is used by `spanmetrics` CONNECTOR + PROCESSOR
        endpoint: "otelcol:9464"
        # these configs apply to the `spanmetrics` CONNECTOR
        resource_to_telemetry_conversion:
            enabled: true
        enable_open_metrics: true # even with `false`, the data wasn't compatible with `jaeger`

processors:
    batch:
    # deprecated spanmetrics PROCESSOR, used for compatibility with Jaeger Metrics
    spanmetrics:
        metrics_exporter: prometheus

connectors:
    # new spanmetrics CONNECTOR
    spanmetrics:

service:
    pipelines:
        traces:
            receivers: [ otlp ]
            processors: [ batch, spanmetrics ] # configuring spanmetrics PROCESSOR (deprecated)
            exporters: [ otlp, spanmetrics ] # configuring spanmetrics CONNECTOR (not compatible w/ jaeger)
        metrics:
            receivers: [ redis, otlp, spanmetrics ] # configuring spanmetrics CONNECTOR as source of "metrics" (not compatible w/ jaeger)
            processors: [ batch ]
            exporters: [ prometheus ]

[puckpuck]

When moving from processor to connector the metric names and tags also had some small changes to them. Could that be what is the issue?

[julianocosta89]

Probably yes, a possible solution here would be adding a transform processor to the collector before sending the metrics to Jaeger.

I wonder if Jaeger will adapt the new release to align with the spanmetrics connector metrics name.

@pavolloffay do you happen to know more about that?

[Ecostack]

Is there any follow up on this issue? I am encountering the same issue while just testing the demo application.