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

[spike]Study of new collectors for new metrics and Rate Control provisions

    XMLWordPrintable

Details

    • Task
    • Resolution: Obsolete
    • Undefined
    • None
    • None
    • None
    • False
    • False
    • NEW
    • NEW
    • Undefined

    Description

      Goals

      Identify features of fluentbit and vector tjhat can be used to implement flow control as described in LOG-884 and linked epics. These include

      • rate limiting at inbound and outbound stages
      • drop and backpressure policies to enforce rate limits
      • metrics to measure inbound/outbound log volume, dropped data etc.

      Acceptance Criteria

      • List of flow control features of vector and fluentd with pointers to relevant documentation.
      • Examples of fluetnd/vector configuration to implement different flow control and rate limiting policies, decribed in LOG-884 and linked epics and design documents.

      Attachments

        Issue Links

          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-1073 Implement flow control by backpressure

          • Undefined - Priority not specified.
          • New

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-884 Flow control mechanisms for more predictable log collection

          • 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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-1074 Combined rate limits for flow control

          • Undefined - Priority not specified.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. LOG-1043 Enhancement proposal for logging flow control API

          • Undefined - Priority not specified.
          • Closed

          Activity

            People

              Unassigned Unassigned
              pmoogi pratibha moogi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: