Drive Space Alert Automation - Is there a way to map a Volume to a Node in SWQL?

martian_monster

This is building off this article about Alert Automation -  Alert Automation for Drive Space 

I have a little over 1000 Windows nodes and I am trying to figure out a way to separate production nodes/volumes from anything else that is not production.  

I have a node alert automation to set who is the node owner for alerting and that is working great.  

My brain is having issues trying to figure out how to scope the volume alert to only production volumes. I can go through and create the trigger condition and I will get the SWQL and open it in SWQL studio and it will report the Volume and give me the URI for the node but not the node name.  I am trying to see if the scope of the alert is correct or not.  If anyone has any suggestions or if I am going about this completely wrong let me know.   

I did create a Volume Custom Property to designate a volume if it was production or not but then I would have to manually go through and apply that to each production volume. Which puts me back to where I started. 

Thanks! -Dave

equalswql

Hello @martian_monster ,

When you copy the SWQL logic from the alert and copy it to SWQL studio, it usually looks something like this (forgive me I'm pulling from memory here):

E0.URI, E0.DisplayName FROM Orion.Volumes E0 (or something like this)

In order to add a column to view the node name, you would have to use either a JOIN or dot walking to pull in the node caption.

Dot walking is easier IMO, I'll post a screenshot later as an example of where you can find the entities linked underneath the appropriate namespace/table in SWQL Studio.

For now, you would update your query like so:

E0.URI, E0.DisplayName, E0.Node.Caption, E0.Node.CustomProperties.[Insert A Node Custom Property Here if Needed], E0.CustomProperties.[Insert a Volume Custom Property Here if Needed]

FROM Orion.Volumes E0

[ALL THE WHERE LOGIC FROM YOUR ORIGINAL ALERT]

Also, in reference to filtering by production volumes, one way to solve this problem (and I'm not saying it's done easily) is to ensure that standardization for naming conventions includes a way of easily capturing Dev/Prod/UAT etc by using a naming convention - maybe it starts with D / P / U accordingly as an easy example.

If standardization doesn't exist to allow this, then unless there is another logic, custom property tagging is the way forward. If you wanted to bulk update volumes, there should be a way to export that for the nodes in scope and update via modifying the csv in excel, then reimport the custom property data to update the environments en masse.

I hope this helps!

=swql