Synthetics monitor status rule — context.monitorName and context.locationName empty in recovery notifications after long-duration alert

After further investigation, we have gathered more data points that make this issue harder to reproduce consistently:

  • A different alert that was active for 6 days (April 7 → April 13) recovered correctly with all context variables populated :white_check_mark:
  • The problematic recovery (April 11 → April 13, ~2 days) arrived with all context variables empty :cross_mark:
  • The issue has also occurred in a separate space with only a single monitor configured, so grouping/aggregation is definitively ruled out as the cause
  • The "Receive distinct alerts for each location" toggle was enabled in the rule where the issue occurred, so location grouping is also ruled out

This means the issue is intermittent and not consistently reproducible, which makes it harder to diagnose. The failure does not seem to be related to:

  • Alert duration (6 days worked fine, 2 days failed)
  • Number of monitors (happened with a single monitor)
  • Location grouping settings (happened with distinct alerts per location enabled)

Has anyone seen this kind of intermittent behavior with Synthetics monitor status rules? Could this be related to a transient issue in the alerting task runner or a race condition during recovery evaluation?