<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Request Attribute in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Best-practices-for-creating-request-attributes/m-p/201700#M23864</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/51369"&gt;@Peter_Youssef&lt;/a&gt;&amp;nbsp;, in general Request Attributes are helpful for data filtering.&amp;nbsp; A simple life example is a request attribute with the value of user login. If this request attribute is available inside every transaction you are able to filter transactions using user login and track user activity on the backend side (for example on the service view, or multidimensional view). You can also use request attribute to tag user sessions (browser perspective / user tag).&lt;/P&gt;</description>
    <pubDate>Sun, 08 Jan 2023 19:04:35 GMT</pubDate>
    <dc:creator>Rapidez</dc:creator>
    <dc:date>2023-01-08T19:04:35Z</dc:date>
    <item>
      <title>Best practices for creating request attributes</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Best-practices-for-creating-request-attributes/m-p/201695#M23861</link>
      <description>&lt;P&gt;Hello Dynatrace Professionals,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What are the best practices or use cases&amp;nbsp; or objectives of creating a request attribute in Dynatrace from a practical point of view as per your experience and lessons learned.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jan 2023 07:56:15 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Best-practices-for-creating-request-attributes/m-p/201695#M23861</guid>
      <dc:creator>Peter_Youssef</dc:creator>
      <dc:date>2023-01-09T07:56:15Z</dc:date>
    </item>
    <item>
      <title>Re: Request Attribute</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Best-practices-for-creating-request-attributes/m-p/201700#M23864</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/51369"&gt;@Peter_Youssef&lt;/a&gt;&amp;nbsp;, in general Request Attributes are helpful for data filtering.&amp;nbsp; A simple life example is a request attribute with the value of user login. If this request attribute is available inside every transaction you are able to filter transactions using user login and track user activity on the backend side (for example on the service view, or multidimensional view). You can also use request attribute to tag user sessions (browser perspective / user tag).&lt;/P&gt;</description>
      <pubDate>Sun, 08 Jan 2023 19:04:35 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Best-practices-for-creating-request-attributes/m-p/201700#M23864</guid>
      <dc:creator>Rapidez</dc:creator>
      <dc:date>2023-01-08T19:04:35Z</dc:date>
    </item>
    <item>
      <title>Re: Request Attribute</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Best-practices-for-creating-request-attributes/m-p/201727#M23872</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/45055"&gt;@Rapidez&lt;/a&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jan 2023 05:31:10 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Best-practices-for-creating-request-attributes/m-p/201727#M23872</guid>
      <dc:creator>Peter_Youssef</dc:creator>
      <dc:date>2023-01-09T05:31:10Z</dc:date>
    </item>
  </channel>
</rss>

