Elastic Observability Redirection URL is broken

[cyrille-leclerc]

Elastic Observability Redirection URL is broken

[swilliams-dev]

I was able to get the link working by creating a custom observability backend in /configure that had my ES base url followed by: /app/apm/services/${serviceName}/transactions/view?rangeFrom=${startTime.minusSeconds(600)}&rangeTo=${startTime.plusSeconds(600)}&transactionName=${rootSpanName}&transactionType=unknown&latencyAggregationType=avg&traceId=${traceId}&transactionId=${spanId}

[cyrille-leclerc]

Cause found: elastic/apm-server#5006

[cyrille-leclerc]

Close as it's fixed for the integration architecture based on the Elastic Observability OTLP intake.

[cyrille-leclerc]

@v1v I checked again and the new URL works well for me with Elastic Observability 7.12

[cyrille-leclerc]

Workaround: set all transactions to type=unknown waiting to have a consistent support of type across Elastic integration architectures.

[swilliams-dev]

Workaround: set all transactions to type=unknown waiting to have a consistent support of type across Elastic integration architectures.

How do you do this? Mine seems stuck in transactionType=job. My usecase is locked to elastic stack 7.10.2, and I have to manually change the link from transactionType=job to transactionType=unknown to get it to resolve.

If there isn't an external way to set this, how would I rebuild the plugin with this change reverted?

[cyrille-leclerc]

Sorry for the inconvenience.
Great "workaround".
It seems that we lost compatibility with Elastis 7.x in recent versions of the Jenkins Otel Plugin. We have to offer this compatibility again.
I reopen this issue waiting to clarify this problem.

[swilliams-dev]

Thanks! Glad to provide details if I can help.

[cyrille-leclerc]

@swilliams-dev I misunderstood your problem. I thought it was an incompatibility with the 7.latest (ie 7.17) version of Elastic. I'm sorry but 7.10 is the 2020 release, an Elastic version that didn't yet have native support for the OTLP protocol and that required to use the now deprecated OpenTelemetry Collector Exporter for Elastic.

I am more inclined to document the "workaround" you identified rather than evolving the Otel Plugin for a setup that rely on components that have been deprecated a year ago.

Can you please share with us why you can't upgrade beyond Elastic 7.10? Why you can't upgrade to a recent 7.x version?

[swilliams-dev]

@cyrille-leclerc it is a bureaucratic limit based on the licensing model change, we are stuck with Apache 2.0: https://www.elastic.co/pricing/faq/licensing

If you have any old resources, I also hope to rig up the dashboard on 7.10.2.

[cyrille-leclerc]

Thanks for the explanation @swilliams-dev we will do our best to handle this scenario

If you have any old resources, I also hope to rig up the dashboard on 7.10.2.

I guess you can find old resources in the history of this git repository.

[kuisathaverat]

it is resolved