-
Bug
-
Resolution: Done
-
Major
-
Logging 5.4.4
-
False
-
None
-
False
-
Logging
-
NEW
-
VERIFIED
-
Before this change, Elasticsearch index templates defined the fields for labels with the wrong types. This change updates those templates to match the expected types forwarded by the log collector
-
Medium
-
-
Log Collection - Sprint 223
-RHOL VERSION 5.4.4
ElasticsearchError error="400 - Rejected by Elasticsearch" appeared in collector pods for application logs when an application namespace has some labels, the main point is that it is not happening with all labels, it seems to be specific with some labels.
Some examples are in "Steps to Reproduce"
2022-08-19 08:35:41 +0000 [warn]: dump an error event: error_class=Fluent::Plugin::ElasticsearchErrorHandler::ElasticsearchError error="400 - Rejected by Elasticsearch" location=nil tag="kubernetes.var.log.pods.test_rails-postgresql-example-1-build_7418d148-3eda-4078-b074-c26d53fa01c3.sti-build.0.log" time=2022-08-19 08:35:39.733921100 +0000 record={"@timestamp"=>"2022-08-19T08:35:39.733921100+00:00", "message"=>"Fetching sassc 2.4.0", "docker"=> {"container_id"=>"f43bb3760f88d040b286f6d6bbdafab2dd05df66d64a6966aef7b0ff8870f3a8"} , "kubernetes"=>{"container_name"=>"sti-build", "namespace_name"=>"test", "pod_name"=>"rails-postgresql-example-1-build", "container_image"=>"quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:aecd1cb82ff1d78d0c8363a5bbdfaf7a19652e9f4e31c48e63d18a933624655f", "container_image_id"=>"quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:aecd1cb82ff1d78d0c8363a5bbdfaf7a19652e9f4e31c48e63d18a933624655f", "pod_id"=>"7418d148-3eda-4078-b074-c26d53fa01c3", "pod_ip"=>"10.131.0.100", "host"=>"worker-0.adricluster.lab.pnq2.cee.redhat.com", "master_url"=>"https://kubernetes.default.svc", "namespace_id"=>"7a116e5e-a434-49fa-86f4-eb4af2d4c860", "namespace_labels"=> {"app"=>"config-server", "app.kubernetes.io/instance"=>"config-server-uat", "kubernetes.io/metadata.name"=>"test"} , "flat_labels"=>["openshift.io/build.name=rails-postgresql-example-1"]}, "level"=>"unknown", "hostname"=>"worker-0.adricluster.lab.pnq2.cee.redhat.com", "pipeline_metadata"=>{"collector"=>{"ipaddr4"=>"10.74.176.82", "inputname"=>"fluent-plugin-systemd", "name"=>"fluentd", "received_at"=>"2022-08-19T08:35:39.735747+00:00", "version"=>"1.14.6 1.6.0"}}, "openshift"=> {"sequence"=>23904} , "viaq_msg_id"=>"ODAwY2NhY2YtOTU5ZC00NmM2LWJjZjctNzFlMzg3MTlhNzAx", "log_type"=>"application", "viaq_index_name"=>"app-write"}
Please take into consideration that also a customer started having this problem after the update from RHOL 5.4.3 to RHOL 5.4.4
- is related to
-
LOG-2963 OpenSearch can no longer be used as an Elasticsearch output for forwarding
- Closed
- links to
- mentioned on
(3 mentioned on)