bcgov / bcgov/devops-platform-workshops

A couple problems in 201 lab

Open
#256 1 comment 0 reactions 1 assignee Claimed by @alitman-bcgov View on GitHub
Dominant language
JavaScript
Stars
39
Forks
52
Avg merge
5d 1h
Merged PRs (30d)
1

Description

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

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.