# Routing of whole traces to a dedicated bucket and not only spans

**URL:** <https://community.dynatrace.com/t/routing-of-whole-traces-to-a-dedicated-bucket-and-not-only-spans/56940>\
**Category:** Open Q&A\
**Tags:** openpipeline, distributed-tracing\
**Created:** [September 14, 2026, 1:20pm UTC](https://community.dynatrace.com/t/routing-of-whole-traces-to-a-dedicated-bucket-and-not-only-spans/56940 "2026-09-14T13:20:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tesp11331](https://avatars.discourse-cdn.com/v4/letter/t/919ad9/32.png) [@tesp11331](https://community.dynatrace.com/u/tesp11331)\
**Post date:** [September 14, 2026, 1:20pm UTC](https://community.dynatrace.com/t/routing-of-whole-traces-to-a-dedicated-bucket-and-not-only-spans/56940/1 "2026-09-14T13:20:15Z")

</div>

Hi All,

recently I created a pipeline to route some spans to a dedicated bucket, my need is actually routing the whole trace those spans belong to and not only the single spans.

Is there a way to do it ?

Thanks

Regards

---

<div class="post-metadata">

**Author:** ![p\_devulapalli](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/p_devulapalli/32/41590_2.png) [@p\_devulapalli](https://community.dynatrace.com/u/p_devulapalli)\
**Post date:** [September 15, 2026, 12:23am UTC](https://community.dynatrace.com/t/routing-of-whole-traces-to-a-dedicated-bucket-and-not-only-spans/56940/2 "2026-09-15T00:23:22Z")

</div>

[@tesp11331](https://community.dynatrace.com/user/75770)&nbsp; trace is a logical reconstruction of all spans that share the same trace.id.&nbsp;When we are looking at a trace or run a DQL, Dynatrace recreates the trace by joining all spans with the same trace.id . You can use any common attribute that’s across the spans to make sure all spans part of the trace are routed to the same bucket.

---

<div class="post-metadata">

**Author:** ![tesp11331](https://avatars.discourse-cdn.com/v4/letter/t/919ad9/32.png) [@tesp11331](https://community.dynatrace.com/u/tesp11331)\
**Post date:** [September 16, 2026, 8:20am UTC](https://community.dynatrace.com/t/routing-of-whole-traces-to-a-dedicated-bucket-and-not-only-spans/56940/3 "2026-09-16T08:20:20Z")

</div>

Hi,&nbsp; it is not easy to find a common attribute across the spans that’s why I was asking for a different approach.

---

<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 17, 2026, 6:35am UTC](https://community.dynatrace.com/t/routing-of-whole-traces-to-a-dedicated-bucket-and-not-only-spans/56940/4 "2026-09-17T06:35:35Z")

</div>

[@tesp11331](https://community.dynatrace.com/user/75770)&nbsp;the condition can be much more complex, A or B or C in the bucket assignment.  
Typically, you would want to use resource attributes like dt.host\_group.id or k8s cluster or maybe primary grail tags.