Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

Delay Traffic

Attack

Attack

Inject latency into egress network traffic.
Targets:
Containers
Install now

Delay Traffic

Inject latency into egress network traffic.
Attack

Attack

Targets:
Containers
Install now

Delay Traffic

Attack

Attack

Inject latency into egress network traffic.
Targets:
Containers
Install now

Delay Traffic

Inject latency into egress network traffic.
Attack

Attack

Targets:
Containers
Install now
Go back to list
Wireshark showing the effects of the attack.Wireshark showing the effects of the attack.

Introduction

Inject latency into all matching traffic.

Details

The network delay operates at the ip level and affects single packets. Thus, you may encounter http requests that are delayed by a multiple of the specified delay.

In this example the traffic is delayed by 500ms. If you tap the wire (using tcpdump) and feed it into Wireshark it looks like shown in the image above.

  1. The first incoming packet initiates the tcp connection and is accepted by the second packet, which is delayed exactly be the 500ms.

  2. With the fourth packet we receive a http request in the payload. Which is acknowledged and answered with a http response in packet four to seven, which are also delayed by 500ms and thus the total latency for the http request sums up to 1 second.

Note: If you are going to attack containers using network attacks, all containers in the target's linux network namespace (e.g. all containers belonging to the same Kubernetes Pod or Replica Set) will be affected. In case you want to target the traffic of a single container in the namespace you can for example use the port parameter to limit the blast radius.

Parameters

ParameterDescriptionDefault
Network DelayHow much should the traffic be delayed?500ms
JitterRandom +-30% jitter to network delaytrue
Fail on Host NetworkEmit failure when the targeted container is using the host networktrue
DurationHow long should the traffic be affected?30s
HostnameRestrict to which hosts the traffic is reduced
IP AddressRestrict to which IP address the traffic is reduced
Network InterfaceTarget Network Interface which should be attacked. All if none specified.
PortsRestrict to which ports the traffic is reduced
Statistics
-Stars
Tags
Container
Kubernetes
Network
Homepage
hub.steadybit.com/extension/com.steadybit.extension_container
License
MIT
MaintainerSteadybit

Useful Recipes

See all
Verify system unavailability status during Redis latency

Verify that an increased latency in a Redis cache is handled by your application properly by having increased processing time but still being able to maintain the throughput.

Tags:
Redis
Recoverability
Targets:

Containers

Datadog monitors

Kubernetes deployments

More Container Actions

See all
Block DNS

Blocks access to DNS servers

Attack

Attack

Containers


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
HubActionsTargetsExtensionsRecipes
© 2024 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon