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

Make packetbeat and filebeat better compatible with community beats #3635

Merged
merged 1 commit into from Feb 22, 2017

Conversation

ruflin
Copy link
Member

@ruflin ruflin commented Feb 21, 2017

Packetbeat and filebeat can be extended through protocols / modules. This requires both to be used as library if they are extended in their own beat. This is a first step to make it better compatible with this by adjusting import paths to depend on ES_BEATS.

Packetbeat and filebeat can be extended through protocols / modules. This requires both to be used as library if they are extended in their own beat. This is a first step to make it better compatible with this by adjusting import paths to depend on ES_BEATS.
@ruflin ruflin added :Generator Related to code generators for building custom Beats or modules. review labels Feb 21, 2017
@tsg
Copy link
Contributor

tsg commented Feb 22, 2017

jenkins, package it

@tsg tsg merged commit 4fa46d1 into elastic:master Feb 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Generator Related to code generators for building custom Beats or modules. review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants