Container monitoring requirements
This Orion Platform topic applies only to the following products:
SAM — VMAN
|Orion Platform module||
If FIPS mode is enabled, you cannot add container services, starting in Orion Platform 2020.2. Remove containers added before FIPS mode was enabled and then delete container services. Otherwise, container polling will continue.
Add each Linux host server as a managed Orion node. To monitor all containers in a single cluster, add each server from the cluster as an Orion node.
An SSH connection to the host server
Need an SSH client? Try the free SolarWinds Solar-PuTTY tool.
Allow all outbound communication from orchestrator machines on the following ports:
Environment-specific ports include:
An Orion Administrator account is required to add or delete container services.
When you add a service, Orion credentials are stored in a plain text file that stays in memory for two hours. SolarWinds recommends creating a dedicated Orion user account to manage container services so critical credentials are not exposed.
Sudo privileges on Linux host servers
For Azure Kubernetes Service (AKS) containers, see:
Each container environment has its own specific requirements, as described in the following topics:
- Docker requirements, deployment script examples, and container removal steps
- Docker Swarm requirements, deployment script examples, and container removal steps
- Kubernetes requirements, installation script examples, and container removal steps
- Apache Mesos requirements, installation script examples, and container removal steps
SolarWinds documentation describes how to display container data in the Orion Web Console. To learn about manipulating containers directly, refer to third-party documentation provided by the vendor. For example, to learn about swarm mode, see Docker docs (© 2020 Docker, Inc., available at docs.docker.com, obtained on October 26, 2020.)