RUM-1836 feat(otel-tracer): send telemetry for Tracer API usage

[ganeshnj]

What?

We want to track how many customers are using the OTel vs OT APIs

Schema update: DataDog/rum-events-format#190

How?

Send config telemetry events when tracer is get from a public API.

The initial plan to send the telemetry log when tracer is initialized which gives accurate data but for consistency reasons, we decided to use configuration telemetry. We may miss data for cases if the tracer is not initialized in first 5 seconds of the creation of configuration telemetry.

Review checklist

• Feature or bugfix MUST have appropriate tests (unit, integration)
• Make sure each commit and the PR mention the Issue number or JIRA reference
• Add CHANGELOG entry for user facing changes

Custom CI job configuration (optional)

• Run unit tests for Core, RUM, Trace, Logs, CR and WVT
• Run unit tests for Session Replay
• Run integration tests
• Run smoke tests
• Run tests for tools/

[maciejburda]

Shouldn't we track metric instead of debug in both cases?

[ganeshnj]

Shouldn't we track metric instead of debug in both cases?

When I was talking with @ncreated, recommendation was to use debug but happy to change whatever makes sense here. End goal is to have some tracking mechanism.

[ncreated]

Shouldn't we track metric instead of debug in both cases?

When I was talking with @ncreated, recommendation was to use debug but happy to change whatever makes sense here. End goal is to have some tracking mechanism.

It doesn't seem to be a metric use case to me. Even with debug logs we can still visualise or generate metrics.

[ncreated]

I can't find b41d863 in rum-events-format repo 🤔 - we need a PR-approved change merged to rum-events-format/master

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

[ganeshnj]

DataDog/rum-events-format#190

There are other unrelated issue due to branch being back.

[maxep]

LGTM 👍

[ncreated]

🎯