Monitor containers in the Orion Platform
This Orion Platform topic applies only to the following products:
SAM — VMAN
Similar to VMs, containers isolate applications and their dependencies into self-contained units that can run anywhere without interfering with each other. Unlike VMs that each have their own virtual OS and hardware, containers share the host system kernel with other containers to save space, increase efficiency, and improve developer productivity.
The ability to monitor containers on Linux nodes in the Orion Platform enables you to:
- Display details about your container infrastructure, including hosts, host clusters, environment dependencies, and deployments.
- Track container, host, and other infrastructure metrics to help ensure and plan capacity.
- View in-depth data about individual containers on the Container Details page.
- Analyze container activity in the AppStack Environment and PerfStack dashboards.
- Organize containers on Orion Maps.
The Orion Platform supports the following container environments:
- Docker Swarm 17.12 and later
- Kubernetes (K8s), including Microsoft Azure Kubernetes (AKS)
- Apache Mesos
To get started monitoring containers quickly:
- Review container monitoring requirements.
- Add a container service to generate a script for Linux nodes that host containers.
- Run provided scripts on Linux nodes.
Wait a few minutes for container status and performance metrics to appear in various areas of the Orion Web Console, such as the Containers widget on the Node Details page and the Container Details page, as shown here. See Display container data in the Orion Web Console for details.
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.
Note the following details about container monitoring:
- Polling occurs every five minutes, by default, but you can adjust intervals on the Global tab of the Advanced Configuration page (http://localhost/Orion/Admin/AdvancedConfiguration/Global.aspx).
Interval changes apply to future container services added to the Orion Platform only.
- Only containers monitored on host servers that are managed Orion nodes count against licenses. To monitor all containers in a single cluster, add each server from the cluster as an Orion node.
- Some containers are created for long-term use, but many are transient and only needed for a specific, temporary purpose. By default, the Orion Platform deletes container data from child nodes after seven days with no activity, but Orion Aggregator containers remain on master nodes until you delete the related container service.
- Although no out-of-the-box alerts and reports currently exist for container monitoring, you can use related conditions and events to create your own. For example, set up an alert to trigger email when a container restarts more than five times.
- Container entities are available in PerfStack. For example, if you track TCP Port Monitor and Average Response Time metrics for an application on a server that hosts a containerized environment and you also have CPU utilization for different containers running throughout the history of the application's deployment, you can trace back to see what happened for containers running at different points in history.
- In Orion Map subviews of Node Details pages, containers appear as authorized children of nodes.
When you upgrade SAM or VMAN, rebuild containers and add container services again to refresh YAML files and agents plugins. Click here for details.
Want to learn more about monitoring containers? Check out these videos: