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
Is your feature request related to a problem? Please describe.
I/O Runtime is working on configurable Log Forwarding, which will allow a namespace to be configured to custom logs destination. Currently supported: Splunk, Azure Log Analytics. This PR allows logging configuration to be managed via aio CLI.
Describe the solution you'd like
The following commands available in aio CLI:
runtime:namespace:log-forwarding:get Get log forwarding destination configuration
runtime:namespace:log-forwarding:set Configure log forwarding destination
runtime:namespace:log-forwarding:set:adobe-io-runtime Set log forwarding destination to Adobe I/O Runtime (Logs will be accessible via aio CLI)
runtime:namespace:log-forwarding:set:azure-log-analytics Set log forwarding destination to Azure Log Analytics
runtime:namespace:log-forwarding:set:splunk-hec Set log forwarding destination to Splunk HEC
The above commands allow to manage Log Forwarding configuration the the namespace. The namespace is determined in the same way as for other commands.
Describe alternatives you've considered
N/A
Additional context
Nothing to add.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I/O Runtime is working on configurable Log Forwarding, which will allow a namespace to be configured to custom logs destination. Currently supported: Splunk, Azure Log Analytics. This PR allows logging configuration to be managed via aio CLI.
Describe the solution you'd like
The following commands available in aio CLI:
The above commands allow to manage Log Forwarding configuration the the namespace. The namespace is determined in the same way as for other commands.
Describe alternatives you've considered
N/A
Additional context
Nothing to add.
The text was updated successfully, but these errors were encountered: