I was looking at the code for the perf-alert plugin because I wasn't sure if it followed the same workflow as the backup-reports plugin where it sends emails and delivers to multiple transports. As it turns out, it only sends emails that are configured in the plugin, but I would love it to use the other transports available if they're set up like transport-slack, etc. As a user who is interested in expanding my monitoring footprint in my infrastructure, I think the perf-alert plugin should follow the same reporting/alerting mechanisms as the backup-report plugin and notify to transport-slack along with others. In my case I use Discord, but Mattermost, etc. users would all benefit based on the format the transport-slack plugin already provides. Reading the code it seems like the Plugin system would benefit from having a singular "alerting" layer that you send messages to within each plugin and then the transport plugins just relay the messages to their appropriate APIs (this would likely require rethinking the plugin archictecture however, so not an actionable item), similar to a job queue.

I would probably be able to file a PR to add this functionality, but I'm not confident enough to give it a go at the moment as I'd like to understand the implications of adding said code first. For now, I'll leave this as a feature request as I think most people would find this a welcome addition.