Can't see any transaction at Insights/Backend/Caches | Sentry Community | Page 1

#

Hi @mighty vapor. I'm happy to dig into this for you! I'll check my internal sources for answers to your question! :wave:

#

The knowledge sources don’t describe your exact upgrade path, but they do show two key requirements for the Caches Insights page to work:

Correct feature flags
In a similar self‑hosted issue where the Caches page returned errors, it was fixed by enabling the feature flag:
```
"projects:span-metrics-extraction-addons"
```
in addition to the other Insights and span‑metrics flags you already listed.[Insights issue]

You’ve already added this flag, so from the docs’ perspective you now have the expected feature flags in place.

Proper cache span instrumentation
The Caches module only surfaces spans with span.op like cache.get / cache.put (and related cache ops). If your SDK is only emitting db.redis or other operations, those won’t appear on the Caches page.[Cache tx issue]

Make sure your application is actually sending cache spans that follow the cache module spec, for example (Java):

ISpan parentSpan = Sentry.getSpan();
if (parentSpan != null) {
    ISpan childSpan = parentSpan.startChild("cache.get", key);
    childSpan.setData("cache.hit", value != null);
    // optional: cache.item_size, cache.key, etc.
    childSpan.finish();
}
```[[Java caches](<https://docs.sentry.io/platforms/java/tracing/instrumentation/custom-instrumentation/caches-module/>)]

Or for .NET:

```csharp
var cacheSpan = SentrySdk.GetSpan()?.StartChild("cache.get");
cacheSpan?.SetData("cache.hit", true /* or false */);
cacheSpan?.Finish();
```[[Dotnet caches](<https://docs.sentry.io/platforms/dotnet/tracing/instrumentation/custom-instrumentation/caches-module/>)]

If, after confirming:

#

the feature flags (including projects:span-metrics-extraction-addons) are active, and
your services are emitting cache.get / cache.put spans as above,

you still see no data on Insights → Backend → Caches, then the knowledge sources don’t provide further self‑hosted‑specific debugging steps. In that case, you’d likely need to inspect your actual events (e.g., via Traces/Discover) to confirm that cache spans are present and match the cache module spec.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@mighty vapor Our robots are still learning and improving, please let us know if this response was correct by reacting below.

#Can't see any transaction at Insights/Backend/Caches

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: