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

Identify files based on their contents in Filebeat #19990

Closed
kvch opened this issue Jul 16, 2020 · 3 comments
Closed

Identify files based on their contents in Filebeat #19990

kvch opened this issue Jul 16, 2020 · 3 comments
Labels
enhancement Filebeat Filebeat Stalled Team:Services (Deprecated) Label for the former Integrations-Services team

Comments

@kvch
Copy link
Contributor

kvch commented Jul 16, 2020

Now multiple options are available to identify files in Filebeat: native, path and inode_marker since #18748. These options provide a quick method to generate an identifier for a file. However, in some use cases or on platforms these might not be sufficient.

More advanced identification can be implemented by fingerprinting full or partial contents of a file.

Follow up issue of #13492

@kvch kvch added enhancement Filebeat Filebeat Team:Services (Deprecated) Label for the former Integrations-Services team labels Jul 16, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations-services (Team:Services)

@botelastic
Copy link

botelastic bot commented Jan 27, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@botelastic botelastic bot added the Stalled label Jan 27, 2022
@jlind23
Copy link
Collaborator

jlind23 commented Mar 31, 2022

Backlog grooming: Closing for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Filebeat Filebeat Stalled Team:Services (Deprecated) Label for the former Integrations-Services team
Projects
None yet
Development

No branches or pull requests

4 participants