bcgov / bcgov/devops-platform-workshops

A couple problems in 201 lab

未关闭
#256 1 条评论 0 个 reaction 已指派 1 人 已被 @alitman-bcgov 认领 在 GitHub 查看
主要语言
JavaScript
星标
39
派生
52
平均合并
5 天 1 小时
30 天内合并 PR
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 摘要。