Microsoft Teams integration should reflect current issue status on card / post updates in thread
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 624
Description
### Problem Statement
We use Sentry integration with Microsoft Teams. It creates cards for incoming Sentry issues in a dedicated Teams channel, so that we are notified when new issues pop up.
However, unfortunately, the cards do not reflect anything that has been done in Sentry on the issue after the notification has been posted. You have to open Sentry to see if the issue has been dealt with and whether the notification can be ignored.
There are buttons on the cards like "Resolve" and they only show the status if the issue has been resolved via those buttons and not if it was resolved in Sentry.
To address this, we have agreed in the Team, that we should comment on the cards to make it clear whether the issue has been dealt with, but it's very annoying, because it leads to double bookkeeping (in Sentry and in Teams).
### Solution Brainstorm
Sentry could update the cards that it creates with the latest status (issue open, closed, merged and so on), by changing the background color of the card - right now all cards look the same.
Sentry could mirror comments that are made in Sentry as comments under the cards. We actually want the comments to be made in Sentry, so that they are there if the issue is reopened or related issue is investigated.
Probably on can generate even more ideas, but the most important is to at least make it possible to reliably see on the first glance if the notification has been dealt with or not (see the background color idea).
We want to define a set of [lightweight metrics]() that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that **do NOT overlap with Tracing**. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.
Examples**:**
* Node.js runtime metrics (e.g., event loop delay, heap usage)
* Prisma-related metrics in Next.js
* Mobile CPU / memory usage to help surface potential ANRs or app hangs
---
**Candidate Metrics (add more below)**
* …
*(please also add ideas, questions or examples in comments)*
Contributor guide
Assessment
This issue has not been assessed yet.