Increasing the user action per minute limit leads to analysis of more user sessions and, therefore, also increases your DEM consumption. Capture of the user session on the cluster side has no impact on the injection of the RUM JavaScript.Rate metrics (for example, JavaScript error rate, conversion rate, crash rate, and bounce rate) aren't impacted, since sessions are either captured fully or not at all.

All count metrics are impacted (for example, user session count, user action count, and conversion count).

Some of the sessions aren't captured and therefore no further analysis is applied. What is the impact on the data visible in the Dynatrace UI?ĭuring the event period, Dynatrace reduces the amount of captured user sessions on the cluster side. The maximum user action count per minute limit is specific to your environment and is there to prevent unexpected high consumption of your license volume by unexpected IT events like unannounced marketing campaigns, unplanned load tests, DDoS attacks, aggressive web scanners, or other. Why does Dynatrace change the capture rate? If the overall traffic volume drops, Dynatrace will automatically return to the capturing rate you've set for your environment. The throttling is done on a user session basis in order to provide statistically correct values in Dynatrace. Once this limit is reached, Dynatrace automatically throttles the number of user sessions being captured until the number of user actions is below the limit again. user actions per minute exceeded' event informs you that the number of user actions generated from Real User Monitoring (Web, Mobile, and OpenKit) has exceeded a limit that is specific to your environment.

user actions per minute exceeded` message mean?Ī 'Max.

Androidgradlepluginversion