Aspire Doesn't Allow Filtering by Resource

OpenTelemetry as a standard provides a lot more insight into Community instances than was previously available. That said, Aspire's dashboard is far from the best OpenTelemetry collector/viewer. It's just a lightweight one to bundle as part of the compose definition as it's just a single container with minimal config. We use DataDog, which has robust filtering support. There are many options out there. I'd recommend taking a look at: Grafana or SigNoz (also pretty simple to use and OSS). 

OpenTelemetry as a standard provides a lot more insight into Community instances than was previously available. That said, Aspire's dashboard is far from the best OpenTelemetry collector/viewer. It's just a lightweight one to bundle as part of the compose definition as it's just a single container with minimal config. We use DataDog, which has robust filtering support. There are many options out there. I'd recommend taking a look at: Grafana or SigNoz (also pretty simple to use and OSS). 

But this is a development environment, so they seem like overkill just to monitor what's going on and why the many things aren't working. This isn't a general Aspire issue as I've used it in plenty of other projects with no issues, so seems to be how Community is using it.

The data that's available to be filtered/visible in Aspire (or any OTLP tool) is a function of how much data is configured to be shipped to OTLP. Community can send as much or as little as you want, scoped down to specific plugins or widened to everything. Please see the tracing, metrics, and logging configuration in Environment Configuration  as well as How can I externally monitor the health of Verint Community? .

I'm sorry but I don't see how this is an answer? There's something about how this data is being sent to Aspire that is causing filtering not to work. You might as well not ship it if your answer is to use something else as it's a terrible developer experience.

It is the answer. Aspire can only filter on what's sent to it. Community's logging intentionally does not send everything by default, as that would overwhelm. It is configurable by design. 

This isn't about *what* we're sending it's about what's there not being filtered. If you look at the two screenshots, one shows loads of data across multiple resources. The second one show it filtered by one of those resources, but it says there's no results. It's not about what's being sent to it, because the data is there, but there's something about it that doesn't match the filter.

It's a valid suggestion because it's often possible to see missing data for correlation in OTLP tools due to filtering levels.

As for why Aspire is not showing this particular log entry which it already has in its db could be a function of it having been pruned if it's old or an Aspire issue which is outside of the scope of this forum. We do not "ship" Aspire. 

It's part of the docker stack in dotnet new installer, so I'd say you do, but it's just semantics. Verint are putting it in and have even documented its presence. If you will not support it, I'd suggest removing it to avoid confusion for others. What I know for sure it's a very unsatisfactory developer experience. It's not about pruning as it's there if you toggle back to All, but nothing shows when choosing a resource.

We do not provide support for Aspire in the same way that we do not provide support for specific SMTP servers. Its presence in the compose stack is a convenience. And even the compose stack itself is provided purely as an example.

One other thing worth mentioning: I have sometimes observed Aspire to have duplicate entries in its drop-down for "Resource". If you have multiple "Web" entries, try others.