https://community.dynatrace.com/t5/Synthetic-Monitoring/Could-you-explain-the-concept-of-different-constraints-within/m-p/266844#M2933 <P>All NAM monitors have an obligatory <A href="https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-monitoring/network-availability-monitors/create-a-nam-monitor#step-level-constraints" target="_blank" rel="noopener">step-level constraint</A>. It is set on the Success rate percent and indicates the condition that needs to be fulfilled to consider the whole step as passed. &nbsp;<BR /><BR />Success rate percent is defined as the ratio of the number of requests that didn't fail to all requests. For example, if your NAM monitor contains 6 requests and 1 request out of 6 has failed, the ratio is (6-1)/6 = 83.33%. If your constraint is defined as ‘&gt;80%’, such execution of the monitor will be considered successful, as 83,3% is above 80%. But if you change your step-level constraint to 100%, the same scenario will cause the monitor’s failure. &nbsp;<BR />&nbsp;<BR /><A href="https://docs.dynatrace.com/docs/shortlink/nam-monitor#request-level-constraints" target="_self">Request-level constraints</A> also define conditions that need to be met to consider each request successful. Request-level constraints are different for different types of NAM monitors. Let’s focus on ICMP requests, as this is the most popular type of NAM monitor. &nbsp;<BR /><BR />We have an ICMP success rate percent constraint, defined as the ratio of the number of packets received to the number of packets sent. For example, if 5 packets (this is the configuration element) were sent and 4 were received, the ratio is 4/5 = 80.00%. If you define your ICMP success rate constraint as ‘&gt;75%’, such request is considered successful, but if you define your ICMP success rate constraint as ‘=100%’, such request is considered as failed.&nbsp;&nbsp;</P> <P>Have a look at the diagram illustrating how step-level constraints and request-level constraints work together for NAM ICMP Ping monitor.&nbsp;</P> <P><span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="nam.png" style="width: 999px;"><img src="https://community.dynatrace.com/t5/image/serverpage/image-id/25601i614CC3631F75ABC1/image-size/large?v=v2&amp;px=999" role="button" title="nam.png" alt="nam.png" /></span></P> <P>&nbsp;</P> <P>&nbsp;</P> Wed, 08 Jan 2025 14:56:36 GMT Jacek_Janowicz 2025-01-08T14:56:36Z https://community.dynatrace.com/t5/Synthetic-Monitoring/Could-you-explain-the-concept-of-different-constraints-within/m-p/266841#M2932 <P>What is their purpose?</P> Wed, 08 Jan 2025 09:21:10 GMT https://community.dynatrace.com/t5/Synthetic-Monitoring/Could-you-explain-the-concept-of-different-constraints-within/m-p/266841#M2932 GosiaMurawska 2025-01-08T09:21:10Z https://community.dynatrace.com/t5/Synthetic-Monitoring/Could-you-explain-the-concept-of-different-constraints-within/m-p/266844#M2933 <P>All NAM monitors have an obligatory <A href="https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-monitoring/network-availability-monitors/create-a-nam-monitor#step-level-constraints" target="_blank" rel="noopener">step-level constraint</A>. It is set on the Success rate percent and indicates the condition that needs to be fulfilled to consider the whole step as passed. &nbsp;<BR /><BR />Success rate percent is defined as the ratio of the number of requests that didn't fail to all requests. For example, if your NAM monitor contains 6 requests and 1 request out of 6 has failed, the ratio is (6-1)/6 = 83.33%. If your constraint is defined as ‘&gt;80%’, such execution of the monitor will be considered successful, as 83,3% is above 80%. But if you change your step-level constraint to 100%, the same scenario will cause the monitor’s failure. &nbsp;<BR />&nbsp;<BR /><A href="https://docs.dynatrace.com/docs/shortlink/nam-monitor#request-level-constraints" target="_self">Request-level constraints</A> also define conditions that need to be met to consider each request successful. Request-level constraints are different for different types of NAM monitors. Let’s focus on ICMP requests, as this is the most popular type of NAM monitor. &nbsp;<BR /><BR />We have an ICMP success rate percent constraint, defined as the ratio of the number of packets received to the number of packets sent. For example, if 5 packets (this is the configuration element) were sent and 4 were received, the ratio is 4/5 = 80.00%. If you define your ICMP success rate constraint as ‘&gt;75%’, such request is considered successful, but if you define your ICMP success rate constraint as ‘=100%’, such request is considered as failed.&nbsp;&nbsp;</P> <P>Have a look at the diagram illustrating how step-level constraints and request-level constraints work together for NAM ICMP Ping monitor.&nbsp;</P> <P><span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="nam.png" style="width: 999px;"><img src="https://community.dynatrace.com/t5/image/serverpage/image-id/25601i614CC3631F75ABC1/image-size/large?v=v2&amp;px=999" role="button" title="nam.png" alt="nam.png" /></span></P> <P>&nbsp;</P> <P>&nbsp;</P> Wed, 08 Jan 2025 14:56:36 GMT https://community.dynatrace.com/t5/Synthetic-Monitoring/Could-you-explain-the-concept-of-different-constraints-within/m-p/266844#M2933 Jacek_Janowicz 2025-01-08T14:56:36Z