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/mariadb/concepts-monitoring.md
+19-4Lines changed: 19 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,13 +50,28 @@ You can enable slow query logging on your server. These logs are also available
50
50
51
51
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.
52
52
53
-
## Service health
54
-
[Azure Service health](../service-health/overview.md) provides a view of all service health notifications in your subscription. You can set up Service Health alerts to notify you via your preferred communication channels when there are issues or changes that may affect the Azure services and regions you use.
53
+
## Planned maintenance notification
55
54
56
-
You can view scheduled maintenance events for Azure Database for MariaDB by using the **planned maintenance** event type. To learn how to create **service health alerts**, visit the [Create activity log alerts on service notifications](../service-health/alerts-activity-log-service-notifications.md) article.
55
+
**Planned maintenance notifications** allow you to receive alerts for upcoming planned maintenance to your Azure Database for MariaDB. 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.
56
+
57
+
> [!Note]
58
+
> 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.
59
+
60
+
### To receive planned maintenance notification
61
+
62
+
1. In the [portal](https://portal.azure.com), select **Service Health**.
63
+
2. In the **Alerts** section, select **Health alerts**.
64
+
3. Select **+ Add service health alert** and fill in the fields.
65
+
4. Fill out the required fields.
66
+
5. Choose the **Event type**, select **Planned maintenance** or **Select all**
67
+
6. In **Action groups** define how you would like to receive the alert (get an email, trigger a logic app etc.)
68
+
7. Ensure Enable rule upon creation is set to Yes.
69
+
8. Select **Create alert rule** to complete your alert
70
+
71
+
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).
57
72
58
73
> [!IMPORTANT]
59
-
> The planned maintenance notifications is available in preview for EAST US and UK South only.
74
+
> Planned maintenance notifications are currently in preview
Copy file name to clipboardExpand all lines: articles/mysql/concepts-monitoring.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,6 +47,7 @@ You can enable slow query and audit logging on your server. These logs are also
47
47
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.
48
48
49
49
## Planned maintenance notification
50
+
50
51
**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.
Copy file name to clipboardExpand all lines: articles/postgresql/concepts-monitoring.md
+19-4Lines changed: 19 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,13 +48,28 @@ You can enable logging on your server. These logs are also available through Azu
48
48
## Performance Recommendations
49
49
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.
50
50
51
-
## Service health
52
-
[Azure Service health](../service-health/overview.md) provides a view of all service health notifications in your subscription. You can set up Service Health alerts to notify you via your preferred communication channels when there are issues or changes that may affect the Azure services and regions you use.
51
+
## Planned maintenance notification
53
52
54
-
You can view scheduled maintenance events for Azure Database for PostgreSQL - Single Server by using the **planned maintenance** event type. To learn how to create **service health alerts**, visit the [Create activity log alerts on service notifications](../service-health/alerts-activity-log-service-notifications.md) article.
53
+
**Planned maintenance notifications** allow you to receive alerts for upcoming planned maintenance to your Azure Database for PostgreSQL - Single Server. 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.
54
+
55
+
> [!Note]
56
+
> 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.
57
+
58
+
### To receive planned maintenance notification
59
+
60
+
1. In the [portal](https://portal.azure.com), select **Service Health**.
61
+
2. In the **Alerts** section, select **Health alerts**.
62
+
3. Select **+ Add service health alert** and fill in the fields.
63
+
4. Fill out the required fields.
64
+
5. Choose the **Event type**, select **Planned maintenance** or **Select all**
65
+
6. In **Action groups** define how you would like to receive the alert (get an email, trigger a logic app etc.)
66
+
7. Ensure Enable rule upon creation is set to Yes.
67
+
8. Select **Create alert rule** to complete your alert
68
+
69
+
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).
55
70
56
71
> [!IMPORTANT]
57
-
> The planned maintenance notifications is available in preview for EAST US and UK South only.
72
+
> Planned maintenance notifications are currently in preview
58
73
59
74
## Next steps
60
75
- See [how to set up alerts](howto-alert-on-metric.md) for guidance on creating an alert on a metric.
0 commit comments