-
Bug
-
Resolution: Unresolved
-
Minor
-
Logging 6.1.z
-
False
-
None
-
False
-
NEW
-
NEW
-
Release Note Not Required
-
-
-
Log Collection - Sprint 268
-
Low
Description of problem:
When running "oc explain obsclf.spec.inputs.receiver", it's missing the syslog receiver:
$ oc explain obsclf.spec.inputs.receiver GROUP: observability.openshift.io KIND: ClusterLogForwarder VERSION: v1FIELD: receiver <Object>DESCRIPTION: Receiver to receive logs from non-cluster sources. FIELDS: http <Object> HTTPReceiver receives encoded logs as a HTTP endpoint. port <integer> -required- Port the Receiver listens on. It must be a value between 1024 and 65535 tls <Object> TLS contains settings for controlling options of TLS connections. The operator will request certificates from the cluster's cert signing service when TLS is not defined. The certificates are injected into a secret named "<clusterlogforwarder.name>-<input.name>" which is mounted into the collector. The collector is configured to use the public and private key provided by the service type <string> -required- Type of Receiver plugin.
Version-Release number of selected component (if applicable):
$ oc get csv |grep cluster-logging cluster-logging.v6.1.3 Red Hat OpenShift Logging 6.1.3 cluster-logging.v6.1.2 Succeeded
How reproducible:
Always
Steps to Reproduce:
- Run the command "oc explain obsclf.spec.inputs.receiver" and verify that not listed the syslog receiver.
Actual results:
Not syslog receiver listed
Expected results:
Syslog receiver listed from the output command and also, it's indicated what's the log_type used for the logs received using the syslog receiver.
It's also missing the log_type used for the logs received when used the http receiver.
