---
title: Charmhub | Deploy Alertmanager using Charmhub - The Open Operator Collection
description: Deploy the latest version of Alertmanager as a Kubernetes Operator on
  any cloud.
url: https://charmhub.io/alertmanager-k8s/configurations
---

# Alertmanager

[Canonical Observability](https://charmhub.io/publisher/observability "View all packages from Canonical Observability")

* [Canonical Observability](https://charmhub.io/publisher/observability "View all packages from Canonical Observability")

Platform:

0.31/stable tf-0.31.1-1-g7796bf8

```
juju deploy alertmanager-k8s --channel 0.31/stable
```

[Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications)

* [config\_file](https://charmhub.io/alertmanager-k8s/configurations#config_file)
* [cpu](https://charmhub.io/alertmanager-k8s/configurations#cpu)
* [memory](https://charmhub.io/alertmanager-k8s/configurations#memory)
* [templates\_file](https://charmhub.io/alertmanager-k8s/configurations#templates_file)
* [web\_external\_url](https://charmhub.io/alertmanager-k8s/configurations#web_external_url)

[Learn about configurations >](https://juju.is/docs/juju/configuration#heading--application-configuration)

* config\_file | string

  Alertmanager configuration file (yaml), with the exclusion of the templates section. To send the contents of a file to this configuration option, the symbol `@` must be used.
  Usage: `juju config alertmanager config_file=@alertmanager.yaml`
  For more information on configuring the Alertmanager, refer to: https://www.prometheus.io/docs/alerting/latest/configuration/
* cpu | string

  K8s cpu resource limit, e.g. "1" or "500m". Default is unset (no limit). This value is used
  for the "limits" portion of the resource requirements (the "requests" portion is
  automatically deduced from it).
  See https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
* memory | string

  K8s memory resource limit, e.g. "1Gi". Default is unset (no limit). This value is used
  for the "limits" portion of the resource requirements (the "requests" portion is
  automatically deduced from it).
  See https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
* templates\_file | string

  Alertmanager templates definition file. This is a slight deviation from the official alertmanager config spec. All templates need to go into this single config option, instead of the 'templates' section of the main configuration file. The templates will be pushed to the workload container, and the configuration file will be updated accordingly. Templates can't be used without `config_file`. Refer to https://prometheus.io/docs/alerting/latest/notification\_examples/ for more details on templates.
* web\_external\_url | string

  DEPRECATED. This config option is no longer used, in favor of "skipPrefix".

  The URL under which Alertmanager is externally reachable (for example, if
  Alertmanager is served via a manually configured ingress).

  This config option is used for the `--web.external-url` alertmanager cli
  argument. If this charm config option is provided, it takes precedence over the
  URL provided over the "ingress" relation.

  Note: this config option shouldn't be included when you're using the "ingress"
  relation (e.g. traefik) - the charm will automatically assign an external url
  to `--web.external-url` when related to an ingress provider.

  This should be a complete URI, including scheme, or a fully qualified subpath
  starting with `/`.
  If Alertmanager is being served directly from the root of a fully-qualified
  host or a bare A record, this may be omitted.
  If the URL has a path portion, Alertmanager will use it to prefix all HTTP
  endpoints.