Integration with `tracing-opentelemetry`'s metrics?

Open
  • Is something wrong?
#53 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
observability-sre

Research direction

No files, tests, or entry points are named. Start by comparing tracing-opentelemetry's MetricsLayer with the current direct OpenTelemetry SDK wrapping, then establish whether both approaches should be supported and what completion criteria would demonstrate that integration.

Written by the indexing model from the issue text.

Description

tracing-opentelemetry has a MetricsLayer type which offers some metrics functionality.

At the moment we directly wrap the Otel SDK.

Should we support both?

Dominant language
Rust
Stars
78
Forks
13
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pydantic/logfire-rust

All issues in pydantic/logfire-rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.