-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
Logging 5.8
-
False
-
-
False
-
-
-
Important
URL
SECTION
Log collection and forwarding > About forwarding logs to third-party systems > Supported Authorization Keys
Log collection and forwarding > About forwarding logs to third-party systems > Creating a Secret
Log collection and forwarding > Forwarding logs using the Fluentd forward protocol
DESCRIPTION
For fluentd, it's possible to define in the secret for authorization a `shared_key` for authorization as it was present in old versions of the documentation where it's said:
- fluentdForward. An external log aggregation solution that supports Fluentd. This option uses the Fluentd forward protocols. The fluentForward output can use a TCP or TLS connection and supports shared-key authentication by providing a shared_key field in a secret. Shared-key authentication can be used with or without TLS.
As the output section is not more present in the documentation Forwarding logs to external third-party logging systems, and this option was not explained in the example in the documentation section specific for Forwarding logs using the Fluentd forward protocol, then, it's not more present in the docs.
CURRENT SITUATION
Not reflected in the documentation in the that possible to configure the `shared_key` when log forwarding to fluentd in the different sections listed in the SECTIONS above. They are:
1.Log collection and forwarding > Configuring log forwarding > Supported Authorization Keys
2.Log collection and forwarding > Configuring log forwarding > Supported Authorization Keys > Creating a secret
3.Log collection and forwarding > Forwarding logs using the Fluentd forward protocol
- is related to
-
OBSDOCS-831 Requirements for when log forwarding when using SSL/TLS
- New