Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-3923

[release-5.4] Kibana filter doesn´t work with kubernetes.namespace_labels.xxxxx

    XMLWordPrintable

Details

    • False
    • None
    • False
    • NEW
    • NEW
    • Bug Fix
    • Hide

      1) Create a namespace and labeled and create different labels for the namespace

      oc label namespace test entorn=pre
oc label namespace test Entorn=PRE
oc label namespace test ENVIRON=PREP

      2) Deploy an application that generates logs

      3)  In Kibana, after creating app* index pattern, use the filter for the previous labels:

       kubernetes.namespace_labels.entorn: pre
 kubernetes.namespace_labels.Entorn: PRE
 kubernetes.namespace_labels.ENVIRON: PREP

      It will not return any results

       

       

       

      Show
      1) Create a namespace and labeled and create different labels for the namespace oc label namespace test entorn=pre oc label namespace test Entorn=PRE oc label namespace test ENVIRON=PREP 2) Deploy an application that generates logs 3)  In Kibana, after creating app* index pattern, use the filter for the previous labels:  kubernetes.namespace_labels.entorn: pre  kubernetes.namespace_labels.Entorn: PRE  kubernetes.namespace_labels.ENVIRON: PREP It will not return any results      
    • Log Collection - Sprint 234, Log Collection - Sprint 235
    • Important

    Description

      Description of problem: Kibana filter is not able to work when search is kubernetes.namespace_labels.xxxxx

      Version-Release number of selected component (if applicable): RHOL 5.5.5

      Actual results: Kibana filter doesn´t work with kubernetes.namespace_labels.xxxxx filters

      Expected results: make a correct filtering

      Additional info:

       

       

       

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. LOG-3439 Kibana filter doesn´t work with kubernetes.namespace_labels.xxxxx

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Activity

            People

              rojacob@redhat.com Robert Jacob
              acandelp Adrian Candel
              Anping Li Anping Li
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: