Add support for CRI-O based logs autodiscover

[vjsamuel]

This PR attempts to do two things:

• Allow docker input to be used generically for file paths instead of explicitly using container names.
• Make autodiscover generate CRI-O paths by default.

[elasticmachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[vjsamuel]

Fixes #8985 and #8988

[vjsamuel]

Failure looks like a flaky test

[jsoriano]

Thanks @vjsamuel for working on this, I think this new path option will be really helpful, it mostly LGTM.

I think we could maintain both options long-term, I still see ids as a more straightforward option for docker use cases and we may think on providing new inputs for other runtimes in the future, so I wouldn't think as ids as deprecated for docker. For this reason I'd also keep the tests for ids and would add tests for paths.

[jsoriano]

Failure looks like a flaky test

Try to update the branch with master, I think that at least the ML-related failures are fixed there.

[vjsamuel]

seems like yet another flaky test case on metricbeat

[jsoriano]

jenkins, test this

[jsoriano]

jenkins, test this again please

[jsoriano]

@vjsamuel for the followup (or here) could you also mention the new paths option in the changelog?

[jsoriano]

@vjsamuel I have merged this and opened a follow up to fix the changelog and add some docs for the new option #10864

[adelbot]

Hi, i don't understand the minimum beat version who is compatible CRI-O ?

[jsoriano]

Hey @adelbot, this change is available since 7.2.0.