Document log_processing_rules for MySQL slow query logs #5237
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.
What does this PR do?
Add a missing
log_processing_rule
entry to the MySQL config samples.Motivation
Without this additional setting, the upcoming MySQL slow log parser (see https://github.com/DataDog/logs-backend/pull/6293) won't be able to extract any data, as the Agent would send logs on a line-by-line basis, instead of grouped as individual entries to the slow query log.
(This also means that users were seeing slow query logs line-by-line in the logs UI up to now, which is arguably a bug since slow query log lines only make sense when viewed as a group.)
Additional Notes
/
Review checklist (to be filled by reviewers)
changelog/
andintegration/
labels attached