[notification::microsoft::office365::teams::plugin]: themes colors not working

[joschi99]

The teams notification will not apply the themes defined into the plugin to highlight the status of the notification with the appropiate color. The teams message is like this one:

[fabien4455]

UP !

I also have the exact same issue. The highlight color is working great on the old teams desktop app. (The green, yellow, and red status OK, WARNING, CRITICAL)

But, on the new teams desktop and webapp, the hightlight color is not here. Please fix this. Microsoft is trying to shutdown the old teams.

[lucie-dubrunfaut]

Hello :)

Does the color theme work if the notification is not "PROBLEM"? Currently the color mapping is as follows:

my $teams_colors = {
        ACKNOWLEDGEMENT => 'fefc8e',
        DOWNTIMEEND => 'f1dfff',
        DOWNTIMESTART => 'f1dfff',
        RECOVERY => '42f56f',
        PROBLEM => {
            host => {
                up          => '42f56f',
                down        => 'f21616',
                unreachable => 'f21616'
            },
            service => {
                ok => '42f56f',
                warning => 'f59042',
                critical => 'f21616',
                unknown => '757575'
            }
        }
    };

If this mapping is not correct, do you have any documentation or other elements that would allow us to create the new color mapping?

[joschi99]

No color is working with Teams 2.0, indipendent if the status

[lucie-dubrunfaut]

Hello :)

So if I understand correctly it's not necessarily that the color mapping is no longer correct but perhaps that since Teams 2.0 it is no longer addressed in the same way or in the same place? If so, do you have any information that would help us know where to send notification colors since Teams 2.0?

[lucie-dubrunfaut]

Hello :)

This topic should benefit from the current development of Teams workflows. Could you give us more information to help us solve this issue in the meantime?

[lucie-dubrunfaut]

Hello :)

Following the update on August release of the Teams connector, a test on the problem of this issue has been added. Can you tell us if the problem remains?