Skip to content

Commit 8805192

Browse files
ambhatnaajlam
andauthored
Update articles/mysql/concepts-monitoring.md
Co-Authored-By: Andrea Lam <[email protected]>
1 parent 102cee2 commit 8805192

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/mysql/concepts-monitoring.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ You can enable slow query and audit logging on your server. These logs are also
4747
The [Performance Recommendations](concepts-performance-recommendations.md) feature identifies opportunities to improve workload performance. Performance Recommendations provides you with recommendations for creating new indexes that have the potential to improve the performance of your workloads. To produce index recommendations, the feature takes into consideration various database characteristics, including its schema and the workload as reported by Query Store. After implementing any performance recommendation, customers should test performance to evaluate the impact of those changes.
4848

4949
## Planned maintenance notification
50-
The **planned maintenance notification** feature allows you to receive alerts for upcoming planned maintenance to your Azure Database for MySQL. This feature utilizes the Azure portal’s [Service Health](../service-health/overview.md) blade – planned maintenance section to allow you to view all scheduled maintenance for your subscriptions all in one place. It also helps to scale the notification to the right audiences for different resource groups, as you may have different teams/contacts responsible for different resources. You will receive the notification about the upcoming maintenance 72 hours before the event.
50+
**Planned maintenance notifications** allow you to receive alerts for upcoming planned maintenance to your Azure Database for MySQL. These notifications are integrated with [Service Health's](../service-health/overview.md) planned maintenance and allows you to view all scheduled maintenance for your subscriptions in one place. It also helps to scale the notification to the right audiences for different resource groups, as you may have different teams/contacts responsible for different resources. You will receive the notification about the upcoming maintenance 72 hours before the event.
5151

5252
> [!Note]
5353
> We will make every attempt to provide **Planned maintenance notification** 72 hours before the event. In event of critical or security patch, we may have to proceed with the urgent deployment and can miss the 72 hours window for notifying you for this event.

0 commit comments

Comments
 (0)