bcgov / bcgov/devops-platform-workshops

A couple problems in 201 lab

オープン
#256 コメント 1 件 リアクション 0 件 担当者 1 名 @alitman-bcgov が担当を希望しています GitHub で見る
主要言語
JavaScript
スター
39
フォーク
52
平均マージ
5日 1時間
マージ済み PR(30日)
1

説明

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.)

コントリビューションガイド

このリポジトリのコントリビューションガイドは索引されていません

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。