Telemetry Plugin throws error with version 1.5.0 for EventQueue metrics

[markus-schwarz-git]

Hi,

we have an issue with the new @cap-js/telemetry version 1.5.0.

For context: We have a cap application with fiori elements which is deployed to SAP BTP and uses SAP event mesh as event broker. We also use the telemetry plugin to send metrics to our SAP Cloud Logging instance.

With @cap-js/telemetry@1.4.1 everything works fine but with version 1.5.0 we observe the behaviour that messages are getting stuck in the SAP Event Mesh Queue and do not get processed - respectively they only get processed after a very long time period.

Every time when these messages are processed we do not have any error within our application but we do get an error in our SAP cloud logging instance which points us directly the @cap-js/telemetry library (see attached error_log.json). The message always roots from /home/vcap/deps/0/node_modules/@cap-js/telemetry/lib/metrics/queue.js:174:31 and it seems that there are necessary properties undefined.

As I mentioned with 1.4.1 everything works fine for us and all messages can be processed. But version 1.4.1 doesn't have a queue.js.

Here is our cds -v:

@cap-js/asyncapi: 1.0.3
@cap-js/cds-test: 0.4.0
@cap-js/cds-typer: 0.36.0
@cap-js/cds-types: 0.13.0
@cap-js/change-tracking: 1.0.8
@cap-js/db-service: 2.3.0
@cap-js/hana: 2.1.2
@cap-js/openapi: 1.2.3
@cap-js/sqlite: 2.0.2
@cap-js/telemetry: 1.5.0
@msg-group/ri: 1.0.0
@sap/cds: 9.1.0
@sap/cds-compiler: 6.1.0
@sap/cds-dk: 9.1.2
@sap/cds-dk (global): 9.1.0
@sap/cds-fiori: 2.0.1
@sap/cds-mtxs: 3.1.0
@sap/eslint-plugin-cds: 4.0.2

Could you please have a look at this?

error_log.json

Best regards,
Markus

[sjvans]

hi @markus-schwarz-git

thanks for reporting. looks like there is an issue with tenant propagation. fyi, you can deactivate the queue metrics via cds.requires.telemetry.metrics._queue = false until there is a solution.

best,
sebastian