Heat/Using-CloudWatch - Revision history

Blues-man at 09:30, 1 July 2013

2013-07-01T09:30:19Z

Shardy at 07:58, 14 May 2013

2013-05-14T07:58:12Z

Ryan Lane: Text replace - "NOTOC" to ""

2013-02-17T23:30:00Z

Text replace - "__NOTOC__" to ""

Ladquin at 00:54, 17 February 2013

2013-02-17T00:54:45Z

Asalkeld at 22:34, 13 November 2012

2012-11-13T22:34:40Z

New page

__NOTOC__
Note: the current cloud watch implementation is incomplete (it only sufficient for [HA](https://github.com/heat-api/heat/wiki/Using-HA)). But should be easy to make more generally useful.

To use cloud watch you need the following in your template:

<pre><nowiki>
"MyOwnAlarm": {
"Type": "AWS::CloudWatch::Alarm",
"Properties": {
"AlarmDescription": "Restart the WikiDatabase if httpd fails > 3 times in 10 minutes",
"MetricName": "ServiceFailure",
"Namespace": "system/linux",
"Statistic": "SampleCount",
"Period": "300",
"EvaluationPeriods": "1",
"Threshold": "2",
"AlarmActions": [ { "Ref": "WebServerRestartPolicy" } ],
"ComparisonOperator": "GreaterThanThreshold"
}
</nowiki></pre>

Note: Currently the only Action that is supported is HEAT::HA::Restarter

Then you need to call this from in your vm:
/opt/aws/bin/cfn-push-stats --watch [[MyOwnAlarm]] [other args]

To see this all together look at the [HA template](https://github.com/heat-api/heat/blob/master/templates/WordPress_Single_Instance_With_HA.template)

== [[CloudWatch]] API ==

An AWS-compatible API to the heat [[CloudWatch]] alarms and metrics is in-progress. Not all AWS actions are supported (yet), but you can do the following:

* List Alarms
* List Metrics (related to alarms only, generic Metric datapoints not yet supported)
* Create Metric Datapoints (similar to current cfn-push-stats functionality but authenticated)
* Set Alarm state (temporarily, useful for testing alarm actions)

Status of API actions as they are implemented will be tracked in the [[CloudWatch|API roadmap page]](https://github.com/heat-api/heat/wiki/Roadmap-Feature:-cloudwatch-api)

You can use the Cloudwatch API by doing the following:

<pre><nowiki>
heat-api-cloudwatch -d &
tail -f /var/log/heat/api-cloudwatch.log
</nowiki></pre>

Note that it is not currently necessary to run heat-api-cloudwatch for HA and autoscaling to work correctly - instances still report Cloudwatch metric data via the metadata server (for the time being at least..)

== [[CloudWatch]] Client "**heat-watch**" ==

A client has been created to demonstrate the [[CloudWatch]] API - it is **heat-watch**

Usage examples:

List Alarms:

<pre><nowiki>
heat-watch describe
</nowiki></pre>

List Metrics Datapoints:

<pre><nowiki>
heat-watch metric-list
</nowiki></pre>

Create Metric Datapoints:

<pre><nowiki>
heat-watch metric-put-data HttpFailureAlarm system/linux ServiceFailure Count 1
</nowiki></pre>

Set Alarm state:

<pre><nowiki>
heat-watch -d set-state HttpFailureAlarm ALARM
</nowiki></pre>

@@ Line 25: / Line 25: @@
 /opt/aws/bin/cfn-push-stats --watch [[MyOwnAlarm]] [other args]
-To see this all together look at the [https://github.com/heat-api/heat/blob/master/templates/WordPress_Single_Instance_With_HA.template HA template]
+To see this all together look at the [https://raw.github.com/openstack/heat-templates/master/cfn/WordPress_Single_Instance_With_HA.template HA template]
 == [[CloudWatch]] API ==

← Older revision		Revision as of 07:58, 14 May 2013
Line 1:		Line 1:

−	Note: the current cloud watch implementation is ~~incomplete (it's only sufficient~~ for [HA~~](https://github~~.~~com/heat-api/heat/wiki/Using-HA)). But should~~ be ~~easy~~ to ~~make more generally useful~~.	+	Note: the current cloud watch implementation is a minimal implementation, and does not provide feature parity with AWS Cloudwatch. It is primarily required to enable metric collection for HA and Autoscaling functionality, but can also be used to configure user defined alarms, as outlined below. This feature will be deprecated or removed during the Havana cycle as we move to using Ceilometer as a metric/alarm service instead.

	To use cloud watch you need the following in your template:		To use cloud watch you need the following in your template:

← Older revision		Revision as of 23:30, 17 February 2013
Line 1:		Line 1:
−	~~__NOTOC__~~	+
	Note: the current cloud watch implementation is incomplete (it's only sufficient for [HA](https://github.com/heat-api/heat/wiki/Using-HA)). But should be easy to make more generally useful.		Note: the current cloud watch implementation is incomplete (it's only sufficient for [HA](https://github.com/heat-api/heat/wiki/Using-HA)). But should be easy to make more generally useful.