Log filter doesn't work if the labelKeys referenced doesn't exist in RHOCP 4

Solution Verified - Updated -

Issue

  • The "OpenShift Console > Observe > Logs" continues showing in the "Filters" the filter matching a default labelKey that doesn't exist anymore, returning no data if it's used.
  • It was configured different labelKeys on the collector for when log forwarding to Loki, the result is that the "OpenShift Console > Observe > Logs" continues showing the filter matching a labelKey that doesn't exist, then, if it's used, the result is not data and the new labelKeys are not listed as an option to filter.
  • "No datapoints found" in the "OpenShift Console > Observe > Logs" when querying the application logs after configuring the clusterLogForwarder for pruning all the default "kubernetes" fields.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat OpenShift Logging (RHOL)
    • 5
    • 6
  • Red Hat OpenShift Console
  • Loki
  • Vector

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