Skip to content

Add FusionCache to registry#8871

Merged
svrnm merged 4 commits intoopen-telemetry:mainfrom
jodydonetti:add-fusioncache
Feb 12, 2026
Merged

Add FusionCache to registry#8871
svrnm merged 4 commits intoopen-telemetry:mainfrom
jodydonetti:add-fusioncache

Conversation

@jodydonetti
Copy link
Copy Markdown
Contributor

Description

FusionCache is an easy to use, fast and robust .NET hybrid cache with advanced resiliency features.

Since FusionCache natively supports OpenTelemetry (docs), I'm proposing adding it to the registry.

Pending Questions

Since FusionCache is a .NET library, it natively supports ActivitySource, Activity, Meter and Counter as a native bridge to OpenTelemetry: this way it does not require any custom package to work with it.

Because of this, in the YAML file I marked it as "native" and as the Nuget package I simply specified the main one.

Having said that, I also created a specific package to offer a more native experience for people wanting to explicitly use OpenTelemetry: this package offers a setup experience in line with the standard OTEL experience in .NET, like this:

services.AddOpenTelemetry()
  // SETUP TRACES
  .WithTracing(tracing => tracing
    .AddFusionCacheInstrumentation()
    .AddConsoleExporter()
  )
  // SETUP METRICS
  .WithMetrics(metrics => metrics
    .AddFusionCacheInstrumentation()
    .AddConsoleExporter()
  );

This is not strictly needed, but it's still nice to have.

So my question is: what should I do?

Meaning, one of:

  • keep the YAML file as-is, simply stating the native experience without the separate package?
  • create an additional YAML file for the separate package?
  • somehow list both in one YAMl file? (I don't know if it's possible to list multiple entries in the package element in the YAML file)

I'm adding the PR as draft to resolve this, please let me know.

Thanks!

@jodydonetti jodydonetti mentioned this pull request Jan 12, 2026
1 task
@jodydonetti jodydonetti force-pushed the add-fusioncache branch 2 times, most recently from 965a3ce to 0d88e73 Compare February 5, 2026 21:03
@jodydonetti jodydonetti marked this pull request as ready for review February 5, 2026 21:04
@jodydonetti jodydonetti requested a review from a team as a code owner February 5, 2026 21:04
Comment thread data/registry/instrumentation-dotnet-fusioncache.yml Outdated
Copy link
Copy Markdown
Member

@svrnm svrnm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

overall lgtm, let's make sure the linters work and then we can merge

Co-authored-by: Severin Neumann <severin.neumann@altmuehlnet.de>
@svrnm
Copy link
Copy Markdown
Member

svrnm commented Feb 12, 2026

/fix:all

@otelbot-docs
Copy link
Copy Markdown
Contributor

otelbot-docs Bot commented Feb 12, 2026

fix:all applied successfully in run 21941205897.

@svrnm svrnm added this pull request to the merge queue Feb 12, 2026
Merged via the queue into open-telemetry:main with commit 0a6c84e Feb 12, 2026
23 checks passed
@otelbot
Copy link
Copy Markdown
Contributor

otelbot Bot commented Feb 12, 2026

Thank you for your contribution @jodydonetti! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey.

@jodydonetti jodydonetti deleted the add-fusioncache branch February 12, 2026 11:31
@jodydonetti
Copy link
Copy Markdown
Contributor Author

Thanks everyone 🎉

Will fill the form asap.

clarissalimab pushed a commit to thoughtbot/opentelemetry.io that referenced this pull request Feb 12, 2026
Co-authored-by: Severin Neumann <severin.neumann@altmuehlnet.de>
Co-authored-by: otelbot <197425009+otelbot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants