Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Migrate telemetry to Open Telemetry standard #2680

Open
3 tasks
kpanot opened this issue Jan 9, 2025 · 0 comments
Open
3 tasks

[Feature]: Migrate telemetry to Open Telemetry standard #2680

kpanot opened this issue Jan 9, 2025 · 0 comments
Labels
enhancement New feature or request innovation Technical innovation triage

Comments

@kpanot
Copy link
Contributor

kpanot commented Jan 9, 2025

Context

In the current implementation of Otter there are 2 different package reporting telemetry information:

  • @o3r/telemetry: reporting information regarding the usage of CLIs, builders and schematics.
  • @o3r/logging: reporting application runtime information during the application life

The format of these data are not standard, not aligned and defined in each packages.

Proposal

Align and standalize the telemetry reported information to the Open Telemetry standard.
To do so, OpenTelemetry provides SDKs that can be used to simplified the formatting of the message and the collect of information.

The principal criteria:

  • Migrate @o3r/telemetry to OpenTelemetry standard
  • Implement Kibana boards for new format

Secondary criteria:

  • Implement (runtime) logger based on OpenTelemetry standard
@kpanot kpanot added enhancement New feature or request innovation Technical innovation triage labels Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request innovation Technical innovation triage
Projects
None yet
Development

No branches or pull requests

1 participant