31 Sysdig Testimonials

“We use Sysdig to identify and alert us to suspicious activity and misconfigurations, and more generally, workloads that may cause security risk.”

“With containers, everything changes every time. Your application never runs on the same node, never runs with the same IP, and never runs with the same port. We had to find a solution to monitor this. That’s why we decided to use Sysdig.”

“We want to be able to create some rules, like you cannot run somethings as root, you cannot mount a host volume in your container, you cannot run this kind of command, and you cannot modify a bin directory. We want to have some set of policies that can be applied dynamically and for all containers to ensure security. Especially if want to expose it in a DMZ.”

"Now that we have established Sysdig in our environment, we are well on our way to establishing our forward-looking platform to deploy our newest generation of application and services, as well as our future applications that we have in the pipeline."

“Being able to move between our environments allows us to run faster. It's one tool for everything. It's not different tools optimized for specific environments. Having this single pane of glass, it doesn't matter where it runs or how it runs. Compared to alternatives, Sysdig improves operations efficiency by 25% and developer efficiency by 20%.”

"We know that as we evolve, Sysdig will support us. Whether it’s collecting Prometheus metrics, or through its kernel-level data inspection, we know we will have the visibility we need."

"From the infrastructure team's perspective it's nice that we can tell our developers to emit metrics with StatsD or Prometheus. You won't have to think about it. They'll just show up in Sysdig."