aboulton

Comments

  • Note that the 2nd simple condition in my screen shot was set to ANY if you only want this alert to trigger when both volumes are below you would simply need to change that simple condition from ANY to ALL
  • This is how I was able to setup the alert to alert on a specific volume, as I stated in the prior post. Thank you for all the help thinking this through.
  • I found a way to specify the Node in the volume details with the volume full name and that seems to be working now. Thank you for the help!
  • Try this, I just cleaned my alerts up over the weekend and this is working for me:
  • I am not sure if this is still the case but in the past I was told by support it is not recommended to mix node and volume details in my alert triggers. So I had to set my alerts up like I have below. Trigger alert when any of the following apply Volume Description is equal to E:\ Volume Description is equal to F:\ Volume…
  • I am actually removing that currently, and adding the node portion into the alert suppression. to see if that corrects the issue. What I have in the suppression is: Suppress Alert when all of the following apply Node Name is not equal to X This alert should then only fire off when node X Has a volume that has fallen below…
  • thank you Jaminsql, That is where I was entering the the key and recieving the error message. I have a feeling there is something wrong with the key I recieved. My account manager is having someone reach out to me just need to wait. Thank you again for the answer. At least I know Im not doing something worng on my end when…
  • Thank you for the quick answer. I just printed out the information on setting up the dependencies. I will give that a try. Thank you
  • I like your message formatting thanks for putting this together and sharing. I know this is an old post but I thought I would add something I have been using with my alert Email messages. As long as you select the html message format you can use html font color and type codes to add easy identification to your alert…
  • Jaminsql, Thank you for the help. After further review it looks like our account manager sent the wrong key. I should have the correct key sometime today. Thanks again for the assistance.
  • We found a way to accomplish this by changing the alert from alerting on the application to alert on the component. This allowed me to add the following to the email message: ${N=SwisEntity;M=Application.Node.NodeWarrantyAlert.HostName} ${N=SwisEntity;M=Application.Node.Location}…