Skip to content

docs: clarify that latency toxics are one-way #756

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Hashim1999164 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: clarify that latency toxics are one-way #756

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -382,7 +382,12 @@ For documentation on implementing custom toxics, see [CREATING_TOXICS.md](./CREA

#### latency

Add a delay to all data going through the proxy. The delay is equal to `latency` +/- `jitter`.
Add a delay to data on a single proxy stream. The delay is equal to `latency` +/- `jitter`.

Toxics are directional: by default a latency toxic is attached to the `downstream`
stream (`server -> client`). It does not delay the opposite direction unless you
also add a latency toxic with `stream=upstream`. For a symmetric round-trip delay,
add latency on both streams.

Attributes:

Expand Down
Loading