-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 geoip steps generic and move to libbeat #10947
Conversation
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 I like it.
@andrewkroh @ph Can you review my changes? I made the content even more generic because I don't think it makes sense to talk about the location of clients within the docs for some of the Beats. Trying to find a balance between being generic enough, but not too vague. I'll push another change tomorrow to add content to the other Beats, but you can review the latest changes anytime. |
* Make geoip steps generic and move to libbeat * Add changes from review * Add topic to all the beats
* Make geoip steps generic and move to libbeat * Add changes from review * Add topic to all the beats
* Make geoip steps generic and move to libbeat * Add changes from review * Add topic to all the beats
…#10947) (elastic#11452) * Make geoip steps generic and move to libbeat (elastic#10947) * Make geoip steps generic and move to libbeat * Add changes from review * Add topic to all the beats * Add link to docs about adding geoip info (elastic#11395)
See #10941.
Note that the content is not simply moved. It's also be modified to be more generic and some of the wording has been improved.
TODO:
[] Add a section that describes how to add the field mapping in case the user wants to add a field that's not in the index templatestriking out because the template contains the fields we anticipate users will need.