Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Developer Guide] Alerting routes #96

Open
Tracked by #81
AshwinSriram11 opened this issue Aug 7, 2024 · 0 comments
Open
Tracked by #81

[Developer Guide] Alerting routes #96

AshwinSriram11 opened this issue Aug 7, 2024 · 0 comments

Comments

@AshwinSriram11
Copy link
Member

AshwinSriram11 commented Aug 7, 2024

We currently have an "Alerting" page in the developer guide that teaches how to deploy Alertmanager and configure it through secrets and AlertmanagerConfig.

With the Platform/Developer relationship that is the focus of our new website structure, it doesn't make much sense to write it this way. #101 focuses on the content for the Platform guide, while this one focuses on the Developer experience.


Planned content:

  • Briefly explain how using a secret is a terrible experience. AlertmanagerConfig to the rescue!!! Goal is to make it clear that for a Platform team, it is advised to build automation around AlertmanagerConfig instead of k8s secrets.
  • Explain how alertmanagerconfig aims to replicate the original Alertmanager configuration struct.
  • Alertmanager has ...configSelectors, Developers are free to decide on their alert routes simply by deploying new AlertmanagerConfig resources. The operator will merge all selected resources before writing the configuration.
@ArthurSens ArthurSens changed the title AlertmanagerConfig page in Developer Guide [Developer Guide] AlertmanagerConfig page in Developer Guide Aug 20, 2024
@ArthurSens ArthurSens changed the title [Developer Guide] AlertmanagerConfig page in Developer Guide [Developer Guide] Alerting routes Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant