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

No input.type httpserver in log_forwarder_input_info

    XMLWordPrintable

Details

    • False
    • None
    • False
    • NEW
    • NEW
    • Before this fix, log_forwarder_input_info only included application, infrastructure, and audit input metric points. With this fix, http is added as a metric point.
    • Bug Fix
    • Log Collection - Sprint 249

    Description

      Description of problem:

      When use the following CLF.spec. the log_forwarder_input_info doesn't include input.type.httpreceiver.
      In logging 5.9, the same issue is present for input.type.syslogreceiver

       

      spec:
        inputs:
        - name: input-http
          receiver:
            http:
              format: kubeAPIAudit
              port: 8080
        pipelines:
        - inputRefs:
          - input-http
          - application
          name: to-default
          outputRefs:
          - default  

       

      
        {
          "metric": {
            "__name__": "log_forwarder_input_info",
            "application": "1",
            "audit": "0",
            "endpoint": "http-metrics",
            "infrastructure": "0",
            "instance": "10.131.0.12:8686",
            "job": "cluster-logging-operator-metrics",
            "namespace": "openshift-logging",
            "pod": "cluster-logging-operator-6d79756c-8bq96",
            "service": "cluster-logging-operator-metrics"
          },
          "value": [
            1706756855.413,
            "1"
          ]
        },

       

      Attachments

        Activity

          People

            rh-ee-calee Calvin Lee
            rhn-support-anli Anping Li
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: