@jklaverstijn , indeed, but beware of what you want to monitor and how. In case that the SAS Environment Manager server is deployed on the same server than any of the SAS tiers, and the server is down, you won't receive any email or be able to access the SAS Environment Manager, because it will be down too.
There are other considerations as well: SAS Environment Manager depends of SASServer1_1 for the Logon and other services as the SAS Content Server, and it depends as well of the SAS Environment Manager Datamart.
To create a real and good SAS Environment Manager implementation, 100% available and usefull for the full purpose, it is required to apply a special deployment (cluster, specific location for EVDM, etc). A bit complex and not really worthy (but always nice to have!) for all the SAS deployments.
Therefore, to provide a more extended proposal:
1st stage: As the initial question was on how to monitor the server/s of SAS, I always suggest to have an external monitoring tool for the most basic monitoring, for starters, one that is used at a company level.
2nd stage: For the specific SAS services and multiple items/components to monitor, the SAS environment manager is the best, because it is already configured. Works like a charm!
3rd stage: In case that you want also to receive information of the specific SAS services on your centralized monitoring tool, you can create alerts that can be exported and linked from the SAS Environment Manager, then import them in your centralized monitoring tool.