-
Notifications
You must be signed in to change notification settings - Fork 562
[aws]: guardduty error message is unhelpful #11090
Copy link
Copy link
Closed
Labels
Integration:awsAWSAWSTeam:Obs-InfraObsObservability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]Team:Security-Service IntegrationsSecurity Service Integrations team [elastic/security-service-integrations]Security Service Integrations team [elastic/security-service-integrations]bugSomething isn't working, use only for issuesSomething isn't working, use only for issuesneeds:triage
Metadata
Metadata
Assignees
Labels
Integration:awsAWSAWSTeam:Obs-InfraObsObservability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]Team:Security-Service IntegrationsSecurity Service Integrations team [elastic/security-service-integrations]Security Service Integrations team [elastic/security-service-integrations]bugSomething isn't working, use only for issuesSomething isn't working, use only for issuesneeds:triage
Type
Fields
Give feedbackNo fields configured for issues without a type.
Integration Name
AWS [aws]
Dataset Name
aws.guardduty aws.elb_logs
Integration Version
2.24.1
Agent Version
8.15.0
Agent Output Type
elasticsearch
Elasticsearch Version
8.15.0
OS Version and Architecture
ubuntu 20.04 LTS
Software/API Version
AWS
Error Message
freshly started ingesting AWS logs, for now Guardduty and ELB logs. all of them end up with event.kind: pipeline_error and error.message: "Cannot invoke "java.lang.CharSequence.length()" because "this.wrapped" is null"
Event Original
7b7f2b74-4804-3097-9879-07bb6e432af9.jsonl.json
For Guardduty, created some example findings, as can be found above.
resulting document:
resulting_document.json
What did you do?
ingest AWS guardduty and ELB logs from S3 via SQS notifications
What did you see?
pipeline_error and error.message
What did you expect to see?
no pipeline_error and no error.message
Anything else?
at a first glance, the fields seem to be parsed all well, dashboards show data. the pipeline_error and error.message are very irritating.