Hello,
We followed below link to set up the integration with our Teams but, nothing seems to be come through to our channel.
#------------------------------------------------------------------------------
# Microsoft Team (office.com) global notification options
# More details are available here regarding the payload syntax options : https://docs.microsoft.com/en-us/outlook/actionable-messages/message-card-reference
# Online designer : https://acdesignerbeta.azurewebsites.net/
# multiple recipients can be given like this:
# "CHANNEL1 CHANNEL2 ..."
# enable/disable sending team notifications
SEND_MSTEAM="YES"
# if a role's recipients are not configured, a notification will be send to
# this slack channel (empty = do not send a notification for unconfigured
# roles):
# For team the channel name is encoded in the URI after ....IncomingWebhook/___/.....
# This value will be replaced in the webhook value to publish to several channels in a same Team.
# In order to get it working properly, you have to replace the value between [] ....IncomingWebhook/[___]/..... by "CHANNEL" string.
DEFAULT_RECIPIENT_MSTEAM=""
# Based on the way MS Teams is working, put the differents channels here like : "CHANNEL1 CHANNEL2 ..."
# AT LEAST ONE CHANNEL IS MANDATORY
MSTEAM_WEBHOOK_URL=""
show original
Guys, cannot wait to see that! Thanks
@nitsan-reznik thx for the comment. Also in Cloud we are preparing a centralized alarm notifications feature. Integrations with Slack and Microsoft Teams are some we intent to do early.
Hi,
That would be useful.
We look forward to seeing that guide,
Hi Nitsan,
No worries, we will figure something out. Thanks!
Happy monitoring
Hi,
Thank you for your response. It would be highly useful to have a guide with screenshot once completed
Thanks Thiago for jumping to this thread!
Hello @nitsan-reznik ,
We have a PR now at Msteams 2 by tomcbe · Pull Request #9905 · netdata/netdata · GitHub that brings fixes for Teams, but we are waiting for the user to do a rebase for we move forward with it.
We were also expecting some instructions to test the PR, so it is possible that your problems will be fixed when the PR is merged, but right now we cannot move forward with it.
Best regards!
