Allow users to customize the Teams message card about prometheus-msteams HOT 12 CLOSED

Did somebody already start to work on that? If not, I would do so.

from prometheus-msteams.

@Knappek I haven’t planned on working on this yet. Feel free to play around and see how you can bring this feature to life. Thanks.

from prometheus-msteams.

Just realized that a message card is not only limited to a size of 14KB but also to a maximum number of 10 sections (see https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/cards/cards-reference#notes-on-the-office-365-connector-card). Hence, we still have a bug that seemed to be fixed #29 . I will address this in the PR for this issue.

from prometheus-msteams.

@bzon I have created another PR draft: #37. We might need to talk about how to handle too large message cards as I think this might not be possible anymore using this templating approach (see my last commit).
Therefore, I thought of make it super easy and send out a teams message for each and every prometheus alert.

from prometheus-msteams.

@bzon is very busy these days, therefor I'd like to have some input from other folks. @LudwigTirazona @shabeermm @daviddob what do you think about sending out a teams message for each and every prometheus alert and don't combine multiple alerts to a single teams message card. Would that be a problem for you? I want to have your opinion on that as you were involved in #29.

from prometheus-msteams.

from prometheus-msteams.

Good point, I didn't know about the MS Teams api rate limit. I agree that it is more appropriate to bundle alerts to single message cards...

Then I'd like to verify my assumptions how to split messages in case that they are too big: Referencing a detailed example teams message card we need to split the sections part as this is the part where we loop over the prometheus alerts as shown in this example card template, am I right?

from prometheus-msteams.

Correct! :)

from prometheus-msteams.

PR #37 implements the functionality described in this issue. Just a few little things missing (like updating Readme etc.) that I will add in the upcoming days.
Would be great if some people can already test it and provide some feedback. @sosoriov this might be of interest for you as well.

from prometheus-msteams.

@cordula-grau fyi, this enhancement solves #27 .

from prometheus-msteams.

opened PR #37 . Would appreciate some code review, otherwise I'll merge it in the next couple of days and create the minor release 1.1.0.

from prometheus-msteams.

This feature is now available in v1.1.0 release.

from prometheus-msteams.