Can this project be archived/deleted? (outdated as compared to official logstash grok patterns)

[AndrewMcQuerry]

This project is severely outdated and over the course of time, Google seems to think that this project is the one that should be first on the results list when search "logstash grok patterns". For most folks, they may never even realize that this project is "not" managed by Elastic and will rely on outdated grok patterns.

Can this project be archived or deleted or made private.. something that will remove it from the Google search results?

[boegel]

@itkovian Thoughts?

[wpoely86]

We're still using this. I'm also not sure in which sense this is outdated. The grok pattern still work fine. People are free to use them.

We can clarify the readme and description that this is not related at all to Elastic?

[AndrewMcQuerry]

Hi - Thanks for the response.

While the patterns may still "work fine", they aren't updated with the latest patterns that exist in the latest versions of Logstash. Primarily, the "ecs-v1" patterns.

Additionally, there seem to be large differences between the "legacy" patterns.
this repo: https://github.com/hpcugent/logstash-patterns/tree/master/files
official repo: https://github.com/logstash-plugins/logstash-patterns-core/tree/main/patterns/legacy

My concern here is more that Google seems to have determined over the years that this project should be shown higher in the search results than the official grok patterns authored by Elastic and shipped/included in latest logstash builds. Most folks (many folks on my team at work) simply search google for grok patterns and click on the first result.

I'm not sure what can be done. I understand that this project may not be able to be archived if it is still in use. Can it be marked as private?

If not, I understand.. just wanted to open dialog into the possibility of removing the confusion between these two projects.