Static Configurations
By default, timeout values for the plugin are pre-configured in the default configuration.
The file to update depends on how the gateway is deployed:
- Host or Docker
- Kubernetes (Helm)
For host or Docker deployments, configure the following settings:
plugin_attr:
proxy-mirror:
timeout:
connect: 60s
read: 60s
send: 60s
Then reload the gateway for changes to take effect.
For Helm deployments, update the chart values that render plugin_attr.proxy-mirror. Keep the rest of your values file unchanged.
For the APISIX Helm chart, set the following values:
apisix:
pluginAttrs:
proxy-mirror:
timeout:
connect: 60s
read: 60s
send: 60s
For the API7 Gateway Helm chart, set the following values:
pluginAttrs:
proxy-mirror:
timeout:
connect: 60s
read: 60s
send: 60s
Then apply the values file with the chart used for this gateway release:
helm upgrade <release-name> <chart-name> -n <namespace> -f values.yaml
Parameters
See plugin common configurations for configuration options available to all plugins.
host
Address of the host to forward the mirrored traffic to. The address should contain the scheme but without the path, such as
http://127.0.0.1:8081.path
Request path to use for mirrored HTTP traffic. If unspecified, the current route URI path is used. For native gRPC and grpc-web traffic, this field is ignored and the gateway preserves the effective gRPC method path after access-phase rewrites.
path_concat_mode
vaild vaule:
replaceorprefixConcatenation mode when
pathis specified. When set toreplace, the configured path replaces the request path. When set toprefix, the request path is appended to the configured path. For native gRPC and grpc-web traffic, this field is ignored and the gateway preserves the effective gRPC method path.sample_ratio
vaild vaule:
between 0.00001 and 1 inclusive
Ratio of the requests that will be mirrored. By default, all traffic are mirrored.