# Extensions 2.0 - How to use dimension filters **URL:** \ **Category:** Dynatrace Tips\ **Tags:** dynatrace-managed, extensions\ **Created:** [June 28, 2022, 9:39am UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625 "2022-06-28T09:39:10Z")\ **Posts on this page:** 16\ **Page:** 1

**Author:** ![Radu](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/radu/32/23351_2.png) [@Radu](https://community.dynatrace.com/u/Radu)\ **Post date:** [June 28, 2022, 9:39am UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/1 "2022-06-28T09:39:10Z")

**Use case** : add [dimension filters](https://www.dynatrace.com/support/help/shortlink/extension-yaml#filters) to an [Extension 2.0 YAML](https://www.dynatrace.com/support/help/extend-dynatrace/extensions20/extension-yaml) so that unwanted data can be filtered out. This can be implemented in the “dimensions” section of each data source definition (under “group” or “subgroup”). This post will use “[snmp](https://www.dynatrace.com/support/help/extend-dynatrace/extensions20/data-sources/snmp-extensions/snmp-schema-reference)” as the data source, but the implementation is the same across all [other data sources](https://www.dynatrace.com/support/help/shortlink/extensions20#data-sources). **Generic concept and syntax** : You can add a filter to a dimension in one of two ways: - **filter: const:\** - **const:** must be followed by a literal filter definition - **\** follows this syntax: - **$eq(\)** – check if **\** matches what you’re filtering - **$prefix(…)** – must begin with … - **$suffix(…)** - must end with … - **$contains(…)** – must contain … - **$and(\, \)** – can be used to chain two or more of the above expressions with AND operator - **$or(\, \)** – can be used to chain two or more of the above expressions with OR operator - **$not(\)** – can be used to negate an expression - **filter: var:\** - **var:** must be followed by the ID of a [defined variable](https://www.dynatrace.com/support/help/shortlink/extension-yaml#variables) (in the vars section) **Example 1** - I’m collecting a **sensor.value** metric (oid 1.0.0.0.0.3) from a table of sensors of my snmp device. The table exposes a dimension called **sensor.type** (oid 1.0.0.0.0.2) which is an integer value for the type of sensor. I know **sensor.type** 3 is a temperature sensor, so I only want to collect the value of this type of sensor. I will have to use filters to only select this dimension value. **YAML definition:** ```auto snmp:
- group: metrics
interval:
minutes: 1
subgroups:
- subgroup: sensor-data
table: true
dimensions:
- key: sensor.type
value: oid:1.0.0.0.0.2
filter: const:$eq(3)
metrics:
- key: sensor.value
value: oid:1.0.0.0.0.3 ``` **Example 2** - The F5 device has a lot of Traffic Profiles that may not be needed for monitoring. I want users to be able to filter out Traffic Profiles that they don’t want monitored. I must create a variable where users can enter syntax to filter out this data. **YAML definition:** ```auto vars:
id: profile-name-filter
type: pattern
displayName: Pattern to filter which Profies are monitored

snmp:
- group: traffic-profiles
interval:
minutes: 1
subgroups:
- subgroup: profile-metrics
table: true
dimensions:
- key: profile.name
value: oid:2.0.0.0.0.1
filter: var:profile-name-filter
metrics:
- key: some.profile.metric
value: oid:2.0.0.0.0.8 ``` Note: the variable field in the Monitoring configuration will take the same syntax as the literal filter definition explained earlier. The users see this: ![Radu_0-1656408990298.png](https://global.discourse-cdn.com/dynatrace/original/2X/2/230b9ba1158d1591e5b526549d5681709fa67487.png) ---

**Author:** ![tarjei](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/tarjei/32/39196_2.png) [@tarjei](https://community.dynatrace.com/u/tarjei)\ **Post date:** [June 28, 2022, 11:24am UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/2 "2022-06-28T11:24:43Z")

So this filtering should work? (It doesnt) ```auto - subgroup: ResourceGroup
wmiNamespace: "root\\mscluster"
query: SELECT State,Name FROM MSCluster_ResourceGroup WHERE Name!='Available Storage'
metrics:
- key: com.kanari.extension.wmi-cl.host.clusterresourcegroup.state
value: column:State
dimensions:
- key: resourcegroup.name
value: Name
filter: const:$contains("Clu") ``` ---

**Author:** ![Radu](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/radu/32/23351_2.png) [@Radu](https://community.dynatrace.com/u/Radu)\ **Post date:** [June 28, 2022, 11:27am UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/3 "2022-06-28T11:27:36Z")

Please remove the quotes around Clu. ---

**Author:** ![Radu](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/radu/32/23351_2.png) [@Radu](https://community.dynatrace.com/u/Radu)\ **Post date:** [June 28, 2022, 11:31am UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/4 "2022-06-28T11:31:28Z")

And also remember that value extraction in WMI always happens from Columns. You correct dimension definition is: ```auto - key: resourcegroup.name
value: column:Name
filter: const:$contains(Clu) ``` ---

**Author:** ![tarjei](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/tarjei/32/39196_2.png) [@tarjei](https://community.dynatrace.com/u/tarjei)\ **Post date:** [June 28, 2022, 11:50am UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/5 "2022-06-28T11:50:30Z")

It doesn’t work. Should I open a support case then? ---

**Author:** ![tarjei](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/tarjei/32/39196_2.png) [@tarjei](https://community.dynatrace.com/u/tarjei)\ **Post date:** [June 28, 2022, 11:51am UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/6 "2022-06-28T11:51:15Z")

This is the entire yaml: ```auto name: "custom:com.kanari.extension.wmi-cl"
version: "1.0.48"
minDynatraceVersion: "1.225"
author:
name: "Kanari AS"

vars:
- id: resourceGroupFilter
displayName: Resource Group Filter
type: pattern
- id: resourceFilter
displayName: Resource Filter
type: pattern
- id: nodeFilter
displayName: Node Filter
type: pattern
- id: networkinterfaceFilter
displayName: Network Interface Filter
type: pattern

metrics:
- key: com.kanari.extension.wmi-cl.host.clusterresourcegroup.state
metadata:
displayName: Cluster ResourceGroup State
description: State of the cluster resource group
unit: Count
- key: com.kanari.extension.wmi-cl.host.clusterresource.state
metadata:
displayName: Cluster Resource State
description: State of the cluster resource
unit: Count
- key: com.kanari.extension.wmi-cl.host.clusternode.state
metadata:
displayName: Cluster Node State
description: State of the cluster node
unit: Count
- key: com.kanari.extension.wmi-cl.host.clusternetworkinterface.state
metadata:
displayName: Cluster Network Interface State
description: State of the cluster network interface
unit: Count

wmi:
- group: Host
interval: 1m
subgroups:
- subgroup: Resource
wmiNamespace: "root\\mscluster"
query: SELECT State,Name FROM MSCluster_Resource
metrics:
- key: com.kanari.extension.wmi-cl.host.clusterresource.state
value: column:State
dimensions:
- key: resource.name
value: column:Name

- subgroup: Node
wmiNamespace: "root\\mscluster"
query: SELECT State,Name FROM MSCluster_Node
metrics:
- key: com.kanari.extension.wmi-cl.host.clusternode.state
value: column:State
dimensions:
- key: node.name
value: column:Name

- subgroup: ResourceGroup
wmiNamespace: "root\\mscluster"
query: SELECT State,Name FROM MSCluster_ResourceGroup WHERE Name!='Available Storage'
metrics:
- key: com.kanari.extension.wmi-cl.host.clusterresourcegroup.state
value: column:State
dimensions:
- key: resourcegroup.name
value: column:Name
filter: var:resourceGroupFilter
- subgroup: Node
wmiNamespace: "root\\mscluster"
query: SELECT State,Name FROM MSCluster_NetworkInterface
metrics:
- key: com.kanari.extension.wmi-cl.host.clusternetworkinterface.state
value: column:State
dimensions:
- key: networkinterface.name
value: column:Name

#vars:
# - id: resourceGroupFilter
# displayName: Pattern matching Resource Groups which should be ignored
# type: pattern

dashboards:
- path: "dashboards/windows_failover_clustering.json"

alerts:
- path: "alerts/node_high.json"
- path: "alerts/node_low.json"
- path: "alerts/cluster_resource_high.json"
- path: "alerts/cluster_resource_low.json"
- path: "alerts/cluster_resourcegroup_high.json"
- path: "alerts/cluster_resourcegroup_low.json"
- path: "alerts/nic_low.json"

screens:
- entityType: wmi:com_kanari_extension_wmi_cluster_instance
detailsSettings:
staticContent:
showProblems: true
showProperties: true
showTags: true
showGlobalFilter: true
showAddTag: true
layout:
autoGenerate: false
cards:
- type: "CHART_GROUP"
key: "host-clusterresources"
propertiesCard:
properties:
- type: RELATION
relation:
entitySelectorTemplate: type(host), toRelationships.runsOn($(entityConditions))
displayName: Host
chartsCards:
- key: "host-clusterresources"
displayName: "Cluster Resources"
numberOfVisibleCharts: 3
charts:
- displayName: "Cluster ResourceGroup State"
metrics:
- metricSelector: "com.kanari.extension.wmi-cl.host.clusterresourcegroup.state:SplitBy(\"resourcegroup.name\")"
- displayName: "Cluster Resource State"
metrics:
- metricSelector: "com.kanari.extension.wmi-cl.host.clusterresource.state:SplitBy(\"resource.name\")"
- displayName: "Cluster Network Interface State"
metrics:
- metricSelector: "com.kanari.extension.wmi-cl.host.clusternetworkinterface.state:SplitBy(\"networkinterface.name\")"
# entitiesListCards:
# - key: "cluster-nic-list"
# displayName: "Network Interfaces List"
# entitySelectorTemplate: "type(wmi:com_kanari_extension_wmi_cluster_network_interface),fromRelationships.runsOn($(entityConditions))"
# displayCharts: false
# displayIcons: true
# enableDetailsExpandability: tru
topology:
types:
- name: wmi:com_kanari_extension_wmi_cluster_instance
displayName: Cluster Instance
enabled: true
rules:
- idPattern: wmi_cluster_instance_{dt.entity.host}
sources:
- sourceType: Metrics
condition: $prefix(com.kanari.extension.wmi-cl.host)
attributes: []
requiredDimensions: []
instanceNamePattern: Cluster Instance on {dt.entity.host}
- idPattern: wmi_cluster_instance_{host}
sources:
- sourceType: Metrics
condition: $prefix(com.kanari.extension.wmi-cl.host)
attributes: []
requiredDimensions: []
instanceNamePattern: Cluster Instance on {host}
- name: wmi:com_kanari_extension_wmi_cluster_network_interface
displayName: Cluster Network Interface
enabled: true
rules:
- idPattern: wmi_cluster_network_interface_{dt.entity.host}
sources:
- sourceType: Metrics
condition: $prefix(com.kanari.extension.wmi-cl.host.clusternetworkinterface)
attributes: []
requiredDimensions: []
instanceNamePattern: Cluster Network Interface on {dt.entity.host} ``` ---

**Author:** ![Radu](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/radu/32/23351_2.png) [@Radu](https://community.dynatrace.com/u/Radu)\ **Post date:** [July 1, 2022, 8:16am UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/7 "2022-07-01T08:16:13Z")

Hi [@tarjei](https://community.dynatrace.com/user/12960) After some discussions I found out that for WMI, due to performance reasons, the filtering within the dimensions definition is disabled. Instead, filtering should be applied directly within the query. You can still use variables to expose the filter as a configuration parameter. This means that for WMI, the filtering takes [WQL syntax](https://docs.microsoft.com/en-us/windows/win32/wmisdk/where-clause) and not the syntax I documented eariler. The example from your extension would be: ```auto query: SELECT State,Name FROM MSCluster_ResourceGroup WHERE Name!='Available Storage' var:resourceGroupFilter
metrics:
- key: com.kanari.extension.wmi-cl.host.clusterresourcegroup.state
value: column:State
dimensions:
- key: resourcegroup.name
value: column:Name ``` Where resourceGroupFilter is a variable defined as before. Within the monitoring configuration you will have to add the additional syntax. For example, “Name starts with Clu” would be “AND Name LIKE ‘Clu%’” Could you try this approach and let me know if it fixes your issue? ---

**Author:** ![tarjei](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/tarjei/32/39196_2.png) [@tarjei](https://community.dynatrace.com/u/tarjei)\ **Post date:** [July 1, 2022, 9:41am UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/8 "2022-07-01T09:41:20Z")

Ok, Thank you! 🙂 I will try this. But you do understand my frustration with this? Would you happen to know when the documentation for ext 2.0 will get the desired TLC? ---

**Author:** ![tarjei](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/tarjei/32/39196_2.png) [@tarjei](https://community.dynatrace.com/u/tarjei)\ **Post date:** [July 1, 2022, 11:20am UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/9 "2022-07-01T11:20:44Z")

I tried it, but it did not work. ---

**Author:** ![Radu](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/radu/32/23351_2.png) [@Radu](https://community.dynatrace.com/u/Radu)\ **Post date:** [July 1, 2022, 11:34am UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/10 "2022-07-01T11:34:51Z")

Could you try one final variation please. Change the query to ```auto query: SELECT State,Name FROM MSCluster_ResourceGroup WHERE var:resourceGroupFilter ``` And add the whole Name filter in the var field of the UI. ---

**Author:** ![tarjei](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/tarjei/32/39196_2.png) [@tarjei](https://community.dynatrace.com/u/tarjei)\ **Post date:** [July 1, 2022, 12:12pm UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/11 "2022-07-01T12:12:10Z")

Hi! I have now tried multiple variants of this, but it doesnt work. ---

**Author:** ![tarjei](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/tarjei/32/39196_2.png) [@tarjei](https://community.dynatrace.com/u/tarjei)\ **Post date:** [February 7, 2023, 2:11pm UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/12 "2023-02-07T14:11:18Z")

Hi [@Radu](https://community.dynatrace.com/user/22272) this does not work. Is this because I have to use a specific schema version? ---

**Author:** ![tarjei](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/tarjei/32/39196_2.png) [@tarjei](https://community.dynatrace.com/u/tarjei)\ **Post date:** [February 7, 2023, 2:19pm UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/13 "2023-02-07T14:19:07Z")

Hi! I see that in Dynatrace IIS Extension, there is dimension filtering. That plugin is using 1.245 schema. [Microsoft IIS | Dynatrace Hub](https://www.dynatrace.com/hub/detail/microsoft-iis/?query=remote+w&offered=dynatrace#screenshots) ---

**Author:** ![Radu](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/radu/32/23351_2.png) [@Radu](https://community.dynatrace.com/u/Radu)\ **Post date:** [February 7, 2023, 2:38pm UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/14 "2023-02-07T14:38:18Z")

Please open a support ticket so we can troubleshoot this. The query looks correct but there may be other things happening that we cannot tell from the YAML alone. ---

**Author:** ![tarjei](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/tarjei/32/39196_2.png) [@tarjei](https://community.dynatrace.com/u/tarjei)\ **Post date:** [February 7, 2023, 4:10pm UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/15 "2023-02-07T16:10:07Z")

Hi! I have an ongoing discussion for this, will make them open a support case for it. Thank you! ---

**Author:** ![jegron](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/jegron/32/12797_2.png) [@jegron](https://community.dynatrace.com/u/jegron)\ **Post date:** [December 5, 2023, 10:45am UTC](https://community.dynatrace.com/t/extensions-2-0-how-to-use-dimension-filters/35625/16 "2023-12-05T10:45:12Z")

Hi [@Radu](https://community.dynatrace.com/user/22272) ! I believe there might not be any documentation available on this subject currently. Would it be possible to reach out to the documentation team for further information on this? Additionally, I’m looking to filter only interfaces specifically with the prefix ‘#’ : _vars:_ _- id: if\_alias_ _type: text_ _displayName: Pattern to filter capturing of Interfaces by Interface Alias_ _dimensions:_ _- key: if.alias_ _value: oid:1.3.6.1.2.1.31.1.1.1.18_ _filter: var:if\_alias_ I tried this syntax : ![jegron_0-1701772690529.png](https://global.discourse-cdn.com/dynatrace/original/3X/a/f/af144f7b744a0323fd770419d007d87ed5f05f63.png) It works but I also obtain all the interfaces which do not have the if alias filled in. How can I exclude them?