#

""

External URL, that alertmanager will expose to receivers

""

External URL Prefix, Prefix for the internal routes of web endpoints

global:
    resolve_timeout: 5m
receivers:
    - name: devnull
route:
    group_by:
        - alertname
    group_interval: 10s
    group_wait: 30s
    receiver: devnull
    repeat_interval: 24h

Alertmanager configuration

""

Use existing configmap if specified otherwise .config values will be used

{}

Empty dir configuration if persistence is disabled for Alertmanager

false

Create alertmanager resources

[]

Specify alternative source for env variables

{}

Extra command line arguments for container of component

[]

Extra containers to run in a pod with alertmanager

[]

Additional hostPath mounts

[]

Extra Volume Mounts for the container

[]

Extra Volumes for the pod

""

Override Alertmanager resources fullname

registry: ""
repository: prom/alertmanager
tag: v0.27.0

Alertmanager image configuration

[]

Image pull secrets

{}

Ingress annotations

false

Enable deployment of ingress for alertmanager component

{}

Ingress extra labels

- name: alertmanager.local
  path:
    - /
  port: web

Array of host objects

""

Ingress controller class name

Prefix

Ingress path type

[]

Array of TLS objects

[]

Additional initContainers to initialize the pod

0.0.0.0:9093

Alertmanager listen address

{}

Pod’s node selector. Details are here

- ReadWriteOnce

Array of access modes. Must match those of existing PV or dynamic provisioner. Details are here

{}

Persistant volume annotations

false

Create/use Persistent Volume Claim for alertmanager component. Empty dir if false

""

Existing Claim name. If defined, PVC must be created manually before volume will be bound

/data

Mount path. Alertmanager data Persistent Volume mount root path.

50Mi

Size of the volume. Better to set the same as resource limit memory property.

""

StorageClass to use for persistent volume. Requires alertmanager.persistentVolume.enabled: true. If defined, PVC created automatically

""

Mount subpath

{}

Alertmanager Pod annotations

{}

Alertmanager Pod labels

enabled: false

Pod’s security context. Details are here

""

Name of Priority Class

httpGet:
    path: '{{ ternary "" .baseURLPrefix (empty .baseURLPrefix) }}/-/healthy'
    port: web

Liveness probe

httpGet:
    path: '{{ ternary "" .baseURLPrefix (empty .baseURLPrefix) }}/-/ready'
    port: web

Readiness probe

httpGet:
    path: '{{ ternary "" .baseURLPrefix (empty .baseURLPrefix) }}/-/ready'
    port: web

Startup probe

{}

Resource object. Details are here

120h

Alertmanager retention

enabled: false

Security context to be added to server pods

{}

Service annotations

""

Service ClusterIP

[]

Service external IPs. Check here for details

""

Service external traffic policy. Check here for details

""

Health check node port for a service. Check here for details

[]

List of service IP families. Check here for details.

""

Service IP family policy. Check here for details.

{}

Service labels

""

Service load balancer IP

[]

Load balancer source range

9093

Service port

ClusterIP

Service type

{}

Alertmanager extra templates

[]

Node tolerations for server scheduling to nodes with taints. Details are here

{}

Alertmanager web configuration

[]

Add extra specs dynamically to this chart

cluster.local.

K8s cluster domain suffix, uses for building storage pods’ FQDN. Details are here

openshift:
    adaptSecurityContext: auto

Openshift security context compatibility configuration

""

Image registry, that can be shared across multiple helm charts

[]

Image pull secrets, that can be shared across multiple helm charts

key: ""
secret:
    key: ""
    name: ""

Enterprise license key configuration for VictoriaMetrics enterprise. Required only for VictoriaMetrics enterprise. Check docs here, for more information, visit site. Request a trial license here Supported starting from VictoriaMetrics v1.94.0

""

License key

key: ""
name: ""

Use existing secret with license key

""

Key in secret with license key

""

Existing secret name

""

Override chart name

{}

Pod affinity

{}

Annotations to be added to the deployment

alerts:
    groups: []

VMAlert configuration

""

VMAlert alert rules configuration. Use existing configmap if specified

basicAuth:
    password: ""
    username: ""
bearer:
    token: ""
    tokenFile: ""
url: ""

VMAlert reads metrics from source, next section represents its configuration. It can be any service which supports MetricsQL or PromQL.

password: ""
username: ""

Basic auth for datasource

""

