Skip to content

feat: support OpenTelemetry SDK 2.0#364

Open
sjvans wants to merge 28 commits into
mainfrom
otel-2.0
Open

feat: support OpenTelemetry SDK 2.0#364
sjvans wants to merge 28 commits into
mainfrom
otel-2.0

Conversation

@sjvans
Copy link
Copy Markdown
Contributor

@sjvans sjvans commented Aug 12, 2025

scope: w/o considering CALM


  • traces
  • metrics
  • logs
  • host-metrics compatible (no 0.200 yet)?
  • instrumentation-runtime-node compatible (no 0.200 yet)?

@PDT42 PDT42 marked this pull request as ready for review August 20, 2025 06:57
@sebastien-savalle
Copy link
Copy Markdown
Contributor

@sjvans : Do you plan to merge it soon ?

@sjvans
Copy link
Copy Markdown
Contributor Author

sjvans commented Dec 23, 2025

@sjvans : Do you plan to merge it soon ?

no, interoperability with Cloud ALM is still open

@harjyotsital15
Copy link
Copy Markdown

Given SAP’s direction—where xotel-agent-ext-js 2.x aligns with OpenTelemetry 2.x and 1.5.x is only supported with fixes until June 30, 2026—this transition is becoming quite time-critical.

Also, considering SAP Cloud ALM’s observability stack is OTEL-based and version mismatches already introduce compatibility issues, moving to 2.0 is essential to avoid fragmentation across CAP apps.

Is there any update on the timeline or next steps for completing the transition to OTel 2.0? This would really help with planning upcoming upgrades on our side. 🚀

@mrl-sap
Copy link
Copy Markdown

mrl-sap commented May 18, 2026

The initial description explicitely mentioned "scope: w/o considering CALM". So I would be interested in a timeline as well.
Can you give a rough estimate?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants