-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
Logging 5.8
-
False
-
-
False
-
-
-
Important
URL
SECTIONS
Logging > Log Collection and Forwarding > Log Forwarding
DESCRIPTION
ISSUE 1
Across the documentation for configuring the Multi Log forwarding implementation, it's not indicated that the logs collected can't be sent to the `default` log storage.
This little detail is important as when configured to send to the `default` Log storage, an error is observed leading to errors when configuring for the first time.
ISSUE 2
At the same time, as it's defined as "Legacy" using "clusterlogging" and "clusterlogforwarder instance", then, it should be expected to transition from the Legacy method to the "Multi Log Forwarder" feature, but, as said before, the "Multi Log Forwarding" implementation can't send the logs to the "default" as it's not supported, then, it's required to define an "output" with all the needed parameters as it could be secrets/tokens, etc to be able to send to the Red Hat managed Log storage: Loki/Elasticsearch.
How to define this "output" and the parameters needed to be able to send to the Red Hat managed "log storage" is not defined.