Change expected migration date for alertmanager (#3250)

This commit is contained in:
Innokentii Konstantinov 2023-11-02 19:01:48 +08:00 committed by GitHub
parent 66a898df7d
commit 6367e3568e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 3 deletions

View file

@ -18,7 +18,7 @@ weight: 300
> ⚠️ A note about **(Legacy)** integrations:
> We are changing internal behaviour of AlertManager integration.
> Integrations that were created before version 1.3.21 are marked as **(Legacy)**.
> These integrations are still receiving and escalating alerts but will be automatically migrated after 1 November 2023.
> These integrations are still receiving and escalating alerts but will be automatically migrated in Q1 2024.
> <br/><br/>
> To ensure a smooth transition you can migrate legacy integrations by yourself now.
> [Here][migration] you can read more about changes and migration process.

View file

@ -17,7 +17,7 @@ weight: 100
> ⚠️ A note about **(Legacy)** integrations:
> We are changing internal behaviour of Grafana Alerting integration.
> Integrations that were created before version 1.3.21 are marked as **(Legacy)**.
> These integrations are still receiving and escalating alerts but will be automatically migrated after 1 November 2023.
> These integrations are still receiving and escalating alerts but will be automatically migrated in Q1 2024.
> <br/><br/>
> To ensure a smooth transition you can migrate them by yourself now.
> [Here][migration] you can read more about changes and migration process.

View file

@ -279,7 +279,7 @@ class Integration extends React.Component<IntegrationProps, IntegrationState> {
<VerticalGroup>
<Text type="secondary">
We are introducing a new {getDisplayName()} integration. The existing integration is marked as Legacy
and will be migrated after 1 November 2023.
and will be migrated in Q1 2024.
</Text>
<Text type="secondary">
To ensure a smooth transition you can migrate now using "Migrate" button in the menu on the right.