Improving logging to troubleshoot pipeline metrics problem #91439
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
masseyke
added
>non-issue
:Data Management/Ingest Node
|
Pinging @elastic/es-data-management (Team:Data Management) |
elasticsearchmachine
added
the
Team:Data Management
joegallo
changed the title
joegallo
approved these changes
Nov 10, 2022
masseyke
added a commit
to masseyke/elasticsearch
that referenced
this pull request
Nov 16, 2022
elasticsearchmachine
pushed a commit
that referenced
this pull request
Nov 16, 2022
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.
We think that we have tracked down the problem of negative metrics (#90319) to be an exception happening in a pipeline. Unfortunately we're not currently getting any information about that exception in order to prevent it. This PR logs the exception when it detects the problem of a listener being called more than once (which is the source of the metrics problem). If the exception can be null, it logs it as a
new RuntimeException(e)so that we still get information about the stack regardless.