This message is typically shown when resource usage is or was extensively being used. This could be due to e.g. a memory leak on the system or insufficient resources or if Cassandra is running on the DM server, a compaction/repair could trigger it as well,...
Normally these exceptions/errors are linked to certain processes. I would suggest to look at the trends of the memory usage (VM Size) of these processes in the Task Manager in the Microsoft element of that server. Or you could also look at a more general memory parameter, like the Physical Memory Usage or Available Physical Memory. This will provide a global view on the memory but won't go into details.
Based on the trends, you'll likely find timestamps, which can be used to look into logs or the event viewer and match with e.g. certain actions.
The easy route would be a DM restart/server reboot, which would certainly be acceptable for single occurrences.
However if this is something that reoccurs often, you might want to dig deeper (starting with the above) or even contact firstname.lastname@example.org