While Using LogForwarding API, Forwarding logs to `Splunk` and `Syslog` server records `garbage` values.
Environment
- Red Hat OpenShift Container Platform
- 4.5
- 4.6
Issue
- While Using Using
LogForwarding API
, Forwarding logs toSplunk
andSyslog
server recordsgarbage
values.
Resolution
- As of now Forwarding[ RHOCP 4.5/4.6] logs to
Splunk
usingLogforwading API
is not supported.
Root Cause
- Log Forwarding API uses below two output
elasticsearch to forward logs to an external Elasticsearch v5.x cluster, specified by server name or FQDN, and/or the internal OpenShift Container Platform Elasticsearch logstore.
forward to forward logs to an external log aggregation solution. This option uses the Fluentd forward protocols.
- Sending Log to
Splunk
with Forwarding type will have agarbage
value asSplunk
doesn't understand theforward
protocol. - From 4.6 onwards
LogForwarding API
Red Hat only supportskafka
,syslog
,fluend
andelasticsearch
as an external log store.
Diagnostic Steps
- Check Log Forwarding
API YAML
file to check type configured
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments