You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Container Runtime Interface (CRI) initiative standardizes an API for container implementations. It defines its own format for logs, compatible with Docker json-file, but with an alternative implementation (no JSON).
We should update our Docker prospector to support that format, probably we can do autodetection just by checking first chars.
Created tests for specific CRI logs.
Autodiscovers by looking at first char and it will invoke CRI or Docker log parser depending on it.
Solution for elastic#5630
Adds support for CRI logs format.
Autodiscovers by looking at first char and it will invoke CRI or Docker log parser depending on it.
Solution for #5630
Container Runtime Interface (CRI) initiative standardizes an API for container implementations. It defines its own format for logs, compatible with Docker
json-file
, but with an alternative implementation (no JSON).We should update our Docker prospector to support that format, probably we can do autodetection just by checking first chars.
Example log line:
CRI-o project: https://github.com/kubernetes-incubator/cri-o
CRI-o code writing logs: https://github.com/mrunalp/cri-o/blob/37e282a29b84ca12b594cc55767295f37da848ea/conmon/conmon.c#L290-L407
The text was updated successfully, but these errors were encountered: