How do I get the vcenter name in alert emails

Hello! 

I'd love to take a crack at this! Do you mind sharing your alert Trigger Condition page, if possible? That will let me know what you're already working with and what conditions you're looking to alert on. Feel free to PM me on thwack if you don't feel comfortable posting on this post.

Hello! 

I'd love to take a crack at this! Do you mind sharing your alert Trigger Condition page, if possible? That will let me know what you're already working with and what conditions you're looking to alert on. Feel free to PM me on thwack if you don't feel comfortable posting on this post.

I did some initial testing in my lab with a dummy alert I set up. Please add this to your e-mail message body:

${N=SWQL;M=SELECT VCenterName
FROM Orion.VIM.VirtualDisks
WHERE VirtualMachineID = ${N=SwisEntity;M=VirtualMachine.VirtualMachineID}}

Thank you! I hope this helps! This kind of interaction is one of the things I love the most about Thwack. Everyone has "communities" these days, but most are just boards where stuff is posted, not communities where people help each other. Thwack is a community!

Hey flackovic, this is the trigger condition I am using.

I did add the your code to my alert but it does not bring any info back. 

Also, don;t you think it is weird that the only place in the database where you can find the VcenterName is in the Orion.VIM.VirtualDisks table?

Thanks so much for looking at this, I am super excited to get past this one!!  :-)

I went ahead and put in a feature request to make the vcenter name available in the Insert Variables option.

https://thwack.solarwinds.com/product-forums/the-orion-platform/i/feature-requests/make-the-vcenter-name-available-as-a-variable-in-alerts-for-vmware-triggered-alerts

I am hoping to maybe get traction this way.  :-)

Done voting in.

@Rachel.Davidson sent you a message about the Feature request

 Yeah that should work. I did a quick test using a mock up with that alert type and scope. No goodnik. I tried a couple of variations - also no good. This is a weird one. Already bumped the feature request. 

Voted! 

Thanks donrobert5,  I will see about getting that part blacked out.  :-)

Hi Rachel,

Came to this thread thinking "I know this", and then saw that alert condition and thought "when did that go in?!"

in general the macros section kinda work by calling a value with reference to whatever table your alert condition starts on (home). So if someone's alert starts in the hardware table, their solution wont work for you, same for the hosts table or the vcenter table, or whatever else.

No idea you could start in triggered alarms now!

I'll give it a test when I can, but in general you can either:

1) use the macros section, select by category, and look through tables that seem related to what you're trying to achieve

2) build your own in the format of a SWQL query a bit like

SELECT r.thing
FROM relatedTable r

or 

SELECT h.detailTable.thing
FROM homeTable h

That produces the sort of data you care about, then add a where condition like

WHERE r.ID = '${ID_MacroFromTheSelector}'

So that it filters down to the thing you care about

(then you might also need to add a block for a UNION or CASE or subquery such that it always produces output and doesnt spit back the SWQL)