chore(spans-migration): add isolation scope to misfire and action tags in alerts comparison

[nikkikapadia]

was getting scope bleed for the trigger action counts so adding in the isolation scope

[cursor]

Bug: Misfire tags captured in scope with no event

The isolation scope at lines 330-334 sets misfire and trigger action tags but doesn't capture any event within that scope. The tags exit the scope without being associated with any Sentry event, making them ineffective. These tags should either be moved into the isolation scope where capture_message is called at line 352, or capture_message should be called within this scope.

 

[codecov]

❌ 2 Tests Failed:

Tests completed	Failed	Passed	Skipped
29947	2	29945	245

View the top 2 failed test(s) by shortest run time

tests.sentry.discover.test_compare_timeseries.CompareAlertsTimeseriesTestCase::test_false_negative_misfires

Stack Traces | 4.7s run time

#x1B[1m#x1B[.../sentry/discover/test_compare_timeseries.py#x1B[0m:214: in test_false_negative_misfires
    mock_set_tag.assert_any_call("false_positive_misfires", 0)
#x1B[1m#x1B[.../hostedtoolcache/Python/3.13.1.../x64/lib/python3.13/unittest/mock.py#x1B[0m:1048: in assert_any_call
    raise AssertionError(
#x1B[1m#x1B[31mE   AssertionError: set_tag('false_positive_misfires', 0) call not found#x1B[0m

tests.sentry.discover.test_compare_timeseries.CompareAlertsTimeseriesTestCase::test_false_positive_misfires

Stack Traces | 6.57s run time

#x1B[1m#x1B[.../sentry/discover/test_compare_timeseries.py#x1B[0m:195: in test_false_positive_misfires
    mock_set_tag.assert_any_call("false_positive_misfires", 1)
#x1B[1m#x1B[.../hostedtoolcache/Python/3.13.1.../x64/lib/python3.13/unittest/mock.py#x1B[0m:1048: in assert_any_call
    raise AssertionError(
#x1B[1m#x1B[31mE   AssertionError: set_tag('false_positive_misfires', 1) call not found#x1B[0m

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}