Sysdig Monitor Review

Docker containers are fully supported but "Events" reporting needs improvement in Mesos


What is most valuable?

Docker containers are completely supported, kind of like "first class citizens".

Also, native support for Mesos, Marathon, AWS, K8s, and others.

How has it helped my organization?

Good monitoring of hosts' metrics (CPU, memory, etc.), great monitoring of containers over Mesos (taking into account resource limits), network traffic, and errors.

What needs improvement?

Not entirely user-friendly at first. It takes a bit of time to get used to the interface. Also, "Events" reporting (errors, crashes, etc.) is not clear at all in a Mesos environment (i.e., it's not clear what specific container is the one that went down). In a Docker Compose environment, it may be way better.

For how long have I used the solution?

About one year.

What was my experience with deployment of the solution?

Nodes and containers monitoring works out-of-the-box, by deploying a container in each node, possibly using Marathon.

In order to monitor masters, you need to manually run another container. Not a problem in itself, but not explained upon installation (had to contact support, and ask specifically about it, for them to "remember" that piece of information).

What do I think about the stability of the solution?

The Sysdig containers do log quite a bit, and over time may suck up some space. Take this into account when deploying (configure log rotation).

What do I think about the scalability of the solution?

None.

How is customer service and technical support?

Great. Always supportive and doing all they could to help out. Had a few calls and got to talk with an engineer about monitoring masters and such.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest