Comments on: Alarm expressions – Part 1 : Metric alarms

By: LucD

LucD — Mon, 04 May 2015 17:15:21 +0000

In reply to Alex. Well, thank you, much appreciated.

By: Alex

Alex — Mon, 04 May 2015 15:40:08 +0000

Thank you again Luc!
I even gave up counting how many hours saved me your amazing scripts!

By: LucD

LucD — Tue, 15 Nov 2011 19:52:09 +0000

In reply to Ziof3ster. Thanks. I just changed the line where I specify the subject to


$trigger.action.Subject = "{eventDescription}"

The email I received got the correct subject. If that doesn't work for you, send me the script you are actually using (to lucd (at) lucd (dot) info)

By: Ziof3ster

Ziof3ster — Tue, 15 Nov 2011 14:09:14 +0000

Hi LucD,

this script is fantastic and I’ve modified it to my enfvironment (Datacenter Level) to monitor the disk latency.

One question. If I want modify the email’s subject using the {eventDescription} variable, it doesn’t work, and simply prints “eventDescription”.

I’ve used the environmental variable successfully inf I create the AlarmAction using the “new-AlarmAction” cmlet. Any Idea how I can use the Enviromental Variables inside your script?

Thanks

By: Tom

Tom — Thu, 18 Nov 2010 15:06:51 +0000

Luc,

Have you been able to create an alarm using the perfcounter with counterID = 2 “CPU Usage” on a “ClusterComputeResource” ? When you peform a QueryAvailablePerfMetric on a cluster it returns the perfMetric with counter ID 2, so expect it should work however I keep on getting a specified parameter is incorrect…

Any ideas ?

Thanks,
Tom

By: LucD

LucD — Thu, 19 Aug 2010 08:26:00 +0000

In reply to jrob24. Hi Jason, thanks for discovering this bug. The new version of the script should solve the problem.

By: jrob24

jrob24 — Wed, 18 Aug 2010 18:54:26 +0000

Luc,

Every time I run the script to gather all of the metrics for each entity I keep receiving the following error:

Exception calling “QueryAvailablePerfMetric” with “4” argument (s): “entity”

Any ideas? Running against a 4.0 U2 host and vCenter. Using PowerCLI 4.1.

By: LucD

LucD — Tue, 30 Mar 2010 18:46:58 +0000

In reply to Tim. Hi Tim, when you use a metricId that returns percentages you have to multiply the desired threshold values by 100. For example, if you want the alarm to trigger at 75% you would have to specify 7500 in the yellow or red property.

By: Tim

Tim — Tue, 30 Mar 2010 10:39:14 +0000

Hi,

I’ve modified the above to take parameters for VM, alarm name, description, counterid and red and yellow thresholds. Fairly simple modification really, however the alarm (alarm 129) is always triggering and the e-mail shows:

Alarm Definition:
[Yellow metric Is above 0%; Red metric Is above 0%]

Despite me passing in 85/95 as yellow/red. When I try and drill down into the alarm settings for the created alarm:
$alarm = get-view ($alarms | where-object {$_.Value -eq “alarm-50”})
$alarm.info.expression.expression.metric

I don’t get anything back from the metric. The level above ($alarm.info.expression.expression) shows:
Operator : isAbove
Type : VirtualMachine
Metric : VMware.Vim.PerfMetricId
Yellow : 85
YellowInterval : 0
Red : 95
RedInterval : 0
DynamicType :
DynamicProperty :

Any idea?

Cheers,

Tim