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

Upstream documentation indicates that AtLeastOnce is the default

XMLWordPrintable

    • Incidents & Support
    • False
    • Hide

      None

      Show
      None
    • False
    • NEW
    • VERIFIED
    • Hide
      Before this update, the documentation regarding Tuning Delivery mode default settings may have lacked clarity or sufficient detail. This could have led to users experiencing difficulty in understanding or optimally configuring these settings for their logging pipelines. With this update, the documentation has been revised to provide more comprehensive and clearer guidance on Tuning Delivery mode default settings, resolving potential ambiguities.
      Show
      Before this update, the documentation regarding Tuning Delivery mode default settings may have lacked clarity or sufficient detail. This could have led to users experiencing difficulty in understanding or optimally configuring these settings for their logging pipelines. With this update, the documentation has been revised to provide more comprehensive and clearer guidance on Tuning Delivery mode default settings, resolving potential ambiguities.
    • Bug Fix
    • Log Collection - Sprint 271, Log Collection - Sprint 272
    • Low

      Description

      In the URL https://github.com/openshift/cluster-logging-operator/blob/release-6.2/docs/features/collection.adoc#tuning is read:

      AtLeastOnce (default): The forwarder will block in an attempt to deliver all messages. When the tuning spec is added to an output, this additionally configures an internal, durable buffer so the collector can attempt to forward any logs read before it restarted

      This is not correct, when it's not set any Delivery option, the "buffer.type" is "memory".

      Let's confirm it:

      $ oc get csv |grep -i logging
cluster-logging.v6.2.2           Red Hat OpenShift Logging          6.2.2     cluster-logging.v6.2.1           Succeeded

      Let's see the clusterLogForwarder CR configured without any tuning option:

      $ oc get obsclf collector -o yaml 
apiVersion: observability.openshift.io/v1
kind: ClusterLogForwarder
metadata:
  creationTimestamp: "2025-05-08T07:30:10Z"
  generation: 1
  name: collector
  namespace: openshift-logging
  resourceVersion: "1033753"
  uid: f24e722d-a4f1-4ce0-9a19-3df24c7e3e24
spec:
  managementState: Managed
  outputs:
  - lokiStack:
      authentication:
        token:
          from: serviceAccount
      target:
        name: logging-loki
        namespace: openshift-logging
    name: default-lokistack
    tls:
      ca:
        configMapName: openshift-service-ca.crt
        key: service-ca.crt
    type: lokiStack
  pipelines:
  - inputRefs:
    - application
    - infrastructure
    - audit
    name: default-logstore
    outputRefs:
    - default-lokistack
  serviceAccount:
    name: collector

      Let's confirm that the Vector configuration generated by the Red Hat Logging Operator has not set "buffer.type: disk", then, it's used the default that it's "buffer.type: memory" [0]

      [0] https://vector.dev/docs/reference/configuration/sinks/loki/#buffer.type

              vparfono Vitalii Parfonov
              rhn-support-ocasalsa Oscar Casal Sanchez
              Kabir Bharti Kabir Bharti
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: