One of the most common alerts that we get is the Long Running Query alert. However, when the query is due to a package executing from an agent job, there is little to no information about what is running long. The attached image is an excerpt from one of the alerts we got this morning. We can tell it is from an executing job, because of the SSISDB database specified. But beyond that, we are left trying to figure out which job/package was the culprit by digging through execution logs and schedules, then trying to match execution lengths with where the alert would have been triggered. Maybe in a future release you can add which package is executing that triggered the alert.