Can this project be used to provide data to SAP Cloud ALM?

[gregorwolf]

Hello CAP JS Telemetry Team,

can you please provide some insights how this project is related to the SAP Cloud ALM - Expert Portal - Next Generation – Data Collection Infrastructure? SAP Cloud ALM Provides the not public NPM packages:

• @sap/xotel-agent-ext-js
• @sap/fesr-to-otel-js

which provide additional data beside the Standard OpenTelemetry data. Can this project and the approach described at OpenTelemetry@SAP be combined?

Best Regards
Gregor

[sjvans]

hi @gregorwolf

work in progress. :)

best,
sebastian

[Mischa1610]

I would also be really interested in this topic.
Is there any information that you can already share @sjvans? Also if it is only a work in progress, I would be happy to try or support it. (Connecting telemetry with this plugin directly from a CAP service on the BTP to SAP Cloud ALM).

Best Regards,
Michael A.

[szymarcus]

Hi,

would also be interested in tracking anonymous usage data from an UI5 app. Happy to get any updates on that.

Thanks in advance
Best Regards,
Marcus

[MaxSchmidtke]

Hi,

and another upvote for this question. Also I noticed, that @sap/xotel-agent-ext-js starts its own instance of node-sdk, as does cap-js/telemetry which are in conflict. Moreover it suppresses a lot of spans already within the collector. I wonder if there was the possibility to send all collected spans (by cap-js/telemetry) to a common collector (one for the entire landscape) and from their distribute to the different consumers (calm, dynatrace, cloud logging, jaeger, you name it) thereby also filtering on which spans to push?

best regards,
Max

[MaxSchmidtke]

Update: I found out that there is a poc which proves that the coexistence of both libraries works:
calm-cls-poc-incidents

[sjvans]

hi @MaxSchmidtke @szymarcus @Mischa1610 @gregorwolf

Update: I found out that there is a poc which proves that the coexistence of both libraries works: calm-cls-poc-incidents

at the moment, yes. however, this co-existence was achieved using OTel APIs that have been deprecated and will be removed in 2.0. hence, the scenario is not officially supported! once we have a solution that also works with OTel 2.0, we will make this public.

best,
sebastian