-
Bug
-
Resolution: Done
-
Normal
-
Logging 5.8.z, Logging 5.9.z, Logging 6.0.z, Logging 6.1.z, Logging 6.2.z, Logging 6.3.z
-
Incidents & Support
-
False
-
-
False
-
NEW
-
VERIFIED
-
-
Bug Fix
-
-
-
Logging - Sprint 274
-
Low
Description of problem:
When verifying how the "url" for Kafka should be, it's not indicated what's the format and possible value.
I'd expect that for any output, I should see the format that the url can take:
<protocol>://<url>:<port>
Where protocol could be http/https/tls/tcp and indicated in specific for Kafka and the rest of the outputs the protocol to be used
Where url, it should be expected to indicate if it's valid to use an ip address or it must be FQDN, in the past, long time ago, some limitations existed on this for some output as it could be syslog
It's frequent to find issues in the configurations as consequence of not knowing the format and not existing a validation for it.
Version-Release number of selected component (if applicable):
Logging 6.y
ClusterLogForwarder API (collector)
How reproducible:
Steps to Reproduce:
- Run the command `oc explain obsclf.spec.outputs.<output>.url and verify that not indicated the format that it can have
- clones
-
LOG-7340 clusterLogForwarder API doesn't indicate that the kafka URL should be tcp or tls
-
- Verified
-
- links to