From 78d2715aba0599210bc9d20e0312da13a9823fba Mon Sep 17 00:00:00 2001
From: Harshini Rangaswamy
<108724024+harshini-rangaswamy@users.noreply.github.com>
Date: Wed, 5 Feb 2025 11:09:51 +0100
Subject: [PATCH] update: Added note about M3 deprecation (#673)
---
docs/platform/concepts/service_backups.md | 17 +----------------
docs/products/m3db.md | 16 +++++++---------
docs/products/m3db/get-started.md | 12 +++++++++++-
3 files changed, 19 insertions(+), 26 deletions(-)
diff --git a/docs/platform/concepts/service_backups.md b/docs/platform/concepts/service_backups.md
index 450e95693..2686f7c09 100644
--- a/docs/platform/concepts/service_backups.md
+++ b/docs/platform/concepts/service_backups.md
@@ -9,8 +9,7 @@ import Variables from "@site/static/variables.json"
Most services have automatic time-based backups that are encrypted and securely stored.
-**Backed-up services:** All Aiven services, except for Apache Kafka® and M3
-Aggregator/Coordinator.
+**Backed-up services:** All Aiven services, except for Apache Kafka®.
**Backup location:** Backups are stored in the object storage of the cloud region
where the service is first created, for example, S3 for AWS or GCS for GCP.
@@ -128,20 +127,6 @@ data.
Hourly backup up to 2 hours |
Plan not available |
-
- Aiven for M3 |
- Plan not available |
- Single day backup |
- Daily backup up to 6 days |
- Daily backup up to 13 days |
-
-
- Aiven for M3 Aggregator / Coordinator |
- Plan not available |
- Plan not available |
- No backups |
- No backups |
-
Aiven for Grafana® |
Plan not available |
diff --git a/docs/products/m3db.md b/docs/products/m3db.md
index 762d5b597..7301dfdb3 100644
--- a/docs/products/m3db.md
+++ b/docs/products/m3db.md
@@ -8,15 +8,13 @@ Aiven for M3 is a fully managed **distributed time series database**, deployable
Aiven for M3 consists of `n` number of **M3DB** and **M3 Coordinator**
pairs (where `n` is the number of nodes as chosen for your Aiven plan).
-M3 is a great choice if your organization has a very large volume of
-metrics to handle, and it can be used as part of your observability
-solution. It is optimized for storing and serving time series through
-associated pairs of times and values. It also provides a reverse index
-of time series.
-
-:::note
-Aiven offers M3 because we ourselves needed a solution that would work
-with the size of our own metrics.
+:::important
+Aiven for M3DB will be **deprecated later this year and will no longer be available**.
+Use [Aiven for Metrics](/docs/products/metrics), powered by Thanos, to store and
+query metrics efficiently.
+
+For details on the deprecation timeline and migration options, see
+[Aiven for M3DB end of life](/docs/platform/reference/end-of-life#aiven-for-m3db).
:::
Read more about [the M3
diff --git a/docs/products/m3db/get-started.md b/docs/products/m3db/get-started.md
index cbec1c4e9..679fb12c8 100644
--- a/docs/products/m3db/get-started.md
+++ b/docs/products/m3db/get-started.md
@@ -8,7 +8,17 @@ To begin your journey with Aiven for M3DB, there are two M3-related
services available in the [Aiven console](https://console.aiven.io).
Start with an **M3DB** service, which is responsible for data storage.
Follow
-[these instructions](/docs/platform/howto/create_new_service) to create an Aiven for M3DB service.
+[these instructions](/docs/platform/howto/create_new_service) to create an
+Aiven for M3DB service.
+
+:::important
+Aiven for M3DB will be deprecated later this year. Consider using
+[Aiven for Metrics](/docs/products/metrics) as an alternative.
+
+For details about the deprecation timeline and migration options, see
+[Aiven for M3DB end of life](/docs/platform/reference/end-of-life#aiven-for-m3db).
+:::
+
For initial experimentation with M3DB, you can opt for a single-node
setup using our startup plans. However, it is important to note that