Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.14](backport #3857) Update APM anomaly known issue re: 8.13.3 #3859

Merged
merged 1 commit into from
May 8, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/en/observability/apm/known-issues.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -20,9 +20,9 @@ Link to fix
////

[[broken-apm-anomaly-rule]]
*Upgrading to v8.13 breaks APM anomaly rules* +
*Upgrading to v8.13.0 to v8.13.2 breaks APM anomaly rules* +
_Elastic Stack versions: 8.13.0, 8.13.1, 8.13.2_ +
_Fixed in Elastic Stack version 8.14.0_
_Fixed in Elastic Stack version 8.13.3_

// The conditions in which this issue occurs
This issue occurs when upgrading the Elastic Stack to version 8.13.0, 8.13.1, or 8.13.2.
Expand All @@ -35,11 +35,11 @@ The following log indicates the presence of this issue:

This issue occurs because a non-optional parameter, `anomalyDetectorTypes` was added in 8.13.0 without
the presence of an automation migration script. This breaks pre-existing rules as they do not have this parameter
and will fail validation. This issue is fixed in v8.14.0.
and will fail validation. This issue is fixed in v8.13.3.

There are three ways to fix this error:

* Upgrade to version 8.14.0 when it's released
* Upgrade to version 8.13.3
* Fix broken anomaly rules in the APM UI (no upgrade required)
* Fix broken anomaly rules with Kibana APIs (no upgrade required)

Expand Down