bcgov / bcgov/devops-platform-workshops

A couple problems in 201 lab

Offen
#256 1 Kommentar 0 Reaktionen 1 zugewiesene Person Beansprucht von @alitman-bcgov Auf GitHub ansehen
Vorherrschende Sprache
JavaScript
Sterne
39
Forks
52
Ø Merge
5 T. 1 Std.
Gemergte PRs (30 T.)
1

Beschreibung

First of all, this is incorrect, on the [Openshift 201 page about logging/alerting](https://github.com/bcgov/devops-platform-workshops/blob/master/openshift-201/logging.md#alerting):

Image

... it should be this:
`oc -n [-dev] describe alertmanagerconfig platform-services-controlled-alert-routing`

----

Secondly... and I'm not certain if this is a bug or a misunderstanding on my part of how alerts work.:

At 3:20 in the video, we're looking inside the `AlertManagerConfig`, and it shows this:

Image

Meanwhile, in the `AlertingRule` that we set up to go with it, we specify this:

Image

Doesn't this mean that this alert will NOT actually get sent to our TechLeads, because it is "critical", and they are only set up to receive "info" or "warning" alerts?

Also, since the "info/warning" is from the default AlertManagerConfig that our projects come with, isn't _that_ a bug in and of itself? i.e. Shouldn't the tech leads be receiving emails about "info-level _or worse_"? i.e. info, warning, AND critical? (And any other levels that might exist that are elevated.)

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.