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

Provide a Mapping from Logstash Configuration files to Data Prepper configurations #466

Closed
dlvenable opened this issue Oct 22, 2021 · 1 comment
Assignees
Milestone

Comments

@dlvenable
Copy link
Member

Is your feature request related to a problem? Please describe.

Beyond just parsing a Logstash configuration grammar, we must also be able map Logstash plugins and settings into Data Prepper plugins and settings.

Describe the solution you'd like

Provide a mapping file which can define how a Logstash plugin should map into Data Prepper.

@dlvenable dlvenable added this to the v1.2 milestone Oct 22, 2021
@dlvenable
Copy link
Member Author

I'd like to propose the following approach.

When a Logstash plugin is found, Data Prepper will look for a file at the classpath location:

com/amazon/dataprepper/logstash/mapping/{pluginName}.mapping.yaml

So for example, the elasticsearch plugin would load: com/amazon/dataprepper/logstash/mapping/elasticsearch.mapping.yaml

This file might look like:

name: opensearch

Or in the case of supporting the amazon_es plugin

name: opensearch
settingValues:
  sigv4: true

Where settingValues sets a specific value.

We also might have something like attributeNames which can convert names of attributes.

For example,

attributeNames:
  logstashAttributeA: dataPrepperAttributeB

dlvenable added a commit to dlvenable/data-prepper that referenced this issue Nov 11, 2021
…per as the mechanism for mapping plugins. This can be configure in the mapping YAML to allow detailed mapping configurations. opensearch-project#466

Signed-off-by: David Venable <[email protected]>
dlvenable added a commit to dlvenable/data-prepper that referenced this issue Nov 12, 2021
dlvenable added a commit that referenced this issue Nov 12, 2021
Refactored the DefaultPluginMapper to use LogstashPluginAttributesMapper as the mechanism for mapping plugins. This can be configure in the mapping YAML to allow detailed mapping configurations. #466

Signed-off-by: David Venable <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants