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

Cherry-pick #24167 to 7.x: [Filebeat][AWS] Fix vpcflow pipeline exception: Cannot invoke "Object.getClass()" because "receiver" is null #24168

Merged
merged 1 commit into from
Feb 23, 2021

Conversation

adriansr
Copy link
Contributor

@adriansr adriansr commented Feb 22, 2021

Cherry-pick of PR #24167 to 7.x branch. Original message:

What does this PR do?

Fixes Filebeat's aws/vpcflow ingest pipeline to avoid painless exceptions when aws.vpcflow fields are missing in the ingested document. This happens for empty lines in text logs, or any lines that don't conform to the expected format.

Why is it important?

The fileset was generating documents with the following error.message:

Cannot invoke "Object.getClass()" because "receiver" is null

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.next.asciidoc or CHANGELOG-developer.next.asciidoc.

….getClass()" because "receiver" is null (elastic#24167)

The pipeline failed with an obscure error.message:
`Cannot invoke "Object.getClass()" because "receiver" is null`
when the ingested message didn't contain `aws.vpcflow.*` fiels.

Filebeat generates documents that lack those fields when parsing
lines from a .log file (not .json) that doesn't conform to the expected
formats. This happened for empty lines in particular.

(cherry picked from commit f4b7a25)
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 22, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Feb 22, 2021
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: Pull request #24168 opened

  • Start Time: 2021-02-22T22:50:25.852+0000

  • Duration: 50 min 29 sec

  • Commit: 0e16c53

Test stats 🧪

Test Results
Failed 0
Passed 6814
Skipped 1153
Total 7967

Trends 🧪

Image of Build Times

Image of Tests

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test Results
Failed 0
Passed 6814
Skipped 1153
Total 7967

@adriansr adriansr merged commit 7305b35 into elastic:7.x Feb 23, 2021
@zube zube bot removed the [zube]: Done label May 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants