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

Enhancement proposal for logging flow control API

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Log Collection
    • None
    • False
    • False
    • NEW
    • NEW
    • Undefined

      Enhancement Proposal Story

      As a cluster admin I want to be able to set a flow control policy (block, drop, ignore) and rate limits (bytes/sec) on selected containers:

      • a cluster-wide default for all containers (optional)
      • a special rate for containers in named namespaces
      • a special rate for containers matching a label selector

      Rates are per-container and measured in bytes/sec,  the default value 0 means no limits are applied.

      Rates are enforced by dropping log data if it exceeds the rate.

      Note: Enforcing rates using back-pressure will be addressed in a separate story. The API proposal should note how this will be added later.

      Rate limits provide greater predictability and fairness in logging traffic.

      Policy determines the quality of service for logging

      • drop: logs may be dropped if produced faster than consumed. This is sometimes called "at most once" delivery.
      • ignore: logs are ignored and will not be forwarded.

      Acceptance Criteria

      The design should

      The design should be amenable to implementation in stages:
      1. Rates with drop policy, namespaces only
      2. Block policy with/without rates limiting
      *
      Enhancement PR must be reviewed and accepted as usual.

      Notes

      This API

            pmoogi pratibha moogi (Inactive)
            rhn-engineering-aconway Alan Conway
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: