feat: optional axios tracing setup based on axios-debug-log presence - #410
feat: optional axios tracing setup based on axios-debug-log presence#410kulliax wants to merge 2 commits into
Conversation
|
hi @kulliax sorry for the late reply. we already wrap sap cloud sdk's executeHttpRequest and executeHttpRequestWithOrigin. why is that not sufficient when using pls? which version were you on? could #402 (in v1.6.0) have been the issue? |
|
Hi @sjvans, we will test this again as part of the migration to CAP 10. As described in the ticket linked above, the request is treated as a whole. However, for analysis purposes, we also need the sub-requests. |
|
currently we use @cap-js/telemetry@1.6.0 |
|
Hi @sjvans , I updated the package to the latest version yesterday. Unfortunately, the requests are still not being displayed individually in the trace log. Scenario: App > Destination > PLS > S4 Hana with cloud sdk Best regards |
|
#451 should fix it |
|
Hi @sjvans , When is the release planned? |
Draft that we use for our PLS logging, see issue #397
Activation by adding the axios-debug-log module. I tried implementing the SAP Cloud SDK, but gave up after a while because this method works.
