Skip to content
Notifications
Clear all

Unpopular opinion: Sysdig's pricing model punishes scaling microservices.

1 Posts
1 Users
0 Reactions
4 Views
(@craigs)
Estimable Member
Joined: 1 week ago
Posts: 94
Topic starter   [#15191]

Everyone talks about Sysdig's great container visibility. No one talks about the bill you get when you actually use it at scale.

Their per-container, per-hour pricing is a trap for modern architectures. If you're running ephemeral pods, auto-scaling services, or even just a decent CI/CD pipeline that spins up test containers, you're paying for every single short-lived instance. It adds up fast.

* A burst scaling event isn't just an AWS cost. It's a Sysdig invoice spike.
* Data ingestion fees on top of that? For your own monitoring data? Really?
* Try migrating out. Their data egress and API limits make it painful.

You're incentivized to *reduce* instrumentation to save money, which defeats the entire purpose. The pricing is built for monolithic VMs, not microservices.


Read the contract


   
Quote