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

Add 'MongoDB.Driver.Core.Extensions.DiagnosticSources' Support #3977

Closed
justurbo opened this issue Jan 22, 2025 · 2 comments
Closed

Add 'MongoDB.Driver.Core.Extensions.DiagnosticSources' Support #3977

justurbo opened this issue Jan 22, 2025 · 2 comments
Labels

Comments

@justurbo
Copy link

Feature Request

Add MongoDB Diagnostics as source to Auto Instrumentation.

I've set up observability of a C# .NET Core app within a Kubernetes cluster using a self-hosted Grafana LGTM (without Mimir) stack. OpenTelemetry sends data to Prometheus and is later viewed in a Grafana Tempo dashboard.

  1. Install kube-prometheus-stack
  2. Install opentelemetry-operator
  3. Add Kubernetes CDR OpenTelemetry Collector
  4. Add Kubernetes CDR OpenTelemetry .NET AutoInstrumentation
  5. Add .NET OpenTelemetry.AutoInstrumentation package
  6. Add .NET MongoDB.Driver.Core.Extensions.DiagnosticSource package

Expectation MongoDB traces are seen in the OpenTelemetry request trace.

Reality MongoDB activity is invisible to Grafana Tempo:

Grafana Tempo Dashboard

@RassK
Copy link
Contributor

RassK commented Jan 23, 2025

Doesn't byte code instrumentation work for you?

@Kielek
Copy link
Contributor

Kielek commented Feb 12, 2025

@justurbo , I am closing it. Feel free to reopen when you provide some more data. @RassK is still valid.

@Kielek Kielek closed this as not planned Won't fix, can't repro, duplicate, stale Feb 12, 2025
@Kielek Kielek added the stale label Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants