edr monitor --teams-webhook giving error #1644
Comments
|
Hey @JyotsnaMalode, |
|
hi @dapollak , I am using below command I am using Teams workflow and not Teams webhook as it will soon be not supported When I check the raw output for "When a Teams webhook request is received" in Wrokflow, I get below data |
|
Hi, same error here. pymsteams appears not to have a solution yet. A workaround could be sent alerts in plain text and allowing ok status code between 200 <= x < 300. |
|
Thanks @mriveraFacephi , will try your suggestion. |
|
I also tried to setup MS Teams alerts with the new Power Automate workflow method, because the connector already does not work anymore for us.
|
|
Update - workaround suggested by @mriveraFacephi worked for me to receive the text message. |
|
Hey @Jonathan-MW , I am having the same issue. Did you try the solution provided by @mriveraFacephi ? I tried but does not seem to work :/ |
|
In short, we will need for an update from pymsteams in order to solve this issue or is there any other option we can use to solve this problem? |
|
@FredRodrigues I think we could also suggest to the elementary team to start using https://github.com/AeroFlorian/MsTeamsAdaptiveCard/tree/master instead of |
|
@ellakz I just looked into this issue and verified that moving the existing webhooks we have to the new webhooks as defined by MS Teams, but then I also get an error: ERROR — Unable to send alert fallback via Teams: 'Response' object has no attribute 'body'When looking at the documentation of MS Teams we will have to migrate to a new solution before 31 januari 2025:
What do you think about my above suggestion to start using another package to send messages to MS Teams? |
|
Hi @JyotsnaMalode, As the deprecation deadline for Office 365 Connectors approaches, we're working on adding support for sending alerts to Teams via workflows. Currently, when we can't format the message, we send a fallback message with JSON data to ensure you're notified about the alert. However, this fallback message is also not in the Adaptive Cards format, so it fails in workflows, which is why you see the error in Power Automate. You might also see another error related to the original alert. Until we roll out support for the Adaptive Cards format, I suggest using the Incoming Webhook application as a temporary solution, if possible. You can pass the URL generated by the Incoming Webhook to Regarding the ERROR log, @FrankTub, this was a minor bug in logging the actual error when sending the alert. I've deployed a quick fix for this today, so it should now print a more accurate message. |
|
@MikaKerman , can I test this by pinning the version of elementary to use as the master branch? |
|
@MikaKerman , I tried to test it out for you but this results in worse behavior in my opinion, see explanation below. I pinned Elementary to the last commit on master in my elementary-data @ git+https://github.com/elementary-data/elementary@masterNext I ran something like: edr monitor --profiles-dir $DBT_PROFILES_DIR --teams-webhook "$MS_TEAMS_DATA_QUALITY_WEBHOOK_URL" --report-url "$DATA_QUALITY_REPORT_URL"This does not result in an error, but no messages are sent to the Teams webhook: |
|
@MikaKerman , I tried out following some time ago and that works for this new webhook in Teams: import requests
from adaptive_cards.card import AdaptiveCard
from adaptive_cards.elements import TextBlock, Image
import adaptive_cards.card_types as types
# Replace with your Teams webhook URL
webhook_url = "some-url"
text_block: TextBlock = TextBlock(
text="It's your third card",
color=types.Colors.ACCENT,
size=types.FontSize.EXTRA_LARGE,
horizontal_alignment=types.HorizontalAlignment.CENTER,
)
image: Image = Image(url="https://adaptivecards.io/content/bf-logo.png")
version: str = "1.5"
card = AdaptiveCard.new() \
.version(version) \
.add_items([text_block, image]) \
.create()
payload = {
"type": "message",
"attachments": [
{
"contentType": "application/vnd.microsoft.card.adaptive",
"content": card.to_dict()
}
]
}
response = requests.post(webhook_url, json=payload)
if response.status_code == 200:
print("Message sent successfully!")
else:
print(f"Failed to send message. Status code: {response.status_code}, response: {response.text}")Resulting output in Teams: 
Perhaps this can point you in the right direction? |
|
@FrankTub dont forget the suppression-interval is by default 24hours
I would add --supression-interval 0 and should send messages to teams. We are currently facing a similar issue, we get the message "ERROR — Unable to send alert via Teams: 'Response' object has no attribute 'body'" but somehow it still sends the message, we are using workflows on teams to parse the message and post the alert on the channel because for our use case we only need the title and description. |
|
@FredRodrigues , pretty sure that |
|
Hi @FrankTub |
Describe the bug
When I execute below command:
edr monitor --teams-webhook giving error
Getting below error in Power Automate workflow
Oops, we failed to format the alert ! -_-' Please share this with the Elementary team via https://elementary-data.com/community or a https://github.com/elementary-data/elementary/issues/new|GitHub issue."
To Reproduce
Steps to reproduce the behavior:
Also getting below error in PowerAutomate
Expected behavior
I was expecting to see alerts in Teams channel
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
pip show elementary-dataVersion: 0.15.1
packages.ymlfileversion: 0.14.1
1.7.10
Redshift
Additional context
Add any other context about the problem here.
Would you be willing to contribute a fix for this issue?
Let us know if you're willing to contribute so that we'll be able to provide guidance.
The text was updated successfully, but these errors were encountered: