11 Feb 2025
01:22 PM
- last edited on
17 Feb 2025
06:59 AM
by
MaciejNeumann
Hello,
Could not find this in any doc:
Solved! Go to Solution.
11 Feb 2025 06:24 PM
They're available if you need to override the default behavior in metric tables. Those will automatically be generated based on the original selector to collect the data for the currently selected column for sorting (metricSelectorSort) and for the the detailed data you can expand/view for rows in a metric table card (metricSelectorDetailed).
metricSelectorSort - This selector is used to gather data for currently sorted column. It should point to the single value. It queries data for whole table for given metric. e.g. for builtin:host.disk.free
selector, generated one will be builtin:host.disk.free$(entityFilter)$(userFilter):splitBy("dt.entity.disk")$(aggregation):last:sort(value(avg,$(sortOrder))):limit(X)
*Do not include limit operator. It will be appended automatically according to card configuration.
metricSelectorDetailed - This selector is used to gather data for details section in table row.e.g. for builtin:host.disk.free
selector, generated one will be builtin:host.disk.free$(entityFilter)$(userFilter):splitBy("dt.entity.disk")$(aggregation)
You only have a need to use these if the default generated ones don't work for you for some reason or another. Personally, in all my extensions I've never had a need for these but they are there for advanced use cases where it is needed.
11 Feb 2025 07:46 PM - edited 11 Feb 2025 07:47 PM
Hi James, thanks for your reply. Fyi noticed this after a 1.0 to 2.0 conversion….