AlertmanagerConfig.spec.receivers[].victoropsConfigs[].httpConfig
httpConfig defines the HTTP client's configuration for VictorOps API requests.
| Field / Type | Description |
|---|---|
authorization defines the authorization header configuration for the client. This is mutually exclusive with BasicAuth and is only available starting from Alertmanager v0.22+. | |
basicAuth defines the basic authentication credentials for the client. This is mutually exclusive with Authorization. If both are defined, BasicAuth takes precedence. | |
bearerTokenSecret defines the secret's key that contains the bearer token to be used by the client for authentication. The secret needs to be in the same namespace as the AlertmanagerConfig object and accessible by the Prometheus Operator.
| |
enableHttp2 | enableHttp2 can be used to disable HTTP2. |
followRedirects | followRedirects specifies whether the client should follow HTTP 3xx redirects. When true, the client will automatically follow redirect responses. |
noProxy | noProxy defines a comma-separated string that can contain IPs, CIDR notation, domain names that should be excluded from proxying. IP and domain names can contain port numbers. It requires Prometheus >= v2.43.0, Alertmanager >= v0.25.0 or Thanos >= v0.32.0. |
oauth2 defines the OAuth2 client credentials used to fetch a token for the targets. This enables OAuth2 authentication flow for HTTP requests. | |
proxyConnectHeader optionally specifies headers to send to proxies during CONNECT requests. It requires Prometheus >= v2.43.0, Alertmanager >= v0.25.0 or Thanos >= v0.32.0.
| |
proxyFromEnvironment | proxyFromEnvironment defines whether to use the proxy configuration defined by environment variables (HTTP_PROXY, HTTPS_PROXY, and NO_PROXY). It requires Prometheus >= v2.43.0, Alertmanager >= v0.25.0 or Thanos >= v0.32.0. |
proxyURL | proxyURL defines an optional proxy URL for HTTP requests. If defined, this field takes precedence over `proxyUrl`. |
proxyUrl | proxyUrl defines the HTTP proxy server to use.
|
tlsConfig defines the TLS configuration for the client. This includes settings for certificates, CA validation, and TLS protocol options. |