Collect logs: containers and orchestration (SolarWinds Observability SaaS)
Send logs from containerized applications to SolarWinds Observability SaaS. Containers are often short-lived, so their logs can be lost when a container stops or is replaced. Forwarding container logs to SolarWinds Observability keeps them available for search and analysis in the Logs Explorer.
When a Kubernetes cluster is monitored by SolarWinds Observability SaaS, logs and events from the cluster are collected by default, and you can adjust which logs are collected. For workloads running on AWS Fargate, including Amazon ECS tasks and Amazon EKS pods with a Fargate profile, you must set up log collection separately.
For detailed instructions on how to send logs in specific scenarios, see: