Those settings will do it but they are the global environment level settings so apply to all applications using the environment global settings. You can use those but you can also access application/service level settings by navigating to that entity's page in the UI and accessing the edit/setting there.
The affected user count doesn't actually trigger a problem event it's the crash rate itself calculated by version, the affected user count just adds context and is normally more of an informed estimate than a hard number. 'Automatically' means a learned dynamic baseline is used for detecting problems by app version so you can adjust this to make it more or less sensitive in various ways. You can switch that to use a fixed threshold but then it is no longer going to be baselining.
Similarly, you wouldn't want to adjust the settings for the services in the global settings you can do that per service as well and the same 'Automatically' -> dynamic baseline applies there as well. "Requests to unmonitored" hosts is a special bucket of requests though and includes traffic going to all endpoints not monitored by a OneAgent using a private IP address (public IP addresses would fall under "Requests to public networks." So understand that this affects quite a bit. You may want to split certain important requests that are under unmonitored hosts into their own service before adjusting settings. This can be done through things like custom devices or using the service detection API.
This page has some details on thresholds: https://www.dynatrace.com/support/help/how-to-use-dynatrace/problem-detection-and-analysis/problem-d...
You can also use custom metric events instead of/in addition to these built in types of events: https://www.dynatrace.com/support/help/how-to-use-dynatrace/problem-detection-and-analysis/problem-d...
Featured Posts
