PMM-12287 Document removal of Integrated Alerting

documentation/docs/alert/contact_points.md

@@ -41,6 +41,7 @@ To use SMTP with a PMM Docker installation:
     - `GF_SMTP_FROM_NAME`: Name to be used when sending out emails.
 
     *NB: If you are using your Gmail’s SMTP credentials as shown above, you will have to generate an app password and fill it in as the value of your $GF_SMTP_PASSWORD variable.*
+
 2. Pass in the `.env` file to Docker run using the `--env-file` flag:
     ```
     docker run --env-file=.env -p 443:443 -p 80:80 percona/pmm-server:3
@@ -122,7 +123,7 @@ A policy will match an alert if the alert’s labels match all the matching labe
 This can be useful, for example, when you want to send notifications to a catch-all contact point as well as to one of more specific contact points handled by subsequent policies.
 6. Toggle **Override grouping** if you do not want to use root policy grouping.
 7. Toggle **Override general timings** to specify how often you want to wait until the initial notification is sent for a new group. When this is disabled, PMM uses root policy group timings instead.
-8. Add a mute timing if you want to mute notifications or this policy for a specific, regular interval. For example, you can create a mute to suppress trivial notifications during weekends.  Mute timings are different from silences in the sense that they are recurring, while silences have a fixed start and end time.
+8. Add a mute timing if you want to mute notifications or this policy for a specific, regular interval. For example, you can create a mute to suppress trivial notifications during weekends. Mute timings are different from silences in the sense that they are recurring, while silences have a fixed start and end time.
 
     !!! caution alert alert-warning "Important"
-        Time specified in mute timing must be in UTC and military format i.e. 14:00 not 2:00 PM.
+        Time specified in mute timing must be in UTC format, i.e. 14:00, not 2:00 PM.

documentation/docs/alert/index.md

@@ -13,5 +13,5 @@ Percona Alerting is powered by Grafana infrastructure. It leverages Grafana's ad
 Depending on the datasources that you want to query, and the complexity of your required evaluation criteria, Percona Alerting enables you to create the following types of alerts:
 
 - **Percona templated alerts**: alerts based on a set of Percona-supplied templates with common events and expressions for alerting.
-If you need custom expressions on which to base your alert rules, you can also create your own templates.
+If you want to use custom expressions in alert rules, you can create your own alert rule templates.
 - **Grafana managed alerts**: alerts that handle complex conditions and can span multiple different data sources like SQL, Prometheus, InfluxDB, etc. These alerts are stored and executed by Grafana.

documentation/docs/configure-pmm/alertmanager.md

@@ -5,7 +5,7 @@ Alertmanager manages alerts, de-duplicating, grouping, and routing them to the a
 This section lets you configure how VictoriaMetrics integrates with an external Alertmanager.
 
 !!! hint alert alert-success "Tip"
-    If possible, use [Integrated Alerting](../alert/index.md) instead of Alertmanager.
+    If possible, use [Percona Alerting](../alert/index.md) instead of Alertmanager.
 
 - The **Alertmanager URL** field should contain the URL of the Alertmanager which would serve your PMM alerts.
 - The **Prometheus Alerting rules** field is used to specify alerting rules in the YAML configuration format.

documentation/docs/release-notes/3.0.0.md

@@ -241,7 +241,7 @@ For the full list of affected plugins and guidance on migration, see [Grafana's
 
 We will provide regular updates on our migration progress in future releases to help you prepare for this change and modernize your dashboards.
 
-## Components upgrade
+## Component upgrades
 
 We've upgraded following PMM components to their latest stable versions to enhance functionality, security, and performance:
 

documentation/docs/release-notes/3.0.0_GA.md

@@ -0,0 +1,32 @@
+# Percona Monitoring and Management 3.0.0 
+
+| **Release date** | January 22nd, 2025                                                                                  |
+| ----------------- | :---------------------------------------------------------------------------------------------- |
+| **Installation** | [Installing Percona Monitoring and Management](../quickstart/index.md) |
+
+Percona Monitoring and Management (PMM) is an open source database monitoring, management, and observability solution for MySQL, PostgreSQL, and MongoDB.
+
+It enables you to observe the health of your database systems, explore new patterns in their behavior, troubleshoot them and execute database management operations—regardless of whether your databases are located on-premises or in the cloud.
+
+## Release summary
+PMM 3.0.0 introduces this and that
+
+
+## Release highlights
+
+### Finalized Integrated Alerting deprecation and API removal
+
+This release completes the deprecation of Integrated Alerting started in PMM 2.31.0 by removing its remaining components and APIs:
+
+- Removed all Integrated Alerting API endpoints, including `/v1/Settings/TestEmailAlertingSettings`
+- Removed Integrated Alerting-related fields from the PMM Settings API (`email_alerting_settings` and `slack_alerting_settings`)
+
+If you still have alert rules that haven't been migrated to Percona Alerting, use the [Integrated Alerting Migration Script](https://github.com/percona/pmm/blob/main/ia_migration.py) to migrate them. [Percona Alerting](../alert/index.md) provides enhanced capabilities through Grafana's alerting infrastructure and pre-configured Alert Rule Templates.
+
+## Improvements
+
+- [PMM-xxx](https://perconadev.atlassian.net/browse/PMM-xxx) - 
+
+## Fixed issues
+
+- [PMM-13360](https://perconadev.atlassian.net/browse/PMM-13360) - Fixed an issue in the MongoDB ReplSet Summary dashboard where nodes in `down` state would sometimes disappear from the **States** panel and their version information would be removed from the MongoDB Versions panel. Nodes in `down` state now remain visible with their last known version information preserved.

documentation/mkdocs-base.yml

@@ -269,9 +269,10 @@ nav:
     - Percona Alerting:
       - alert/index.md
       - alert/alert_rules.md
-      - alert/alert_notifications.md
+      - alert/contact_points.md
       - alert/templates_list.md
       - alert/silence_alerts.md
+      - alert/disable_alerts.md
     - Backup and restore: 
       - backup/index.md
       - backup/prepare_storage_location.md