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

Update documentation with document_id #13739

Closed
urso opened this issue Sep 19, 2019 · 2 comments · Fixed by #15171
Closed

Update documentation with document_id #13739

urso opened this issue Sep 19, 2019 · 2 comments · Fixed by #15171
Assignees
Labels
docs libbeat Team:Integrations Label for the Integrations team v7.6.0

Comments

@urso
Copy link

urso commented Sep 19, 2019

PR #5844 adds the new document_id setting for json decoding. This configures the field in the JSON document, that is read into @metadata.id.

The elasticsearch output sets the document id @metadata.id if present and uses the create operation -> if ID exists already, event is not indexed again.

For other outputs the @metadata.id field is added to the event so it can be used by logstash.

The original PR mentions the new setting, but we have to add some more documentation about the impact.

@urso urso changed the title document_id Update documentation with document_id Sep 19, 2019
@dedemorton
Copy link
Contributor

We need to add a topic (all under the umbrella of de-duplication) that describes the various ways to configure document IDs: ES chooses, via JSON input, random, fingerprinting,

@urso
Copy link
Author

urso commented Nov 18, 2019

@ycombinator fyi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs libbeat Team:Integrations Label for the Integrations team v7.6.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants