Test how your application handles a PostgreSQL outage. Run Gremlin network experiments and reliability tests to validate timeouts and failover.
Teams choose Azure Database for PostgreSQL partly for familiarity. The engine behaves the way your engineers already understand, which is a real advantage and the source of a quiet assumption: that operational knowledge from self-hosted Postgres transfers directly to the managed service.
Some of it does not. Failover timing, connection limits, and maintenance windows are Azure's decisions now. Connection pooling in particular tends to be configured from habit rather than from the managed service's actual limits, and the mismatch only appears when connections start getting refused during a traffic peak.
Gremlin replaces that assumption with measurements. Blackhole experiments make the database endpoint unreachable so you can time a failover from the application's side and confirm your pool reconnects without intervention. Latency experiments slow the connection to see how far requests back up before your timeouts fire.
Knowing Postgres is not the same as knowing this Postgres. Measuring the difference costs an afternoon and saves you the incident where you learn it the hard way.
Dependencies: Failure Test
Simulate a failed dependency by dropping all network traffic to the dependency.
Dependencies: Latency Test
Recreate poor network conditions by delaying all network traffic to a dependency by 100ms.
* Testing a dependency doesn't require installing anything on it. Gremlin runs the experiment from the service that calls it, so compatibility depends on that host rather than on the dependency itself. Check our compatibility documentation for supported operating systems and platforms, or get in touch if you don't see yours.
Intelligent Health Checks - Azure
Automatically monitor your Azure services during testing in one-click with Intelligent Health Checks.
Avoid downtime. Use Gremlin to turn failure into resilience.
Gremlin empowers you to proactively root out failure before it causes downtime. See how you can harness chaos to build resilient systems by requesting a demo of Gremlin.
