Description of problem:
There are too many "No Action Needed for xxxxxxxxx" logs in rsyslog pod logs. It's hard for users to know what happened in rsyslog pod when checking the rsyslog logs.

For example:
No Action Needed for  { "msg": "environment variable TZ is not set, auto correcting this to TZ=\/etc\/localtime  [v8.37.0-9.el7 try http:\/\/www.rsyslog.com\/e\/2442 ]", "rawmsg": "environment variable TZ is not set, auto correcting this to TZ=\/etc\/localtime  [v8.37.0-9.el7 try http:\/\/www.rsyslog.com\/e\/2442 ]", "timereported": "2019-07-16T07:29:11.668367+00:00", "hostname": "rsyslog-gkqvh", "syslogtag": "rsyslogd-2442:", "inputname": "rsyslogd", "fromhost": "rsyslog-gkqvh", "fromhost-ip": "127.0.0.1", "pri": "44", "syslogfacility": "5", "syslogseverity": "4", "timegenerated": "2019-07-16T07:29:11.668367+00:00", "programname": "rsyslogd-2442", "protocol-version": "0", "structured-data": "-", "app-name": "rsyslogd-2442", "procid": "-", "msgid": "-", "uuid": null, "$!": { "level": "unknown", "pipeline_metadata": { "collector": { "name": "rsyslog", "inputname": "rsyslogd", "received_at": "2019-07-16T07:29:11.668367+00:00", "ipaddr4": "10.0.168.134", "ipaddr6": "::ffff:10.0.168.134", "version": "8.37.0-9.el7 " } } } }
No Action Needed for  { "msg": " [origin software=\"rsyslogd\" swVersion=\"8.37.0-9.el7\" x-pid=\"14\" x-info=\"http:\/\/www.rsyslog.com\"] start", "rawmsg": " [origin software=\"rsyslogd\" swVersion=\"8.37.0-9.el7\" x-pid=\"14\" x-info=\"http:\/\/www.rsyslog.com\"] start", "timereported": "2019-07-16T07:29:11.677199+00:00", "hostname": "rsyslog-gkqvh", "syslogtag": "rsyslogd:", "inputname": "rsyslogd", "fromhost": "rsyslog-gkqvh", "fromhost-ip": "127.0.0.1", "pri": "46", "syslogfacility": "5", "syslogseverity": "6", "timegenerated": "2019-07-16T07:29:11.677199+00:00", "programname": "rsyslogd", "protocol-version": "0", "structured-data": "-", "app-name": "rsyslogd", "procid": "-", "msgid": "-", "uuid": null, "$!": { "level": "unknown", "pipeline_metadata": { "collector": { "name": "rsyslog", "inputname": "rsyslogd", "received_at": "2019-07-16T07:29:11.677199+00:00", "ipaddr4": "10.0.168.134", "ipaddr6": "::ffff:10.0.168.134", "version": "8.37.0-9.el7 " } } } }
Jul 16 07:29:11 rsyslog-gkqvh rsyslogd-2442: environment variable TZ is not set, auto correcting this to TZ=/etc/localtime  [v8.37.0-9.el7 try http://www.rsyslog.com/e/2442 ]
Jul 16 07:29:11 rsyslog-gkqvh rsyslogd: [origin software="rsyslogd" swVersion="8.37.0-9.el7" x-pid="14" x-info="http://www.rsyslog.com"] start
No Action Needed for  { "msg": "crio-df0fa4cb425d0dc1fbcc832ef7abd9e921138c6c07bc6c6f92ebf29dc2989201.scope: Consumed 23ms CPU time", "rawmsg": "crio-df0fa4cb425d0dc1fbcc832ef7abd9e921138c6c07bc6c6f92ebf29dc2989201.scope: Consumed 23ms CPU time", "timereported": "2019-07-16T07:29:02.975820+00:00", "hostname": "rsyslog-gkqvh", "syslogtag": "systemd[1]:", "inputname": "imjournal", "fromhost": "rsyslog-gkqvh", "fromhost-ip": "127.0.0.1", "pri": "30", "syslogfacility": "3", "syslogseverity": "6", "timegenerated": "2019-07-16T07:29:02.975820+00:00", "programname": "systemd", "protocol-version": "0", "structured-data": "-", "app-name": "systemd", "procid": "1", "msgid": "-", "uuid": null, "$!": { "hostname": "10-0-168-134.kubelet.kube-system.svc.cluster.local", "level": "info", "@timestamp": "2019-07-16T07:29:02.975820+00:00", "CODE_FUNC": "unit_log_resources", "INVOCATION_ID": "90cb8de20113463f8cec9cad847dbf51", "CPU_USAGE_NSEC": "23101733", "message": "crio-df0fa4cb425d0dc1fbcc832ef7abd9e921138c6c07bc6c6f92ebf29dc2989201.scope: Consumed 23ms CPU time", "pipeline_metadata": { "collector": { "original_raw_message": "crio-df0fa4cb425d0dc1fbcc832ef7abd9e921138c6c07bc6c6f92ebf29dc2989201.scope: Consumed 23ms CPU time", "name": "rsyslog", "inputname": "imjournal", "received_at": "2019-07-16T07:29:02.975820+00:00", "ipaddr4": "10.0.168.134", "ipaddr6": "::ffff:10.0.168.134", "version": "8.37.0-9.el7 " } }, "systemd": { "t": { "MACHINE_ID": "ec2b91c00b035ae38424333fa90822cb", "BOOT_ID": "20bdf7e620f34e0687fab900c64b7d18", "CAP_EFFECTIVE": "3fffffffff", "CMDLINE": "\/usr\/lib\/systemd\/systemd --switched-root --system --deserialize 16", "COMM": "systemd", "EXE": "\/usr\/lib\/systemd\/systemd", "GID": "0", "HOSTNAME": "ip-10-0-168-134", "PID": "1", "SELINUX_CONTEXT": "system_u:system_r:init_t:s0", "SOURCE_REALTIME_TIMESTAMP": "1563262142975803", "SYSTEMD_CGROUP": "\/init.scope", "SYSTEMD_SLICE": "-.slice", "SYSTEMD_UNIT": "init.scope", "TRANSPORT": "journal", "UID": "0" }, "u": { "CODE_FILE": "..\/src\/core\/unit.c", "CODE_LINE": "2272", "MESSAGE_ID": "ae8f7b866b0347b9af31fe1c80b127c0", "UNIT": "crio-df0fa4cb425d0dc1fbcc832ef7abd9e921138c6c07bc6c6f92ebf29dc2989201.scope", "SYSLOG_FACILITY": "3", "SYSLOG_IDENTIFIER": "systemd" } } } }


Version-Release number of selected component (if applicable):
ose-logging-rsyslog-v4.2.0-201907141446
ose-cluster-logging-operator-v4.2.0-201907121819


How reproducible:
Always

Steps to Reproduce:
1. Deploy logging using rsyslog as log collector
2. check rsyslog pod logs, `oc exec -c rsyslog $rsyslog-pod -- logs`
3.

Actual results:
There are many "No Action Needed for xxxxxxxxx" in rsyslog pod logs.

Expected results:
These logs should not be shown when checking rsyslog pod logs.

Additional info: