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

Fluentd collector not setting labels from /var/log/pods paths

XMLWordPrintable

    • False
    • False
    • NEW
    • VERIFIED
    • Hide
      Before this update, a change to the container logs path caused this metric to always be zero with older releases configured with the original path. With this update, the plugin which exposes metrics about collected logs supports reading from either path to resolve the issue.
      Show
      Before this update, a change to the container logs path caused this metric to always be zero with older releases configured with the original path. With this update, the plugin which exposes metrics about collected logs supports reading from either path to resolve the issue.
    • Logging (Core) - Sprint 215

      Since the switch to /var/log/pods, the fluentd collector is not setting namspace, podname and containername labels on log_*_bytes_total metrics.

      It is still expecting the old/var/log/containers path, but we are now reading from /var/log/pods.

      For example:
        

      Name container containername endpoint exported_namespace hostname instance job namespace path plugin_id pod podname prometheus service type Value
      log_collected_bytes_total collector notfound metrics notfound collector-m9bq5 10.128.1.200:24231 collector openshift-logging /var/log/pods/chat_chatter_05682f61-8a44-47af-ae0f-41ad3792e20a/chatter/0.log container-input collector-m9bq5 notfound openshift-monitoring/k8s collector tail 46317128

      The collector needs to recognise /var/log/pods paths.

              rhn-engineering-aconway Alan Conway
              rhn-engineering-aconway Alan Conway
              Qiaoling Tang Qiaoling Tang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: