topic Re: Collection rules when one request attribute sets multiple data sources in Open Q&A

Collection rules when one request attribute sets multiple data sources

994620873 — Wed, 29 Jun 2022 12:56:44 GMT

When multiple data sources are set for one request attribute, only the first value is taken. What are the collection rules?

Re: Collection rules when one request attribute sets multiple data sources

Karolina_Linda — Wed, 29 Jun 2022 06:15:28 GMT

Hello @994620873!

I labeled your post with the request attributes label - I hope that way the experts on that topic will spot your question quicker 🙂

Have a great day and enjoy the Dynatrace Community!

Karolina

Re: Collection rules when one request attribute sets multiple data sources

pahofmann — Wed, 29 Jun 2022 09:31:01 GMT

If by collection rules you mean if only certain values are captured, then there are no extra rules.

All available values are captured and dynatrace then uses the first in the list as the value.

Re: Collection rules when one request attribute sets multiple data sources

994620873 — Fri, 01 Jul 2022 09:10:40 GMT

Thank you for your reply.

In the environment of the screenshot, I set five data sources, select the first value in the rule, but take the value of the third data source in purepath, what is the priority rule when setting multiple data sources?

Re: Collection rules when one request attribute sets multiple data sources

pahofmann — Mon, 04 Jul 2022 08:16:52 GMT

You can order the data sources with the little arrows. It goes down in priority from the top.

Re: Collection rules when one request attribute sets multiple data sources

994620873 — Mon, 04 Jul 2022 08:27:05 GMT

Among the five data sources in the screenshot, the parameter 'param' has the highest priority, but the third parameter 'web request url' is displayed in purepath.

Re: Collection rules when one request attribute sets multiple data sources

pahofmann — Mon, 04 Jul 2022 08:51:20 GMT

Ah sorry I now I get it.

If you look at the Request Attributes for the top service in that PurePath, it will only pick attributes from that node for the data sources.

The header in the screenshot is not on the request to the initial service but on a downstream call to an external service (Request to public network). That's why it is not picking it up.