We've been getting a few Mendix Monitoring alerts recently about CPU and DB usage in our test environments, the alerts are useful, but a lot of the time you really need to dive in and search for whats actually causing the problem. Waiting around for the logs to generate so you can see whats happened, and even then they don't always specify helpful information.
Would be very useful to simply add into the email, any current running microflows on the environment, which will give you a much better idea of whats actually causing the problem, from just looking at the info in the email.
Can imagine it would be pretty simple to retrieve that information and add it to email, as guesing that those emails are generated based off the Metrics page on the Mendix developer home environment overview?
Could be easy, useful and get some good feedback!