This is important. I am also trying to migrate my myriad of notifications and alerts to this method as the connectors will begin to stop working in August.
It seems the Graylog format is not Adaptive Card compatible, as I have tried many iterations of trying to get it to work.
Are any of the Graylog team addressing this or even looking at it? Seems a pretty important part of the whole use case of graylog in the first place… If you can’t notify, graylog’s value plummets (at least for us).
Graylog v6 supports custom HTTP notifications that can be used to create a webhook. There are Microsoft Workflow templates for working with webhooks. Have you tried this method?
Yes, however it doesnt seem to let you configure the payload. Graylog forces the title and the subtitle in its own code, rather than allowing that to be configured in the message part of the notification. This seems to break the Workflow since MS expects the cards formatted a particular way.
Are you trying to use the existing Microsoft Teams Notification or the new Custom HTTP Notification released in 6.0? The Teams Notification does not allow for payload changes but the Custom HTTP Notification does. I am currently working on a generic payload that will work with Adaptive Cards, but if you already have experience migrating other notifications to use the Adaptive Card payload it may be pretty easy for you to get something working for your use case.
Wanted to give a quick update on this one - an updated version of the Teams notification within Graylog will be available in our September maintenance releases (and in the upcoming Graylog 6.1 version). However, if you are on 6.0 or later and want to test out the Power Automate Workflow today you can use the attached workaround. MicrosoftTeamsWorkflowNotifications.pdf (268.0 KB)