-
Bug
-
Resolution: Not a Bug
-
Major
-
Logging 5.9.0
-
False
-
None
-
False
-
NEW
-
OBSDA-549 - Reliability and performance tuning for log collection
-
NEW
-
Release Note Not Required
-
-
-
Log Collection - Sprint 250, Log Collection - Sprint 251
Description of problem:
When compression, minRetryDuration, maxRetryDuration are enabled, cluster-logging-operator reports Invalid message. ( For example: message: compression is not supported for the output type)
But when delivery, maxWrite=<AtMostOnce|AtLeastOnce> are enabled. vector.toml isn't updated. no warning message.
if syslog Output Plugin supports maxWrite,delivery, the vector.toml should be updated. if syslog Output Plugin doesn't support these values, it is better to show warning message like compression.
How reproducible:
Always
Steps to Reproduce:
- Forward logs to syslogserver using delivery=AtMostOnce and maxWrite=10Mi.
cat <<EOF | oc apply -f -
apiVersion: logging.openshift.io/v1
kind: ClusterLogForwarder
metadata:
name: clf-logs
spec:
inputs:
- application:
namespaces:
- project-qa-1
name: myLogsQA
outputs:
- name: syslogserver
secret:
name: to-syslogserver
type: syslog
url: tls://rsyslogserver.syslog-aosqe.svc:6514
tuning:
delivery: AtMostOnce
maxWrite: 10Mi
pipelines:
- inputRefs:
- myLogsQA
name: pipe1
outputRefs:
- syslogserver
serviceAccountName: clf-syslogserver
EOF
Actual results:
vector.toml isn't updated, no warn message in CLF.status