Error reconciling clusterlogging by an invalid JSON definition in RHOCP 4

Solution Verified - Updated -

Issue

  • Changes applied to the clusterLogging CR are not applied when observing in the clusterLogging operator pod the error indicating that missed the field structuredTypeKey or structuredTypeName

    {"_ts":"2023-08-14T14:27:27.865948363Z","_level":"0","_component":"cluster-logging-operator","_message":"Error reconciling clusterlogging instance","_error":{"msg":"structuredTypeKey or structuredTypeName must be defined for Elasticsearch output named \"default\" when JSON parsing is enabled on pipeline \"container-logs\" that references it"}}
    
  • After upgrading to RHOL 5.8 log collectors don't exist anymore, the collector daemonset is missed and oc events shows an error similar to:

    25h         Warning   Invalid                clusterlogforwarder/instance                structuredTypeKey or structuredTypeName must be defined for Elasticsearch output named "default" when JSON parsing is enabled on pipeline "<pipeline name>" that references it
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat OpenShift Logging (RHOL)
    • 5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content