- Notifications
You must be signed in to change notification settings - Fork 508
Add awsfirehose integration package #7146
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
Add awsfirehose integration package #7146
Conversation
🌐 Coverage report
|
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 think you can remove the whole namespace block.
That's because you don't need to add the explicit fall back for default. Even if the documents don't contain the data_stream.namespace field, it will use the namespace from the current data stream name. If the logs are sent to logs-awsfirehose.log-default, the reroute processor will parse out default from that data stream name in case it can't find a data_stream.namespace field. See the options table in https://www.elastic.co/guide/en/elasticsearch/reference/current/reroute-processor.html for more details.
As {{data_stream.namespace}} is the default value for namespace, you can simply omit it.
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.
Ha good point thanks!! I realized elastic-package doesn't accept empty namespace, target_dataset or if so I'm adding it in elastic/elastic-package#1391. Will remove them afterwards.
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.
great work so far kaiyan - thanks !
some small comments, but overall looking great.
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'm trying to figure out if these (cloudwatch) fields live here or we should delegate all service-specific mappings to the downstream integrations. i think having the mapping here too is probably right, since then any generic logs shipped via cloudwatch at least have these fields. so after all, ignore this comment... :)
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 think for this integration in particular, it would be useful to use the dynamic ECS mappings instead of explicit mappings.
| This PR is getting too big to review. I will merge it first. @tommyers-elastic Let's keep the conversation ongoing and I will create separate PRs to address them. |
| Package awsfirehose - 0.1.0 containing this change is available at https://epr.elastic.co/search?package=awsfirehose |
| Hello @tommyers-elastic
|
| @lucabelluccini yes - but not yet, we still have work to do to figure out exactly what the upgrade process looks like for existing users, and how that works with fresh installs. for now the existing documentation is still accurate. the docs in the package contain more details on how to configure things right now and enable the routing. we will combine everything when it's time to GA the integration. |
| Thanks @tommyers-elastic |
What does this PR do?
WIP: Im working on using
routing-rules.ymlinstead.This PR is to add
awsfirehoseintegration package as its own package. This integration supportsrerouteprocessors to provide routing configurations for logs. For example, if the fieldaws.cloudwatch.log_streamvalue containsCloudTrail, then route this log entry from the defaultlogs-awsfirehose.logs-defaulttologs-aws.cloudtrail-defaultdata stream.The original plan is to add
awsfirehoseas an input package. But package spec does not support predefined pipelines in input packages nor routing rules. Please see elastic/package-spec#566 for more details.Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
awsfirehoseintegration andawsintegration assetslogs-awsfirehose.logs-0.1.0logs-awsfirehose.logs-default. For example:logs-aws.cloudtrail-defaultinstead and with message field all parsed by thecloudtrailingest pipelines.Screenshots
Related issues