Transaction Alerts | Transactions filtered for devices do not collect data

[andyl-ioki]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Create a transaction with a specific device, e.g. device:SM-A226B
2. Note the warning icon next to the filter input which states:

   We don't routinely collect metrics from "device". However, we do so once this alert has been saved.

3. Save the alert.
4. Check the alert and see in the Transaction Duration part that the "Summary" shows 100% for the clock icon - "The time spent waiting for metrics matching the filters used."

---

Note:
We made sure that the tag device:SM-A226B and is available for our project. So there are users with this specific device and transactions gathered with it.
We tried also other tags like app.device with the same result.

This is related to an issue I created earlier. Since then it only showed me the empty graph. I thought that it will change over time, but it does not. :(

Expected Result

After a short while the page shows data in the alert graph.
Alerts are triggered (if necessary) properly.

Actual Result

Transactions graph of the alert stays empty (for weeks).
Waiting time stays at 100%.

When clicking on "Open in Discover" you can see a proper graph:

When getting back to edit the rule, even there a proper data graph is shown, with a small information noting "The chart data above is an estimate based on the stored transactions that match the filters specified.":

Note:
I created very low thresholds for this alert to test if at least they trigger, but they didn't. :(

Product Area

Alerts

Link

No response

DSN

No response

Version

No response

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-alerts for triage ⏲️

[roggenkemper]

thanks for bringing this up again! i've reached out to the team in charge of this project to get an answer for you.

[andyl-ioki]

We are receiving data now.
Thanks so much!

[andyl-ioki]

Unfortunately I have to reopen this issue again.
It was working for me at that time, when I wrote the comment above ☝️

But since then I did not have the chance to see the correct view again. It is like described in the issue again. No data at all and waiting time stays at 100%. :(

Maybe I switched your A/B Testing group and did not get back in there? :D

@roggenkemper can you check that again? Thanks in advance :)

[matejminar]

Hey @andyl-ioki , this should be fixed as soon as getsentry/relay#2728 is deployed. 👍

[andyl-ioki]

Cool. Thanks for the reply.

[matejminar]

@andyl-ioki Can you confirm it's working now?

[andyl-ioki]

Hej @matejminar,

All in all: No, it is not working :(

In detail:
Yesterday I checked the existing alert. Rechecked it today as well. I also modified the alert and checked it again after couple of hours. It is still not showing any graph/data. (When I edit the alert, it shows a striped graph with the info that the data is not yet collected but then after saving the modifications of the rule)

I also created a new rule today, with the same filters ... no luck. I also can't see the striped graph. It's just empty.

[matejminar]

I'll have a chat with our ingest team. Everything else looks good from a product standpoint. Sorry for any inconvenience caused.

[andyl-ioki]

Thanks for the fast reply and taking care of it 👍
I will let you know if something changes on our "Alert" side.

[obostjancic]

Hi @andyl-ioki We have taken a closer look at this, and have a suspicion that it is related to the environment filter condition. In order to verify that, would you mind temporarily editing the alert to target "All environments" instead of the currently selected one. It should take a couple of minutes to propagate the change, but after that you should start seeing the data come in.

[andyl-ioki]

@obostjancic I will have a look now 👀

[andyl-ioki]

@obostjancic
Sorry for my late reply.

I have good news - when I removed the filter for the environment the graph starts to show up 🎉

I don't know if the warning and critical messages behave correctly, but we will see.

[obostjancic]

@andyl-ioki Great! 🎉 The fix for environment filter should then land with #59995. I'll link this issue to it, so that you get notified when it's merged.