-
Notifications
You must be signed in to change notification settings - Fork 474
[AWS] Add lambda logs dataset #14070
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
[AWS] Add lambda logs dataset #14070
Conversation
…thomas/integrations into issue-262-new-lambda-dataset
🚀 Benchmarks reportPackage
|
Data stream | Previous EPS | New EPS | Diff (%) | Result |
---|---|---|---|---|
inspector |
2083.33 | 1760.56 | -322.77 (-15.49%) | 💔 |
rds |
23255.81 | 18181.82 | -5073.99 (-21.82%) | 💔 |
s3access |
4807.69 | 3745.32 | -1062.37 (-22.1%) | 💔 |
securityhub_findings |
2217.29 | 1191.9 | -1025.39 (-46.25%) | 💔 |
securityhub_findings_full_posture |
2202.64 | 1474.93 | -727.71 (-33.04%) | 💔 |
apigateway_logs |
19607.84 | 6250 | -13357.84 (-68.12%) | 💔 |
securityhub_insights |
1219.51 | 895.26 | -324.25 (-26.59%) | 💔 |
vpcflow |
10869.57 | 8403.36 | -2466.21 (-22.69%) | 💔 |
waf |
8547.01 | 6410.26 | -2136.75 (-25%) | 💔 |
cloudwatch_logs |
1e+06 | 500000 | -500000 (-50%) | 💔 |
config |
3891.05 | 1926.78 | -1964.27 (-50.48%) | 💔 |
ec2_metrics |
27777.78 | 22222.22 | -5555.56 (-20%) | 💔 |
emr_logs |
27777.78 | 23255.81 | -4521.97 (-16.28%) | 💔 |
To see the full report comment with /test benchmark fullreport
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
review as codeowner
packages/aws/data_stream/lambda_logs/elasticsearch/ingest_pipeline/aws-lambda-json.yml
Outdated
Show resolved
Hide resolved
packages/aws/data_stream/lambda_logs/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
…of set to collate pipeline errors
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM for SSI-owned files.
packages/aws/data_stream/lambda_logs/elasticsearch/ingest_pipeline/aws-lambda-json.yml
Show resolved
Hide resolved
packages/aws/data_stream/lambda_logs/elasticsearch/ingest_pipeline/aws-lambda-json.yml
Outdated
Show resolved
Hide resolved
packages/aws/data_stream/lambda_logs/elasticsearch/ingest_pipeline/aws-lambda-json.yml
Show resolved
Hide resolved
packages/aws/data_stream/lambda_logs/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe the ingest pipeline could be optimised by renaming parsed.record
to aws.lambda
once, as it's used in most places, instead of renaming it for each field individually. That said, I’ll leave the decision to you — everything else looks good to me.
packages/aws/data_stream/lambda_logs/_dev/test/pipeline/test-awslambda-platform-json.log
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left few nits and a minor follow up. Otherwise nice addition 🙌
/test |
1 similar comment
/test |
💚 Build Succeeded
History
|
|
Package aws - 3.6.0 containing this change is available at https://epr.elastic.co/package/aws/3.6.0/ |
Proposed commit message
Add a dataset for AWS lambda logs.
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
elastic-package build && elastic-package stack up -v -d --services package-registry
Screenshots
No screenshots added as part of this PR.