Scrape crio logs, includes kata logs too

We see kata logs with `SYSLOG_IDENTIFIER:kata-runtime` under
`_SYSTEMD_UNIT:crio.service` in kibana. Need to verify if this holds
good for `SYSLOG_IDENTIFIER=kata-proxy` and `SYSLOG_IDENTIFIER=kata-shim`

Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
This commit is contained in:
Saikrishna
2018-12-05 23:39:44 +00:00
committed by Manohar Castelino
parent 8de91a2ba5
commit 845306aa86
@@ -320,7 +320,7 @@ data:
<source>
@id journald-container-runtime
@type systemd
matches [{ "_SYSTEMD_UNIT": "{{ container_runtime }}.service" }]
matches [{ "_SYSTEMD_UNIT": "crio.service" }]
<storage>
@type local
persistent true
@@ -330,16 +330,16 @@ data:
tag container-runtime
</source>
<source>
@type systemd
path /var/log/journal
matches [{"SYSLOG_IDENTIFIER": "kata-runtime"}, {"SYSLOG_IDENTIFIER": "kata-proxy"}, {"SYSLOG_IDENTIFIER": "kata-shim"}]
tag kata-containers
<entry>
fields_strip_underscores true
fields_lowercase true
</entry>
</source>
# <source>
# @type systemd
# path /var/log/journal
# matches [{"SYSLOG_IDENTIFIER": "kata-runtime"}, {"SYSLOG_IDENTIFIER": "kata-proxy"}, {"SYSLOG_IDENTIFIER": "kata-shim"}]
# tag kata-containers
# <entry>
# fields_strip_underscores true
# fields_lowercase true
# </entry>
# </source>
<source>
@id journald-kubelet