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

Improve multi_line debug logs #871

Merged
merged 2 commits into from
Mar 4, 2025
Merged

Improve multi_line debug logs #871

merged 2 commits into from
Mar 4, 2025

Conversation

strawgate
Copy link
Contributor

Fixes #870

Why is it important?

The current multi_line skipped message is a bit confusing and may lead a customer to believe the event has been skipped.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.md and updated share/version.py, if my change requires a new release.

Copy link

github-actions bot commented Mar 3, 2025

Minimum allowed coverage is 100%

Generated by 🐒 cobertura-action against e3fcf4a

@zmoog
Copy link
Contributor

zmoog commented Mar 4, 2025

Hey @strawgate, thanks for this PR. We'll fix the linter complaints and release an update.

@zmoog zmoog merged commit a464de3 into elastic:main Mar 4, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The "multi_line skipped" debug message is confusing
3 participants