Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This bug has nothing to do with rsyslog itself - this is about configuration and/or the ansible playbooks used to deploy rsyslog. We don't really have a category for that (we don't even have an official set of ansible playbooks for rsyslog yet). So this is definitely NOTABUG as far as rsyslog is concerned.
Next - there is definitely a difference in the data between json-file and journald. Fields such as
< "CONTAINER_ID": "72367058f4e7",
< "CONTAINER_ID_FULL": "72367058f4e7b9107d252499db3dd13fdcfb0658c929d9738460abe541ad1d16",
< "CONTAINER_NAME": "k8s_centos-logtest_centos-logtest-w7qkp_prj_f7c20fe9-a5eb-11e8-9ba7-fa163e68a0de_0",
< "CONTAINER_TAG": "72367058f4e7",
only exist in journald data, and fields such as
> "log": "2018-08-22 09:41:39,243 - SVTLogger - INFO - centos-logtest-49b67 : 182 : BV8V9ykY7 8isGABl2e v7AamrYk5 vwNQBxOHO 0AnIAArK3 I6ZCaRCvv uhMNX4NS4 r9nPcNLrQ m4AOvVocS LWqrs6BEN 0Q8jL5sz9 XLDyrIqUa y8W39QG9J aloZbI0eO P7XM55qN1 oM6MbRBRr r0NzPghtS ucqVrcIiW ZxXXlGp4o OdnFzEbZY \n",
> "stream": "stderr",
> "time": "2018-08-22T09:41:39.243510296Z",
only exist in json-file data.
Can you provide which ansible playbooks you used to deploy rsyslog?