<?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: Definition of timeouts in RUM in Dynatrace API</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-API/Definition-of-timeouts-in-RUM/m-p/251837#M3290</link>
    <description>&lt;P&gt;For Browser Monitors, there is an option to increase the event and monitor timeout for both playback and execution on private locations. This is described in the information box &lt;A href="https://docs.dynatrace.com/docs/shortlink/id-brower-clickpath-events#wait" target="_self"&gt;here.&amp;nbsp;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Before increasing the timeout I would take a look at why the monitor is hitting the hard timeout. Are the pages loading as quickly as you expect? Have you added in waits that are not really needed? Often we can decrease the time a script takes to run by changing the waits. You can see the descriptions of the different wait strategies&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://www.dynatrace.com/support/help/how-to-use-dynatrace/synthetic-monitoring/browser-monitors/browser-clickpath-events#wait" target="_self" rel="noopener noreferrer"&gt;here.&lt;/A&gt;&amp;nbsp;&lt;STRONG&gt;Wait for specific element to appear&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;or&amp;nbsp;&lt;STRONG&gt;Wait for next event&amp;nbsp;&lt;/STRONG&gt;are usually good options to try in this scenario.&amp;nbsp;&lt;BR /&gt;That said, if you just have a really slow site and the monitor needs to navigate across many pages you may find you need to increase the hard timeout. We added an option to increase the hard timeout for Browser Monitors. It is only available in the API and you can find the documentation&amp;nbsp;&lt;A href="https://www.dynatrace.com/support/help/dynatrace-api/environment-api/synthetic-v2/synthetic-configuration-v2/put-configuration" target="_self" rel="noopener noreferrer"&gt;here&lt;/A&gt;.&lt;BR /&gt;&lt;SPAN class="model"&gt;&lt;SPAN class="prop"&gt;bmMonitorTimeout - browser monitor execution timeout (ms)&lt;BR /&gt;maximum:&amp;nbsp;900000&lt;BR /&gt;minimum:&amp;nbsp;60000&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV class="renderedMarkdown"&gt;
&lt;P&gt;bmStepTimeout - browser monitor single step execution timeout (ms)&lt;/P&gt;
&lt;/DIV&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class="model"&gt;&lt;SPAN class="prop"&gt;maximum:&amp;nbsp;180000&lt;BR /&gt;minimum:&amp;nbsp;10000&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 29 Jul 2024 10:52:04 GMT</pubDate>
    <dc:creator>HannahM</dc:creator>
    <dc:date>2024-07-29T10:52:04Z</dc:date>
    <item>
      <title>Definition of timeouts in RUM</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Definition-of-timeouts-in-RUM/m-p/250122#M3245</link>
      <description>&lt;P&gt;I have heard about the term "Embedded local playback timeout". What is the meaning of this &amp;amp; what is that timeout performan.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jul 2024 12:17:53 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Definition-of-timeouts-in-RUM/m-p/250122#M3245</guid>
      <dc:creator>JyotiSingh</dc:creator>
      <dc:date>2024-07-12T12:17:53Z</dc:date>
    </item>
    <item>
      <title>Re: Definition of timeouts in RUM</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Definition-of-timeouts-in-RUM/m-p/250143#M3246</link>
      <description>&lt;P&gt;Can you confirm what you heard this term in relation to? Possibly Session replay or Synthetic monitoring? Also, are you only interested in this in relation to APIs or is this a general question?&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jul 2024 07:51:38 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Definition-of-timeouts-in-RUM/m-p/250143#M3246</guid>
      <dc:creator>HannahM</dc:creator>
      <dc:date>2024-07-09T07:51:38Z</dc:date>
    </item>
    <item>
      <title>Re: Definition of timeouts in RUM</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Definition-of-timeouts-in-RUM/m-p/251696#M3278</link>
      <description>&lt;P&gt;It was in terms of browser monitor.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2024 09:49:41 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Definition-of-timeouts-in-RUM/m-p/251696#M3278</guid>
      <dc:creator>JyotiSingh</dc:creator>
      <dc:date>2024-07-26T09:49:41Z</dc:date>
    </item>
    <item>
      <title>Re: Definition of timeouts in RUM</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Definition-of-timeouts-in-RUM/m-p/251837#M3290</link>
      <description>&lt;P&gt;For Browser Monitors, there is an option to increase the event and monitor timeout for both playback and execution on private locations. This is described in the information box &lt;A href="https://docs.dynatrace.com/docs/shortlink/id-brower-clickpath-events#wait" target="_self"&gt;here.&amp;nbsp;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Before increasing the timeout I would take a look at why the monitor is hitting the hard timeout. Are the pages loading as quickly as you expect? Have you added in waits that are not really needed? Often we can decrease the time a script takes to run by changing the waits. You can see the descriptions of the different wait strategies&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://www.dynatrace.com/support/help/how-to-use-dynatrace/synthetic-monitoring/browser-monitors/browser-clickpath-events#wait" target="_self" rel="noopener noreferrer"&gt;here.&lt;/A&gt;&amp;nbsp;&lt;STRONG&gt;Wait for specific element to appear&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;or&amp;nbsp;&lt;STRONG&gt;Wait for next event&amp;nbsp;&lt;/STRONG&gt;are usually good options to try in this scenario.&amp;nbsp;&lt;BR /&gt;That said, if you just have a really slow site and the monitor needs to navigate across many pages you may find you need to increase the hard timeout. We added an option to increase the hard timeout for Browser Monitors. It is only available in the API and you can find the documentation&amp;nbsp;&lt;A href="https://www.dynatrace.com/support/help/dynatrace-api/environment-api/synthetic-v2/synthetic-configuration-v2/put-configuration" target="_self" rel="noopener noreferrer"&gt;here&lt;/A&gt;.&lt;BR /&gt;&lt;SPAN class="model"&gt;&lt;SPAN class="prop"&gt;bmMonitorTimeout - browser monitor execution timeout (ms)&lt;BR /&gt;maximum:&amp;nbsp;900000&lt;BR /&gt;minimum:&amp;nbsp;60000&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV class="renderedMarkdown"&gt;
&lt;P&gt;bmStepTimeout - browser monitor single step execution timeout (ms)&lt;/P&gt;
&lt;/DIV&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class="model"&gt;&lt;SPAN class="prop"&gt;maximum:&amp;nbsp;180000&lt;BR /&gt;minimum:&amp;nbsp;10000&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2024 10:52:04 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Definition-of-timeouts-in-RUM/m-p/251837#M3290</guid>
      <dc:creator>HannahM</dc:creator>
      <dc:date>2024-07-29T10:52:04Z</dc:date>
    </item>
    <item>
      <title>Re: Definition of timeouts in RUM</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Definition-of-timeouts-in-RUM/m-p/253120#M3314</link>
      <description>&lt;P&gt;Thank you for providing this detail explanation.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2024 06:13:09 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Definition-of-timeouts-in-RUM/m-p/253120#M3314</guid>
      <dc:creator>JyotiSingh</dc:creator>
      <dc:date>2024-08-12T06:13:09Z</dc:date>
    </item>
  </channel>
</rss>

