APM: add known issue of lazy rollover bug #4459
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: inge4pres <[email protected]>
inge4pres
added
backport-8.15
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
Signed-off-by: inge4pres <[email protected]>
Signed-off-by: inge4pres <[email protected]>
simitt
requested changes
Oct 31, 2024
| The version check would fail any APM document produced with a different version of APM server compared to the version of the installed APM’s ingest pipeline. | ||
| In 8.13.0 the version check in the ingest pipeline was removed. | ||
| However, in 8.15.0 APM Server has a different way of managing data streams, that is not aware of the version check present in the ingest pipeline. | ||
| Thus, the leftover version check remains and prevents the ingestion of data. |
There was a problem hiding this comment.
I find this a bit confusing, and the main RC is the lazy rollover bug; how about:
Due to the combination of an internal change in how apm data management assets are set up from 8.15 onwards and a bug in Elasticsearch, related to lazy rollover of data streams, the ingestion pipeline conducting the version check is not removed on upgrade and prevents the ingestion of data.
There was a problem hiding this comment.
I was esitant to add a link to the ES issue, but yeah that makes it read better
Co-authored-by: simitt <[email protected]>
Signed-off-by: inge4pres <[email protected]>
Signed-off-by: inge4pres <[email protected]>
Signed-off-by: inge4pres <[email protected]>
simitt
approved these changes
Oct 31, 2024
bmorelli25
approved these changes
Oct 31, 2024
mergify bot
pushed a commit
that referenced
this pull request
Oct 31, 2024
Signed-off-by: inge4pres <[email protected]> Co-authored-by: simitt <[email protected]> (cherry picked from commit 66a73ef)
mergify bot
pushed a commit
that referenced
this pull request
Oct 31, 2024
Signed-off-by: inge4pres <[email protected]> Co-authored-by: simitt <[email protected]> (cherry picked from commit 66a73ef)
This was referenced Oct 31, 2024
colleenmcginnis
pushed a commit
that referenced
this pull request
Oct 31, 2024
Signed-off-by: inge4pres <[email protected]> Co-authored-by: simitt <[email protected]> (cherry picked from commit 66a73ef) Co-authored-by: Francesco Gualazzi <[email protected]>
colleenmcginnis
pushed a commit
that referenced
this pull request
Oct 31, 2024
Signed-off-by: inge4pres <[email protected]> Co-authored-by: simitt <[email protected]> (cherry picked from commit 66a73ef) Co-authored-by: Francesco Gualazzi <[email protected]>
mergify bot
pushed a commit
that referenced
this pull request
Oct 31, 2024
Signed-off-by: inge4pres <[email protected]> Co-authored-by: simitt <[email protected]> (cherry picked from commit 66a73ef)
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add a known issue section for APM to explain a problem occurring when upgrading to 8.15.0.
Documentation sets edited in this PR
Check all that apply.
docs/en/observability/*)docs/en/serverless/*)docs/en/integrations/*)Related issue
Closes #
Checklist
Follow-up tasks
Select one.