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. If containers were added before FIPS mode was enabled, remove them from nodes and then delete container services. Otherwise, container polling will continue.
Add Linux host servers as managed Orion nodes. To monitor all containers in a single cluster, add each server from the cluster as an Orion node.
Sudo privileges on the master server
An SSH connection to the master 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:
|Orion account credentials||SolarWinds recommends creating a specific Orion user account to manage container services. When you add a service, credentials are stored in a plain text file that stays in memory for two hours. By using a dedicated account, no actual user credentials will be exposed.|
Each container environment has its own specific requirements, as described in:
- 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