Token with Bearer token. You can use one of token or tokenFile. You don’t need to add “Bearer” prefix string

""

Token Auth file with Bearer token. You can use one of token or tokenFile

[]

Additional environment variables (ex.: secret tokens, flags). Check here for details.

[]

Specify alternative source for env variables

envflag.enable: true
envflag.prefix: VM_
httpListenAddr: :8880
loggerFormat: json
rule:
    - /config/alert-rules.yaml

Extra command line arguments for container of component

[]

Additional containers to run in the same pod

[]

Additional hostPath mounts

[]

Extra Volume Mounts for the container. Expects a lice of volume mounts

[]

Extra Volumes for the pod

""

Override vmalert resources fullname

pullPolicy: IfNotPresent
registry: ""
repository: victoriametrics/vmalert
tag: ""
variant: ""

VMAlert image configuration

[]

Image pull secrets

{}

Ingress annotations

false

Enable deployment of ingress for vmalert component

{}

Ingress extra labels

- name: vmalert.local
  path:
    - /
  port: http

Array of host objects

""

Ingress controller class name

Prefix

Ingress path type

[]

Array of TLS objects

[]

Additional initContainers to initialize the pod

{}

Labels to be added to the deployment

0

Specifies the minimum number of seconds for which a newly created Pod should be ready without any of its containers crashing/terminating 0 is the standard k8s default

""

Override default app label name

{}

Pod’s node selector. Details are here

alertmanager:
    basicAuth:
        password: ""
        username: ""
    bearer:
        token: ""
        tokenFile: ""
    url: ""

Notifier to use for alerts. Multiple notifiers can be enabled by using notifiers section

password: ""
username: ""

Basic auth for alertmanager

""

Token with Bearer token. You can use one of token or tokenFile. You don’t need to add “Bearer” prefix string

""

Token Auth file with Bearer token. You can use one of token or tokenFile

[]

Additional notifiers to use for alerts

{}

Annotations to be added to pod

enabled: false
labels: {}

See kubectl explain poddisruptionbudget.spec for more. Or check docs

{}

Pod’s additional labels

enabled: true

Pod’s security context. Details are here

""

Name of Priority Class

failureThreshold: 3
initialDelaySeconds: 5
periodSeconds: 15
tcpSocket: {}
timeoutSeconds: 5

Liveness probe

failureThreshold: 3
httpGet: {}
initialDelaySeconds: 5
periodSeconds: 15
timeoutSeconds: 5

Readiness probe

{}

Startup probe

password: ""
username: ""

Basic auth for remote read

token: ""
tokenFile: ""

Auth based on Bearer token for remote read

""

Token with Bearer token. You can use one of token or tokenFile. You don’t need to add “Bearer” prefix string

""

Token Auth file with Bearer token. You can use one of token or tokenFile

""

VMAlert remote read URL

password: ""
username: ""

Basic auth for remote write

token: ""
tokenFile: ""

Auth based on Bearer token for remote write

""

Token with Bearer token. You can use one of token or tokenFile. You don’t need to add “Bearer” prefix string

""

Token Auth file with Bearer token. You can use one of token or tokenFile

""

VMAlert remote write URL

1

Replica count

{}

Resource object. Details are here

enabled: true

Security context to be added to server pods

{}

Service annotations

""

Service ClusterIP

[]

Service external IPs. Check here for details

""

Service external traffic policy. Check here for details

""

Health check node port for a service. Check here for details

[]

List of service IP families. Check here for details.

""

Service IP family policy. Check here for details.

{}

Service labels

""

Service load balancer IP

[]

Load balancer source range

8880

Service port

ClusterIP

Service type

rollingUpdate:
    maxSurge: 25%
    maxUnavailable: 25%
type: RollingUpdate

Deployment strategy, set to standard k8s default

[]

Node tolerations for server scheduling to nodes with taints. Details are here

enabled: false

Vertical Pod Autoscaler

false

Use VPA for vmalert

{}

Annotations to add to the service account

true

Mount API token to pod directly

true

Specifies whether a service account should be created

null

The name of the service account to use. If not set and create is true, a name is generated using the fullname template

{}

Service Monitor annotations

{}

Basic auth params for Service Monitor

false

Enable deployment of Service Monitor for server component. This is Prometheus operator object

{}

Service Monitor labels

[]

Service Monitor metricRelabelings

[]

Service Monitor relabelings