Container Monitoring
Atatus container monitoring provides real-time visibility into your containerized applications and microservices environments. Capturing and analyzing metrics, traces, and logs ensures the health and performance of your deployments.
Pick what you watch, by name or image.
The agent finds every container on its own. Include or exclude them for metrics, logs or both with one environment variable.
$ sudo docker run -d -e ATATUS_LICENSE_KEY="lic_infra_*****" \ -e ATATUS_CONTAINER_EXCLUDE="name:nginx* name:auth-service" \ ... atatus/atatus-infra-agent:4.3.0
Metrics and logs5
- checkoutshop/checkout:2.14.0
- payment-serviceshop/payment:2.14.0
- cart-serviceshop/cart:2.14.0
- mysqlmysql:8.0
- redisredis:7.2
Metrics only0
- none
Logs only0
- none
Not monitored3
- auth-serviceshop/auth:2.14.0
- nginxnginx:1.27
- nginx-replicanginx:1.27
Run the agent your way.
Next to your containers, or inside your image. Drag it and see what each one sees.
Drag the agent, or press it to switch
Every container on the host
- Containers
- checkout, nginx, postgres, php-fpm, found on their own
- Per container
- CPU, memory, network in and out, I/O, volumes, swap
- Logs
- Logs from every container on the host
- Inside php-fpm
- Not its processes. Put the agent in that image for those
sudo docker run -d -e ATATUS_LICENSE_KEY="YOUR_LICENSE_KEY" \ --user=root \ --volume="/var/lib/docker/containers:/var/lib/docker/containers:ro" \ --volume="/var/run/docker.sock:/var/run/docker.sock:ro" \ --volume="/sys/fs/cgroup:/hostfs/sys/fs/cgroup:ro" \ --volume="/proc:/hostfs/proc:ro" \ --volume="/:/hostfs:ro" \ -it atatus/atatus-infra-agent:4.3.0 -- -c /etc/atatus-infra-agent/ --system.hostfs=/hostfs
One container. Everything about it.
The real container screen. Click a number.
More containers. Same bill.
Priced per host, not per container. Scale out and watch the total stay put.
Container Monitoring, screen by screen.
Real screens from the Atatus app.
Powering better performance for modern teams
"Solid Product even better support." The integration path is incredibly simple/easy and the overall interface is very intuitive. That said, I had a handful of odd use cases that the support team was incredibly responsive in helping me work through.
Questions about container monitoring
Pricing, deployment, data and the agent. If something is missing, a person will answer it on a demo call.
Container Monitoring shows the health and resource use of every container: CPU, memory, network in and out, I/O, swap and volumes, along with each container's state and logs, across Docker hosts and orchestration platforms.
Docker, Docker Compose and Docker Swarm, where the agent runs as a sidecar container, and Amazon ECS, where it runs as a daemon service. You can also bundle the agent inside your own image. Kubernetes pods and containers are covered by Kubernetes Monitoring, installed with a Helm chart.
The agent discovers containers on its own as they start, so short-lived containers are picked up without extra setup. Terminated containers stay in the Containers view with their status, so you can still look into what happened.
Yes. Set ATATUS_CONTAINER_INCLUDE or ATATUS_CONTAINER_EXCLUDE on the agent, using name: for container names and image: for image names, for example name:nginx* or image:mysql. There are separate variables for logs and for metrics.
Yes. Run the agent on every host, as a sidecar, a Swarm global service or an ECS daemon service, and all containers report into one Containers view that you can filter by status, cluster, namespace and node.
Containers are included in Infrastructure Monitoring, which is priced per host: $20 per host per month, or $15 per host per month with yearly billing. The number of containers on a host does not change the price, and there is no per-user pricing.