|
|
|
@ -18,7 +18,7 @@ option (udpa.annotations.file_status).package_version_status = ACTIVE; |
|
|
|
|
// [#protodoc-title: Common fault injection types] |
|
|
|
|
|
|
|
|
|
// Delay specification is used to inject latency into the |
|
|
|
|
// HTTP/gRPC/Mongo/Redis operation or delay proxying of TCP connections. |
|
|
|
|
// HTTP/Mongo operation. |
|
|
|
|
// [#next-free-field: 6] |
|
|
|
|
message FaultDelay { |
|
|
|
|
option (udpa.annotations.versioning).previous_message_type = |
|
|
|
@ -46,10 +46,9 @@ message FaultDelay { |
|
|
|
|
|
|
|
|
|
// 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. |
|
|
|
|
// the JSON/YAML Duration mapping. For HTTP/Mongo, the specified |
|
|
|
|
// delay will be injected before a new request/operation. |
|
|
|
|
// This is required if type is FIXED. |
|
|
|
|
google.protobuf.Duration fixed_delay = 3 [(validate.rules).duration = {gt {}}]; |
|
|
|
|
|
|
|
|
|
// Fault delays are controlled via an HTTP header (if applicable). |
|
|
|
|