Alertmanager-k8s docs - index

Charmed Alertmanager

alertmanager-k8s is a charm for Alertmanager. It is an essential part of the COS Lite bundle.

This Charmed Operator handles instantiation, scaling, configuration, and Day 2 operations specific to Alertmanager.

This operator drives the Alertmanager application, and it can be composed with other operators to deliver a complex application or service.

The charm imposes configurable resource limits on the workload, can be readily integrated with alert sources such as prometheus or loki, and comes with built-in alert rules and dashboards for self-monitoring.

This charm is:

  • part of the COS Lite bundle
  • intended to be used together with prometheus-k8s

In this documentation

Tutorial
Get started - a hands-on introduction for new users deploying the charmed operator.
How-to guides
Step-by-step guides covering key operations and common tasks
Explanation
Concepts - discussion and clarification of key topics
Reference
Technical information - specifications, APIs, architecture

Project and community

Charmed Alertmanager is part of the Canonical Observability Stack. It’s an open source project that warmly welcomes community projects, contributions, suggestions, fixes and constructive feedback.

Thinking about using the Canonical Observability Stack for your next project? Get in touch!

Navigation

Level Path Navlink
1 Tutorials Tutorials
2 integrating-with-receivers Integrating with receivers
2 writing-great-alerts Writing great charmed alert rules
1 How To How To
2 integrating Integrating
1 Reference Reference
2 solution-matrix Solution matrix
2 Security Cryptographic documentation for COS-Lite charms
1 Explanation Explanation
2 topology-labels Juju topology labels

Redirects

Mapping table
Path Location

Hi @tmihoc,

What is our deletion policy? Per alertmanager-k8s/112, this page and all subpages can be deleted.

1 Like

@sed-i Just adding a comment to let people know that, in light of our discussion, this doc will not be deleted but rather updated.

Page updated in the spirit of Nginx Ingress Integrator docs - index

TODO: Reuse the following existing (unused, outdated) pages: