Test Azure Container Apps Jobs reliability with Gremlin Failure Flags. Inject latency and errors to validate job timeout and failure reporting.
Jobs in Azure Container Apps run and exit, which means the success signal is simply that the process ended. A job that hangs never produces that signal, and it never produces a failure either. It occupies an ambiguous state that monitoring rarely covers well.
Scheduled work makes it worse. If a job runs nightly and hangs, the next night's run may start while the previous one is still stuck, or may not start at all. Either outcome gets discovered days later by whoever depends on the output, and by then several runs are affected.
Add Failure Flags to your job container and you can establish an upper bound on runtime. Inject latency into an outbound call and confirm the job gives up rather than waiting indefinitely. Inject an error and check whether exceeding that bound produces an alert anyone sees.
For unattended scheduled work, a job that fails quickly and loudly is worth considerably more than one that usually succeeds.
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.
Unreliable Networks - Dependencies
Simulate unreliable network conditions when communicating with dependencies by adding latency to API calls. Test whether your users are affected when dependency response times degrade.
* Failure Flags works wherever you can add the SDK to your application and run the Gremlin sidecar. Not every language and platform combination has been individually tested, and not all are officially supported. Check our compatibility documentation for what's verified, or get in touch if you don't see your runtime.
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.
.svg)