Skip to content

Commit d87de03

Browse files
authored
Update concepts-monitoring.md
1 parent 53de4d7 commit d87de03

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/mysql/concepts-monitoring.md

Lines changed: 2 additions & 2 deletions
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-
**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.
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 allow 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 notice for all events. However, in cases of critical or security patches, notifications might be sent closer to the event or be omitted.
@@ -66,7 +66,7 @@ The [Performance Recommendations](concepts-performance-recommendations.md) featu
6666
For detailed steps on how to create **service health alerts**, refer to [Create activity log alerts on service notifications](../service-health/alerts-activity-log-service-notifications.md).
6767

6868
> [!IMPORTANT]
69-
> The planned maintenance notifications is in preview.
69+
> Planned maintenance notifications are currently in preview
7070
7171
## Next steps
7272
- See [How to set up alerts](howto-alert-on-metric.md) for guidance on creating an alert on a metric.

0 commit comments

Comments
 (0)