ubuntu/alertmanager repository overview

ubuntu/alertmanager is a rock for alertmanager maintained by Canonical⁠.

The Alertmanager handles alerts sent by client applications such as the Prometheus server. It takes care of deduplicating, grouping, and routing them to the correct receiver integrations such as email, PagerDuty, OpSGenie, or many other mechanisms thanks to the webhook receiver. It also takes care of silencing and inhibition of alerts.

[Learn more about alertmanager⁠]

⁠Tags and Architectures

NOTE: These tags follow a specific naming convention that respects the concept of channels⁠.

⁠Get started

This rock's entrypoint is Pebble, a container-optimized init process that enables the orchestration of a collection of local service processes as an organized set.

[Learn more about Pebble⁠]

⁠Inspect

To view the Pebble services⁠ and checks⁠ defined in this rock:

docker run --rm ubuntu/alertmanager:0.32-26.04_stable plan

⁠Run

To run this rock, use any of the usual container runtimes, for example, docker:

docker run --name alertmanager-container \
    -p 9093:9093 \
    ubuntu/alertmanager:0.32-26.04_stable

Alertmanager starts on port 9093. Access your Alertmanager instance at http://localhost:9093.

⁠Get logs

To view the logs of the running container, run:

docker exec alertmanager-container pebble logs

Or, for a specific service:

docker exec alertmanager-container pebble logs <service>

⁠Monitor health checks

Rocks may have predefined health checks that you can list by running:

docker exec alertmanager-container pebble checks

The overall health of your container can be inspected via:

docker exec alertmanager-container pebble health

⁠Configuration

⁠Environment variables

⁠Volumes

⁠Ports

[Report a bug⁠] [Contribute⁠]

Canonical is the provider of this container image. It is the user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within, as well as with Canonical’s IP Policy⁠.