[✨ Triage] dotnet/aspire#11798 by KalleOlaviNiemitalo - Structured log filter on existence of attribute #1555
Description
Triage for dotnet/aspire#11798.
Repo filter: area-dashboard issues.
MihuBot version: 554101.
Ping MihaZupan for any issues.
This is a test triage report generated by AI, aimed at helping the triage team quickly identify past issues/PRs that may be related.
Take any conclusions with a large grain of salt.
Tool logs
dotnet/aspire#11798: Structured log filter on existence of attribute by KalleOlaviNiemitalo
[Tool] Searching for structured log filter exists attribute, log filter parameter exists, filter condition exists not exists, structured logging filter dropdown, TraceSource Arg0 parameter logging (IncludeOpen=True, IncludeClosed=True, IncludeIssues=True, IncludePullRequests=False, Repository=dotnet/aspire)
[Tool] Found 56 issues, 107 comments, 37 returned results (16903 ms)
Here are related issues and discussions relevant to issue #11798 "Structured log filter on existence of attribute":
1. No direct support for "exists"/"not exists" filter conditions
No existing issue or PR directly implements or discusses adding "exists"/"not exists" conditions to the structured log filter UI. However, several issues and comments touch on the extensibility and limitations of the current filtering system:
2. Related filtering feature requests and discussions
Issue #848 (Nov 2023) - Filtering on Structured logs page
- Discusses the structured logs filter UI and its flexibility.
- Comments clarify that filtering is enabled for any field in the records, not just those shown, and multiple filters can be combined.
- No mention of "exists"/"not exists" conditions, but the infrastructure is described as flexible.
- Closed as duplicate of #896.
Issue #1313 (Dec 2023 - Feb 2024) - Dashboard - Add ability to see logs per available loggers
- Requests more advanced filtering, specifically by logger category.
- Comments indicate that category filtering was added to the structured logs filter dialog.
- No mention of existence-based filtering.
Issue #2571 (Mar 2024) - Standardize filter options and display between Resource and Structured Logs view
- Discusses aligning filtering capabilities between Resource and Structured Logs views.
- No mention of existence-based filtering.
Issue #2394 (Feb - Mar 2024) - Improve structured log detail
- Suggests making structured information more prominent and organized in the details pane.
- No mention of filter conditions.
Issue #719 (Nov 2023) - Error reminder isn't clear enough when clicking 'Apply Filter' without value typed in 'Filter' window on 'Structured Logs' page.
- Reports that the filter UI requires a value and gives only a subtle error when left empty.
- This matches your workaround attempt ("A value is required" error).
- No discussion of supporting filters that do not require a value (such as "exists").
3. Filtering by attributes in other telemetry types
Issue #5100 (Jul - Sep 2024) - Custom filtering by attributes in Traces
- Requests filtering traces and metrics by record attributes, similar to logs.
- Comments confirm that metrics already support attribute filtering, and traces will get this feature.
- No mention of existence-based filtering, but shows interest in attribute-based filtering generally.
Issue #5290 (Aug - Sep 2024) - Custom filters in dashboard traces
- Duplicate of #5100, confirms attribute filtering for traces will ship in Aspire 9.
Issue #1416 (Dec 2023 - Sep 2024) - Support filtering traces by request path
- Requests filtering traces by span properties (attributes).
- Comments clarify that generic attribute filtering is desired.
- Marked as duplicate of #5100.
4. Filtering by log level, severity, and other fields
Several issues discuss filtering by log level, severity, and category, but none mention existence-based filtering:
- #530 (Oct 2023) - Make filtering by Severity easy in structured logs view
- #2650 (Mar 2024) - Unable to select log level in dashboard structured logs page
- #703 (Nov 2023) - Changing 'Level' doesn't show filtered contents
5. Filtering UX and usability
- #2972 (Mar 2024 - Sep 2024) - Don't clear selected log entry in structured logs if filters are removed
- #4143 (May 2024 - Mar 2025) - Enable/Disable Structured Log Filters on Aspire Dashboard
6. Filtering by existence workaround
Your workaround ("Parameter: Arg0, Condition: !=, Value: (empty)") matches the limitation described in #719, where the filter UI requires a value and does not allow empty values, nor does it support existence-based conditions.
Summary
- No existing issue or PR adds "exists"/"not exists" conditions to the structured log filter UI.
- The current filter UI requires a value for all conditions, as confirmed by #719.
- Attribute-based filtering is a recurring request for logs, traces, and metrics, but always in the context of value-based conditions.
- The infrastructure is described as flexible, but the UI does not expose existence-based filtering.
- Your feature request is novel and not yet tracked or implemented.
Recommendation
- This is a valid feature request and not a duplicate.
- Reference #719 for the current limitation ("A value is required").
- Reference #848 and related issues for context on filter extensibility.
- Consider linking to attribute filtering requests in traces (#5100, #5290, #1416) to show broader interest in advanced filtering.
Let me know if you need a draft response or further breakdown!