Skip to content

Conversation

@masseyke
Copy link
Member

This moves the logAndBuildException() method into AbstractProcessor so that it can be used by other processors besides KeyValueProcessor.

@masseyke masseyke added >non-issue :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP v8.14.0 labels Mar 29, 2024
@masseyke masseyke requested a review from joegallo March 29, 2024 20:17
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

@masseyke masseyke merged commit c6a0d4f into elastic:main Mar 29, 2024
@masseyke masseyke deleted the extract-logAndBuildException branch March 29, 2024 21:29
if (logger.isTraceEnabled()) {
logger.trace(message, throwable);
} else {
logger.warn(longMessage);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Logging a warning on every ingest processor error seems like it could overwhelm the log, eg if a simple user error is hammered against the system. Why do we need to log user errors?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >non-issue Team:Data Management Meta label for data/management team v8.14.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants