Telemetry: processing upon API request interception needs to happen asynchronously

[dsilvam]

Parent Issue

No response

Problem Statement

When API interception is enabled, the processing is happening in a synchronous way which makes the requests to take longer and may even fail to respond if an underlying error happens.

Steps to Reproduce

• Bring up dotCMS in debug mode
• Install the telemetry plugin
• Enable API tracking with the property TELEMETRY_API_METRICS_ENABLED set to true
• Put a breakpoint in https://github.com/dotCMS/com.dotcms.telemetry/blob/main/src/main/java/com/dotcms/experience/collectors/api/ApiMetricWebInterceptor.java#L38
• Hit the frontend at localhost:8080

Issue: see how the breakpoint gets hit but the page doesn't get rendered until resuming.

Acceptance Criteria

The processing that happens on the interception of the API hits needs to happen asynchronously.

dotCMS Version

Telemetry plugin 24.05.2

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[freddyDOTCMS]

No changes are needed because saving the hit to the database is already done asynchronously, as shown here:

https://github.com/dotCMS/com.dotcms.telemetry/blob/f3eb85d3911ae0f4ea7c6a7c072cf8357119ac88/src/main/java/com/dotcms/experience/collectors/api/ApiMetricFactorySubmitter.java#L48

We have some code that does not run on the request thread. This code selects the MetricType for the current request, which should not take much time. Additionally, if any exceptions are thrown in this code, the response will continue normally.