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

This is a minor update (do not send email) Bug 1921263 - Using legacy Log Forwarding is not sending logs to the internal Elasticsearch

    XMLWordPrintable

Details

    • False
    • False
    • NEW
    • NEW
    • Undefined
    • Logging (Core) - Sprint 197, Logging (Core) - Sprint 198

    Description

      +++ This bug was initially created as a clone of Bug #1911477 +++

      [Description of problem]
      In previous version, for example 3.x and until 4.3. When using secure_forward following the documentation [1] the logs were sent to the internal Elasticsearch and to the external instance.

      Now, in 4.5 it's only sending to the external instance and it doesn't send more to the internal Elasticsearch.

      Verifying the documentation, it has not changed [2]. Then, it's expected that it works like it did in the past:

      • Sending logs to the internal Elasticsearch
      • Sending logs to the external instance configured in the secure-forward configmap

      One thing has changed in the configuration generated for fluentd. In 4.3 the fluentd configuration after configuring secure_forward following the documentation is like this:

      Attachments

        Issue Links

          Activity

            People

              jcantril@redhat.com Jeffrey Cantrill
              jcantril@redhat.com Jeffrey Cantrill
              Anping Li Anping Li
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 1 hour
                  1h
                  Remaining:
                  Remaining Estimate - 1 hour
                  1h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified