Uploaded image for project: 'Observability and Data Analysis Program'
  1. Observability and Data Analysis Program
  2. OBSDA-620

Enable Stream (stdout/stderr) information in logs in vector

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%
    • If Release Note Needed, Set a Value
    • 0

    Description

      + Customer wants to enable  Stream (stdout/stderr) information in logs collected by Vector.

      + Customer is trying to setup log forwarder to forward logs to an external Logstash instance and are currently using the 'fluentd forward' protocol to forward the logs to Logstash.

      + By looking at the logs received at logstash cu Noticed that the entries don't contain any information from which log stream (stdout or stderr) the logs have been received.

      + Because this information is dropped in the fluentd configuration (https://github.com/openshift/cluster-logging-operator/blob/791ca54e5598a004d03c82722262f4e44873597c/internal/generator/fluentd/ingress.go#L298).

      + As Customer is planning to migrate from Fluentd to vector as collector , so  want to enable  Stream (stdout/stderr) information in Vector.

      Attachments

        Issue Links

          is blocked by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-5262 Log Collection 6.0 Tech Debt

          • 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.
          • In Progress

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LOG-5292 Add stream info to data model

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • To Do
          is incorporated by

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OBSDA-482 Enable option for debugging Vector for troubleshooting

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • To Do

          Activity

            People

              jamparke@redhat.com Jamie Parker
              rhn-support-niv Niveditha V
              Jeffrey Cantrill
              Jamie Parker Jamie Parker
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: