You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When forwarding logs to Splunk, aio rt logs command does not works and sends this message:
Namespace is configured with custom log forwarding destination: 'splunk_hec'. Please use corresponding logging platform to view logs.
Actual Behavior
If you run aio rt logs --tail in 1 tab and configure Splunk forwarding in a different tab, then you will continue to see logs both in Splunk and terminal until you decide to close your terminal.
The text was updated successfully, but these errors were encountered:
It is not intended behavior that aio rt logs returns logs in case of custom log forwarding because aio rt can't fetch logs from a custom destination. Due to recent change in the logging configuration, logs are duplicated and sent to Adobe-managed system as well in case of custom log forwarding. So aio rt logs can actually fetch logs while the command is still running. But if it will be restarted after custom log forwarding is configured, it will fail due to client-side validation. It is not guaranteed that logs will be duplicated to an Adobe system in case custom log forwarding is configured, so aio rt logs returning logs while still running is just a side-effect.
Expected Behavior
When forwarding logs to Splunk, aio rt logs command does not works and sends this message:
Actual Behavior
If you run
aio rt logs --tail
in 1 tab and configure Splunk forwarding in a different tab, then you will continue to see logs both in Splunk and terminal until you decide to close your terminal.The text was updated successfully, but these errors were encountered: