<?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: What is &amp;quot;Event&amp;quot; on Purepath screen ? in Dashboarding</title>
    <link>https://community.dynatrace.com/t5/Dashboarding/What-is-quot-Event-quot-on-Purepath-screen/m-p/81430#M290</link>
    <description>&lt;P&gt;Hello &lt;A rel="user" href="https://answers.dynatrace.com/users/25634/view.html" nodeid="25634"&gt;@Hiroshi K.&lt;/A&gt;,&lt;BR /&gt;&lt;BR /&gt;Below you can find an example of the "event" in the Purepath screen from our EasyTravel demo:&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/23821-opera-snapshot-2020-02-26-161647-vvl663managed-spr.png" /&gt;&lt;/P&gt;&lt;P&gt;If you click on it, you will see this screen:&lt;BR /&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/23784-opera-snapshot-2020-02-26-162512-vvl663managed-spr.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;As you can see, the service type is "Queue listener service" and &lt;STRONG&gt;the event&lt;/STRONG&gt; is "consume from request_queue". All of this is connected to the &lt;A rel="noopener noreferrer noopener noreferrer" href="https://en.wikipedia.org/wiki/Message_queue" target="_blank"&gt;Message queue&lt;/A&gt; and asynchronous communications protocols. You can read about event in them here:&lt;BR /&gt;&lt;BR /&gt;"Many of the more widely known communications protocols in use operate synchronously. The HTTP protocol – used in the World Wide Web and in web services – offers an obvious example where a user sends a request for a web page and then waits for a reply.&lt;/P&gt;&lt;P&gt;However, scenarios exist in which synchronous behaviour is not appropriate. For example, AJAX (Asynchronous JavaScript and XML) can be used to asynchronously send text, JSON or XML messages to update part of a web page with more relevant information. Google uses this approach for their Google Suggest, a search feature which sends the user's partially typed queries to Google's servers and returns a list of possible full queries the user might be interested in the process of typing. This list is asynchronously updated as the user types.&lt;/P&gt;&lt;P&gt;Other asynchronous examples exist in &lt;STRONG&gt;event&lt;/STRONG&gt; notification systems and publish/subscribe systems.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;An application may need to notify another that &lt;STRONG&gt;an event&lt;/STRONG&gt; has occurred, but does not need to wait for a response.&lt;/LI&gt;&lt;LI&gt;In publish/subscribe systems, an application "publishes" information for any number of clients to read.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;In both of the above examples it would not make sense for the sender of the information to have to wait if, for example, one of the recipients had crashed."&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 26 Feb 2020 15:51:25 GMT</pubDate>
    <dc:creator>MaciejNeumann</dc:creator>
    <dc:date>2020-02-26T15:51:25Z</dc:date>
    <item>
      <title>What is "Event" on Purepath screen ?</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/What-is-quot-Event-quot-on-Purepath-screen/m-p/81429#M289</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;I do not understand what "Event" is on Purepath screen.&lt;BR /&gt;Could anyone please give me an example and tell me?&lt;/P&gt;&lt;P&gt;Thank you for your support.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 13 Jul 2018 08:14:22 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/What-is-quot-Event-quot-on-Purepath-screen/m-p/81429#M289</guid>
      <dc:creator>hiroshi_kitahar</dc:creator>
      <dc:date>2018-07-13T08:14:22Z</dc:date>
    </item>
    <item>
      <title>Re: What is "Event" on Purepath screen ?</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/What-is-quot-Event-quot-on-Purepath-screen/m-p/81430#M290</link>
      <description>&lt;P&gt;Hello &lt;A rel="user" href="https://answers.dynatrace.com/users/25634/view.html" nodeid="25634"&gt;@Hiroshi K.&lt;/A&gt;,&lt;BR /&gt;&lt;BR /&gt;Below you can find an example of the "event" in the Purepath screen from our EasyTravel demo:&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/23821-opera-snapshot-2020-02-26-161647-vvl663managed-spr.png" /&gt;&lt;/P&gt;&lt;P&gt;If you click on it, you will see this screen:&lt;BR /&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/23784-opera-snapshot-2020-02-26-162512-vvl663managed-spr.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;As you can see, the service type is "Queue listener service" and &lt;STRONG&gt;the event&lt;/STRONG&gt; is "consume from request_queue". All of this is connected to the &lt;A rel="noopener noreferrer noopener noreferrer" href="https://en.wikipedia.org/wiki/Message_queue" target="_blank"&gt;Message queue&lt;/A&gt; and asynchronous communications protocols. You can read about event in them here:&lt;BR /&gt;&lt;BR /&gt;"Many of the more widely known communications protocols in use operate synchronously. The HTTP protocol – used in the World Wide Web and in web services – offers an obvious example where a user sends a request for a web page and then waits for a reply.&lt;/P&gt;&lt;P&gt;However, scenarios exist in which synchronous behaviour is not appropriate. For example, AJAX (Asynchronous JavaScript and XML) can be used to asynchronously send text, JSON or XML messages to update part of a web page with more relevant information. Google uses this approach for their Google Suggest, a search feature which sends the user's partially typed queries to Google's servers and returns a list of possible full queries the user might be interested in the process of typing. This list is asynchronously updated as the user types.&lt;/P&gt;&lt;P&gt;Other asynchronous examples exist in &lt;STRONG&gt;event&lt;/STRONG&gt; notification systems and publish/subscribe systems.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;An application may need to notify another that &lt;STRONG&gt;an event&lt;/STRONG&gt; has occurred, but does not need to wait for a response.&lt;/LI&gt;&lt;LI&gt;In publish/subscribe systems, an application "publishes" information for any number of clients to read.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;In both of the above examples it would not make sense for the sender of the information to have to wait if, for example, one of the recipients had crashed."&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2020 15:51:25 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/What-is-quot-Event-quot-on-Purepath-screen/m-p/81430#M290</guid>
      <dc:creator>MaciejNeumann</dc:creator>
      <dc:date>2020-02-26T15:51:25Z</dc:date>
    </item>
    <item>
      <title>Re: What is "Event" on Purepath screen ?</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/What-is-quot-Event-quot-on-Purepath-screen/m-p/81431#M291</link>
      <description>&lt;P&gt;Great answer, very well detailed! &lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2020 18:59:01 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/What-is-quot-Event-quot-on-Purepath-screen/m-p/81431#M291</guid>
      <dc:creator>justin_hogue</dc:creator>
      <dc:date>2020-02-26T18:59:01Z</dc:date>
    </item>
  </channel>
</rss>

