Common fault injection types

Delay specification is used to inject latency into the HTTP/gRPC/Mongo/Redis operation or delay proxying of TCP connections.

type

(config.filter.fault.v2.FaultDelay.FaultDelayType) Unused and deprecated. Will be removed in the next release.

fixed_delay

() Add a fixed delay before forwarding the operation upstream. See https://developers.google.com/protocol-buffers/docs/proto3#json for the JSON/YAML Duration mapping. For HTTP/Mongo/Redis, the specified delay will be injected before a new request/operation. For TCP connections, the proxying of the connection upstream will be delayed for the specified period. This is required if type is FIXED.

Precisely one of , header_delay must be set.

header_delay

() Fault delays are controlled via an HTTP header (if applicable).

Precisely one of fixed_delay, must be set.

percentage

config.filter.fault.v2.FaultDelay.HeaderDelay

Fault delays are controlled via an HTTP header (if applicable). See the HTTP fault filter documentation for more information.

FIXED

(DEFAULT) ⁣Unused and deprecated.

config.filter.fault.v2.FaultRateLimit

Describes a rate limit to be applied.

fixed_limit

(config.filter.fault.v2.FaultRateLimit.FixedLimit) A fixed rate limit.

Precisely one of , header_limit must be set.

() Rate limits are controlled via an HTTP header (if applicable).

Precisely one of fixed_limit, must be set.

percentage

(type.FractionalPercent) The percentage of operations/connections/requests on which the rate limit will be injected.

Describes a fixed/constant rate limit.

limit_kbps

(uint64) The limit supplied in KiB/s.

config.filter.fault.v2.FaultRateLimit.HeaderLimit

[config.filter.fault.v2.FaultRateLimit.HeaderLimit proto]

Rate limits are controlled via an HTTP header (if applicable). See the documentation for more information.