Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

Service Task Count

Check

Check

Verify service task count
Install now

Service Task Count

Verify service task count
Check

Check

Targets:

ECS Service

Install now

Service Task Count

Check

Check

Verify service task count
Install now

Service Task Count

Verify service task count
Check

Check

Targets:

ECS Service

Install now
Go back to list

Introduction

Checks if the count of running tasks in a service is matching your expectation.

It compares the count of running tasks in a service with the desired count. It, therefore, assumes that the specified mode (see below) becomes true within the specified timeout.

Use Cases

  • Check if the running count is equal to the desired count
  • Check if the running count is below the desired count
  • Check if there is at least one running task
  • Check if the running count increases
  • Check if the running count decreased

Parameters

ParameterDescriptionDefault
TimeoutHow long should the check wait for the configured condition to become true?10s
Service task countHow should the running service task count change? (See values below)

Service Task Count

You can use the service task count check in one of the following modes:

  • running count = desired count: Can be used to assure that the amount of desired tasks is equal to the actual running tasks in a service. Helpful to check e.g. after an attack whether tasks are recovering.
  • running count > 0: To assure that at least one task is available in a service to handle load.
  • running count < desired count: To make sure that tasks in a service matching the check's query are below the specified running count. This can be helpful in case you want to verify that attacks lead to restarts of tasks.
  • running count increases: Check if the running task count in a service increases compared to the actual number of running tasks when you started the action.
  • running count decreases: Check if the running task count decreases compared to the actual number of running tasks when you started the action.
Statistics
-Stars
Tags
AWS
Cloud
Homepage
hub.steadybit.com/extension/com.steadybit.extension_aws
License
MIT
MaintainerSteadybit
Install now

Useful Templates

See all
AWS ECS Service Is Scaled up Within Reasonable Time

Verify that your ECS service is scaled up on increased CPU usage.

Motivation

Important ECS services should be scaled up within a reasonable time for an elastic and resilient cloud infrastructure. Undetected high CPU spikes and long startup times are undesirable in these infrastructures.

Structure

First, we ensure that all ECS service's tasks are ready to serve traffic. Afterward, we inject high CPU usage into the ECS task and expect that within a reasonable amount of time, ECS increases the number of ECS tasks and they become ready to handle incoming traffic.

Scalability
CPU
AWS ECS
AWS

ECS Service

ECS Tasks

Scaling up of ECS Service Within Given Time

Ensure that you can scale up your ECS service in a reasonable time.

Motivation

For an elastic and resilient cloud infrastructure, ensure you can scale up your ECS services within a reasonable time. Long startup times are undesirable but sometimes unnoticed and unexpected.

Structure

Validate that all ECS tasks of an ECS service are running. Once we scale the ECS service up, the newly scheduled task should be ready within a reasonable time.

Scalability
Elasticity
AWS ECS
AWS

ECS Service

More ECS Service Actions

See all
Start Using Steadybit Today

Get started with Steadybit, and you’ll get access to all of our features to discover the full power of Steadybit. Available for SaaS and on-prem!

Are you unsure where to begin?

No worries, our reliability experts are here to help: book a demo with them!

Steadybit logoResilience Hub
Try Steadybit
© 2024 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon