# How to filter OpenTelemetry array attributes in OpenPipeline Dynamic Routing?

**URL:** <https://community.dynatrace.com/t/how-to-filter-opentelemetry-array-attributes-in-openpipeline-dynamic-routing/56943>\
**Category:** DQL\
**Tags:** openpipeline, dql, logs\
**Created:** [September 14, 2026, 7:32pm UTC](https://community.dynatrace.com/t/how-to-filter-opentelemetry-array-attributes-in-openpipeline-dynamic-routing/56943 "2026-09-14T19:32:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Carl\_Me](https://avatars.discourse-cdn.com/v4/letter/c/87869e/32.png) [@Carl\_Me](https://community.dynatrace.com/u/Carl_Me)\
**Post date:** [September 14, 2026, 7:32pm UTC](https://community.dynatrace.com/t/how-to-filter-opentelemetry-array-attributes-in-openpipeline-dynamic-routing/56943/1 "2026-09-14T19:32:23Z")

</div>

Hi everyone,  
I’m looking for some guidance regarding OpenPipeline Dynamic Routing and filtering OpenTelemetry array attributes.  
I receive log records containing an attribute that is stored as an array, for example:

- [“1”, “2”]
- [“1”]
- [“2”]
- and potentially other values as well.&nbsp; ( equal or not equal )

My goal is to create routing rules based on the content of this array. However, I noticed that in the Dynamic Routing matcher, the array() function is not available and any expression using it returns the following error:

_Invalid matching condition. The function `array()` isn’t enabled._

Because of this limitation, I haven’t found a way to validate whether an array contains a specific value or to compare it against a list of expected values.

Has anyone successfully filtered OpenTelemetry array attributes in OpenPipeline Dynamic Routing?  
For example:

- Route logs when the array contains “1”
- Route logs when the array contains “2”
- Route logs when the array contains either “1” and “2”

Are there any supported functions, workarounds, transformations, or best practices to achieve this?

Thanks in advance for any suggestions!

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [September 15, 2026, 7:29pm UTC](https://community.dynatrace.com/t/how-to-filter-opentelemetry-array-attributes-in-openpipeline-dynamic-routing/56943/2 "2026-09-15T19:29:12Z")

</div>

[@Carl\_Me](https://community.dynatrace.com/user/56348)&nbsp; matchesValue or matchesPhrase will work on arrays too.&nbsp;[DQL matcher in OpenPipeline — Dynatrace Docs](https://docs.dynatrace.com/docs/shortlink/dql-matcher-openpipeline#lp-dql-matchesValue)

- Route logs when the array contains “1” - **matchesValue(myattribute, “1”)**
- Route logs when the array contains “2” -&nbsp;**matchesValue(myattribute, “2”)**
- Route logs when the array contains either “1” and “2” -&nbsp;**matchesValue(myattribute, “1”) and&nbsp;matchesValue(myattribute, “2”)**
