When true, the from/to values are auto-computed from data min/max span timestamps on load.
Debounce delay in milliseconds applied to text filters. 0 disables debouncing.
Dot-path or special key (e.g. 'spanName', 'serviceName', 'hasError', '*') the filter matches on.
Human-readable label rendered next to the control.
Dropdown options. Use string[] for simple values or FilterOption[] for value/label pairs.
How to populate dropdown options: 'static' (from attribute) or 'auto' (from data).
Placeholder text for text and datetime-range inputs. Empty string when not set.
When true, fetch is gated until the user supplies a value.
Whether the filter runs client-side or is pushed to the data source.
Whether the filter matches span-level fields or per-log event attributes.
Which UI control to render.
Pixel width of the rendered control. 0 falls back to the default per type.
Parsed representation of a
<trace-filter>child element's attributes.One config per filter field.
<trace-visualizer>collects these from any<trace-filter>children at connect time, but they can also be supplied programmatically viaTraceVisualizerConfig.filterConfigs.The config drives both the rendered control (via FilterFieldType) and the matching logic in
filterSpans(fromfilter.ts) /buildQueryParams(fromfilter.ts).