You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/alerts/proactive-diagnostics.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ Select a detection to view its details.
36
36
Smart detection detects and notifies about various issues, such as:
37
37
38
38
*[Smart detection - Failure Anomalies](./proactive-failure-diagnostics.md). We use machine learning to set the expected rate of failed requests for your app, correlating with load, and other factors. Notifies if the failure rate goes outside the expected envelope.
39
-
*[Smart detection - Performance Anomalies](./proactive-performance-diagnostics.md). Notifies if response time of an operation or dependency duration is slowing down, compared to historical baseline. It also notifies if we identify an anomalous pattern in response time, or page load time.
39
+
*[Smart detection - Performance Anomalies](./smart-detection-performance.md). Notifies if response time of an operation or dependency duration is slowing down, compared to historical baseline. It also notifies if we identify an anomalous pattern in response time, or page load time.
40
40
* General degradations and issues, like [Trace degradation](./proactive-trace-severity.md), [Memory leak](./proactive-potential-memory-leak.md), [Abnormal rise in Exception volume](./proactive-exception-volume.md) and [Security anti-patterns](./proactive-application-security-detection-pack.md).
41
41
42
42
(The help links in each notification take you to the relevant articles.)
Copy file name to clipboardExpand all lines: articles/azure-monitor/alerts/proactive-failure-diagnostics.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -415,7 +415,7 @@ Smart Detection of Failure Anomalies complements other similar but distinct feat
415
415
416
416
*[metric alerts](./alerts-log.md) are set by you and can monitor a wide range of metrics such as CPU occupancy, request rates, page load times, and so on. You can use them to warn you, for example, if you need to add more resources. By contrast, Smart Detection of Failure Anomalies covers a small range of critical metrics (currently only failed request rate), designed to notify you in near real-time manner once your web app's failed request rate increases compared to web app's normal behavior. Unlike metric alerts, Smart Detection automatically sets and updates thresholds in response changes in the behavior. Smart Detection also starts the diagnostic work for you, saving you time in resolving issues.
417
417
418
-
*[Smart Detection of performance anomalies](proactive-performance-diagnostics.md) also uses machine intelligence to discover unusual patterns in your metrics, and no configuration by you is required. But unlike Smart Detection of Failure Anomalies, the purpose of Smart Detection of performance anomalies is to find segments of your usage manifold that might be badly served - for example, by specific pages on a specific type of browser. The analysis is performed daily, and if any result is found, it's likely to be much less urgent than an alert. By contrast, the analysis for Failure Anomalies is performed continuously on incoming application data, and you will be notified within minutes if server failure rates are greater than expected.
418
+
*[Smart Detection of performance anomalies](smart-detection-performance.md) also uses machine intelligence to discover unusual patterns in your metrics, and no configuration by you is required. But unlike Smart Detection of Failure Anomalies, the purpose of Smart Detection of performance anomalies is to find segments of your usage manifold that might be badly served - for example, by specific pages on a specific type of browser. The analysis is performed daily, and if any result is found, it's likely to be much less urgent than an alert. By contrast, the analysis for Failure Anomalies is performed continuously on incoming application data, and you will be notified within minutes if server failure rates are greater than expected.
Copy file name to clipboardExpand all lines: articles/azure-monitor/alerts/smart-detection-performance.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ No, a notification doesn't mean that your app definitely has a problem. It's sim
36
36
The notifications include diagnostic information. Here's an example:
37
37
38
38
39
-

39
+

40
40
41
41
1.**Triage**. The notification shows you how many users or how many operations are affected. This information can help you assign a priority to the problem.
42
42
2.**Scope**. Is the problem affecting all traffic, or just some pages? Is it restricted to particular browsers or locations? This information can be obtained from the notification.
@@ -48,7 +48,7 @@ The notifications include diagnostic information. Here's an example:
48
48
49
49
Smart detection notifications are enabled by default. They are sent to users that have [Monitoring Reader](../../role-based-access-control/built-in-roles.md#monitoring-reader) and [Monitoring Contributor](../../role-based-access-control/built-in-roles.md#monitoring-contributor) access to the subscription in which the Application Insights resource resides. To change the default notification, either click **Configure** in the email notification, or open **Smart detection settings** in Application Insights.
* You can disable the default notification, and replace it with a specified list of emails.
54
54
@@ -130,7 +130,7 @@ Modern applications often adopt a micro services design approach, which in many
130
130
131
131
Example of dependency degradation notification:
132
132
133
-

133
+

134
134
135
135
Notice that it tells you:
136
136
@@ -146,18 +146,18 @@ Notice that it tells you:
146
146
147
147
## Smart detection of slow performing patterns
148
148
149
-
Application Insights finds performance issues that might only affect some portion of your users, or only affect users in some cases. For example, if a page loads slower on a specific browser types compared to others, or if a particular server handles requests more slowly than other servers. It can also discover problems that are associated with combinations of properties, such as slow page loads in one geographical area for clients using particular operating system.
149
+
Application Insights finds performance issues that might only affect some portion of your users, or only affect users in some cases. For example, if a page loads slower on a specific browser type compared to others, or if a particular server handles requests more slowly than other servers. It can also discover problems that are associated with combinations of properties, such as slow page loads in one geographical area for clients using particular operating system.
150
150
151
151
Anomalies like these are hard to detect just by inspecting the data, but are more common than you might think. Often they only surface when your customers complain. By that time, it's too late: the affected users are already switching to your competitors!
152
152
153
153
Currently, our algorithms look at page load times, request response times at the server, and dependency response times.
154
154
155
155
You don't have to set any thresholds or configure rules. Machine learning and data mining algorithms are used to detect abnormal patterns.
156
156
157
-

157
+

158
158
159
159
***When** shows the time the issue was detected.
160
-
***What** describes te problem that was detected, and th characteristics of the set of events that we found, which displayed the problem behavior.
160
+
***What** describes the problem that was detected, and th characteristics of the set of events that we found, which displayed the problem behavior.
161
161
* The table compares the poorly performing set with the average behavior of all other events.
162
162
163
163
Click the links to open Metric Explorer to view reports, filtered by the time and properties of the slow performing set.
0 commit comments