AES does not offer this feature OOTB but it can be added
a- create an agent and activity to check file system. Schedule it to run on each node periodically.
b- In the agent, if file system space is not sufficient, use the loghelper 'alert' method do send an alert code to files and AES -- say "OSFS0001".
By default, if AES 73 does not recognize an alert code, it should store the alert and create a single generic case for that alert per system. To do this right, you'd need to create a new action item class; correlate these issues probably using system name and node name; and clone some of the logic and artifacts from the PEGA0010 message logic (agent failed); create a file system issue scorecard and add that scorecard to the subscription menu.