ex_aws_cloudwatch v2.0.4 ExAws.Cloudwatch
Operations on AWS CloudWatch
AWS CloudWatch provides a reliable, scalable, and flexible monitoring solution for your AWS resources.
More information:
Link to this section Summary
Functions
Deletes the specified alarms
Deletes all dashboards that you specify
Retrieves the history for the specified alarm
Retrieves the specified alarms
Retrieves the alarms for the specified metric
Disables the actions for the specified alarms
Enables the actions for the specified alarms
Displays the details of the dashboard that you specify
Gets statistics for the specified metric
Returns a list of the dashboards for your account
List the specified metrics
Creates a dashboard if it does not already exist, or updates an existing dashboard
Creates or updates an alarm and associates it with the specified metric
Publishes metric data points to Amazon CloudWatch
Link to this section Types
action()
describe_alarm_history_opts()
describe_alarm_history_opts() :: [
alarm_name: binary(),
history_item_type: binary(),
start_date: %DateTime{
calendar: term(),
day: term(),
hour: term(),
microsecond: term(),
minute: term(),
month: term(),
second: term(),
std_offset: term(),
time_zone: term(),
utc_offset: term(),
year: term(),
zone_abbr: term()
},
end_date: %DateTime{
calendar: term(),
day: term(),
hour: term(),
microsecond: term(),
minute: term(),
month: term(),
second: term(),
std_offset: term(),
time_zone: term(),
utc_offset: term(),
year: term(),
zone_abbr: term()
},
max_records: integer(),
next_token: binary()
]
describe_alarm_history_opts() :: [ alarm_name: binary(), history_item_type: binary(), start_date: %DateTime{ calendar: term(), day: term(), hour: term(), microsecond: term(), minute: term(), month: term(), second: term(), std_offset: term(), time_zone: term(), utc_offset: term(), year: term(), zone_abbr: term() }, end_date: %DateTime{ calendar: term(), day: term(), hour: term(), microsecond: term(), minute: term(), month: term(), second: term(), std_offset: term(), time_zone: term(), utc_offset: term(), year: term(), zone_abbr: term() }, max_records: integer(), next_token: binary() ]
describe_alarm_opts()
describe_alarms_for_metric_opts()
dimension()
get_dashboard_opts()
get_dashboard_opts() :: [{:dashboard_name, binary()}]
get_dashboard_opts() :: [{:dashboard_name, binary()}]
get_metric_statistics_opts()
list_dashboards_opts()
list_metrics_opts()
metric_datum()
metric_datum() :: [
counts: [non_neg_integer()],
dimensions: [dimension(), ...],
metric_name: binary(),
statistic_values: statistic_set(),
storage_resolution: integer(),
timestamp: DateTime.t(),
unit: binary(),
value: number(),
values: [number()]
]
metric_datum() :: [ counts: [non_neg_integer()], dimensions: [dimension(), ...], metric_name: binary(), statistic_values: statistic_set(), storage_resolution: integer(), timestamp: DateTime.t(), unit: binary(), value: number(), values: [number()] ]
param()
put_metric_alarm_opts()
put_metric_alarm_opts() :: [
actions_enabled: boolean(),
alarm_actions: [binary(), ...],
alarm_description: binary(),
dimensions: [dimension(), ...],
evaluate_low_sample_count_percentile: binary(),
extended_statistic: binary(),
insufficient_data_actions: [binary(), ...],
ok_actions: [binary(), ...],
treat_missing_data: binary(),
unit: binary()
]
put_metric_alarm_opts() :: [ actions_enabled: boolean(), alarm_actions: [binary(), ...], alarm_description: binary(), dimensions: [dimension(), ...], evaluate_low_sample_count_percentile: binary(), extended_statistic: binary(), insufficient_data_actions: [binary(), ...], ok_actions: [binary(), ...], treat_missing_data: binary(), unit: binary() ]
statistic_set()
Link to this section Functions
delete_alarms(alarm_names)
delete_alarms(alarm_names :: [binary(), ...]) :: ExAws.Operation.Query.t()
delete_alarms(alarm_names :: [binary(), ...]) :: ExAws.Operation.Query.t()
Deletes the specified alarms.
You may specify up to 100 alarms to delete. In the event of an error, no alarms are deleted.
Examples:
iex> ExAws.Cloudwatch.delete_alarms(["alarm1", "alarm2"])
%ExAws.Operation.Query{action: :delete_alarms,
params: %{"Action" => "DeleteAlarms", "AlarmNames.member.1" => "alarm1",
"AlarmNames.member.2" => "alarm2", "Version" => "2010-08-01"},
parser: &ExAws.Cloudwatch.Parsers.parse/2, path: "/", service: :monitoring}
delete_dashboards(dashboard_names)
delete_dashboards(dashboard_names :: [binary(), ...]) ::
ExAws.Operation.Query.t()
delete_dashboards(dashboard_names :: [binary(), ...]) :: ExAws.Operation.Query.t()
Deletes all dashboards that you specify.
You may specify up to 100 dashboards to delete. If there is an error, no dashboards are deleted.
Examples:
iex> ExAws.Cloudwatch.delete_dashboards(["dash1", "dash2"])
%ExAws.Operation.Query{action: :delete_dashboards,
params: %{"Action" => "DeleteDashboards", "DashboardNames.member.1" => "dash1",
"DashboardNames.member.2" => "dash2", "Version" => "2010-08-01"},
parser: &ExAws.Cloudwatch.Parsers.parse/2, path: "/", service: :monitoring}
describe_alarm_history(opts \\ [])
describe_alarm_history(opts :: describe_alarm_history_opts()) ::
ExAws.Operation.Query.t()
describe_alarm_history(opts :: describe_alarm_history_opts()) :: ExAws.Operation.Query.t()
Retrieves the history for the specified alarm.
You can filter the results by date range or item type. If an alarm name is not specified, the histories for all alarms are returned.
CloudWatch retains the history of an alarm even if you delete the alarm.
Examples:
iex> ExAws.Cloudwatch.describe_alarm_history()
%ExAws.Operation.Query{action: :describe_alarm_history,
params: %{"Action" => "DescribeAlarmHistory", "Version" => "2010-08-01"},
parser: &ExAws.Cloudwatch.Parsers.parse/2, path: "/", service: :monitoring}
describe_alarms(opts \\ [])
describe_alarms(opts :: describe_alarm_opts()) :: ExAws.Operation.Query.t()
describe_alarms(opts :: describe_alarm_opts()) :: ExAws.Operation.Query.t()
Retrieves the specified alarms.
If no alarms are specified, all alarms are returned. Alarms can be retrieved by using only a prefix for the alarm name, the alarm state, or a prefix for any action.
Examples:
iex> ExAws.Cloudwatch.describe_alarms()
%ExAws.Operation.Query{action: :describe_alarms,
params: %{"Action" => "DescribeAlarms", "Version" => "2010-08-01"},
parser: &ExAws.Cloudwatch.Parsers.parse/2, path: "/", service: :monitoring}
describe_alarms_for_metric(metric_name, namespace, opts \\ [])
describe_alarms_for_metric(
metric_name :: binary(),
namespace :: binary(),
opts :: describe_alarms_for_metric_opts()
) :: ExAws.Operation.Query.t()
describe_alarms_for_metric( metric_name :: binary(), namespace :: binary(), opts :: describe_alarms_for_metric_opts() ) :: ExAws.Operation.Query.t()
Retrieves the alarms for the specified metric.
To filter the results, specify a statistic, period, or unit.
Examples:
iex> ExAws.Cloudwatch.describe_alarms_for_metric(
...> "metric_name",
...> "namespace")
%ExAws.Operation.Query{action: :describe_alarms_for_metric,
params: %{"Action" => "DescribeAlarmsForMetric", "MetricName" => "metric_name",
"Namespace" => "namespace", "Version" => "2010-08-01"},
parser: &ExAws.Cloudwatch.Parsers.parse/2, path: "/", service: :monitoring}
disable_alarm_actions(alarm_names)
disable_alarm_actions(alarm_names :: [binary(), ...]) ::
ExAws.Operation.Query.t()
disable_alarm_actions(alarm_names :: [binary(), ...]) :: ExAws.Operation.Query.t()
Disables the actions for the specified alarms.
When an alarm's actions are disabled, the alarm actions do not execute when the alarm state changes.
Examples:
iex> ExAws.Cloudwatch.disable_alarm_actions(alarm_names: ["alarm1", "alarm2"])
%ExAws.Operation.Query{action: :disable_alarm_actions,
params: %{"Action" => "DisableAlarmActions",
"AlarmNames.member.AlarmNames.1" => "alarm1",
"AlarmNames.member.AlarmNames.2" => "alarm2", "Version" => "2010-08-01"},
parser: &ExAws.Cloudwatch.Parsers.parse/2, path: "/", service: :monitoring}
enable_alarm_actions(alarm_names)
enable_alarm_actions(alarm_names :: [binary(), ...]) ::
ExAws.Operation.Query.t()
enable_alarm_actions(alarm_names :: [binary(), ...]) :: ExAws.Operation.Query.t()
Enables the actions for the specified alarms.
Examples:
iex> ExAws.Cloudwatch.enable_alarm_actions(alarm_names: ["alarm1", "alarm2"])
%ExAws.Operation.Query{action: :enable_alarm_actions,
params: %{"Action" => "EnableAlarmActions",
"AlarmNames.member.AlarmNames.1" => "alarm1",
"AlarmNames.member.AlarmNames.2" => "alarm2", "Version" => "2010-08-01"},
parser: &ExAws.Cloudwatch.Parsers.parse/2, path: "/", service: :monitoring}
get_dashboard(opts \\ [])
get_dashboard(opts :: get_dashboard_opts()) :: ExAws.Operation.Query.t()
get_dashboard(opts :: get_dashboard_opts()) :: ExAws.Operation.Query.t()
Displays the details of the dashboard that you specify.
To copy an existing dashboard, use get_dashboard/0, and then use the data returned within dashboard_body as the template for the new dashboard when you call put_dashboard/2 to create the copy.
Examples:
iex> ExAws.Cloudwatch.get_dashboard([dashboard_name: "dashboard_name"])
%ExAws.Operation.Query{action: :get_dashboard,
params: %{"Action" => "GetDashboard", "DashboardName" => "dashboard_name",
"Version" => "2010-08-01"},
parser: &ExAws.Cloudwatch.Parsers.parse/2, path: "/", service: :monitoring}
get_metric_statistics(namespace, metric_name, start_time, end_time, period, opts \\ [])
get_metric_statistics(
namespace :: binary(),
metric_name :: binary(),
start_time :: %DateTime{
calendar: term(),
day: term(),
hour: term(),
microsecond: term(),
minute: term(),
month: term(),
second: term(),
std_offset: term(),
time_zone: term(),
utc_offset: term(),
year: term(),
zone_abbr: term()
},
end_time :: %DateTime{
calendar: term(),
day: term(),
hour: term(),
microsecond: term(),
minute: term(),
month: term(),
second: term(),
std_offset: term(),
time_zone: term(),
utc_offset: term(),
year: term(),
zone_abbr: term()
},
period :: integer(),
opts :: get_metric_statistics_opts()
) :: ExAws.Operation.Query.t()
get_metric_statistics( namespace :: binary(), metric_name :: binary(), start_time :: %DateTime{ calendar: term(), day: term(), hour: term(), microsecond: term(), minute: term(), month: term(), second: term(), std_offset: term(), time_zone: term(), utc_offset: term(), year: term(), zone_abbr: term() }, end_time :: %DateTime{ calendar: term(), day: term(), hour: term(), microsecond: term(), minute: term(), month: term(), second: term(), std_offset: term(), time_zone: term(), utc_offset: term(), year: term(), zone_abbr: term() }, period :: integer(), opts :: get_metric_statistics_opts() ) :: ExAws.Operation.Query.t()
Gets statistics for the specified metric.
The maximum number of data points returned from a single call is 1,440. If you request more than 1,440 data points, CloudWatch returns an error. To reduce the number of data points, you can narrow the specified time range and make multiple requests across adjacent time ranges, or you can increase the specified period. Data points are not returned in chronological order.
CloudWatch aggregates data points based on the length of the period that you specify. For example, if you request statistics with a one-hour period, CloudWatch aggregates all data points with time stamps that fall within each one-hour period. Therefore, the number of values aggregated by CloudWatch is larger than the number of data points returned.
CloudWatch needs raw data points to calculate percentile statistics. If you publish data using a statistic set instead, you can only retrieve percentile statistics for this data if one of the following conditions is true:
The sample_count value of the statistic set is 1. The Min and the Max values of the statistic set are equal.
Amazon CloudWatch retains metric data as follows:
- Data points with a period of less than 60 seconds are available for 3 hours. These data points are high-resolution metrics and are available only for custom metrics that have been defined with a StorageResolution of 1.
- Data points with a period of 60 seconds (1-minute) are available for 15 days.
- Data points with a period of 300 seconds (5-minute) are available for 63 days.
- Data points with a period of 3600 seconds (1 hour) are available for 455 days (15 months).
- Data points that are initially published with a shorter period are aggregated together for long-term storage. For example, if you collect data using a period of 1 minute, the data remains available for 15 days with 1-minute resolution. After 15 days, this data is still available, but is aggregated and retrievable only with a resolution of 5 minutes. After 63 days, the data is further aggregated and is available with a resolution of 1 hour.
CloudWatch started retaining 5-minute and 1-hour metric data as of July 9, 2016.
Examples:
iex> {:ok, start_time, 0} = DateTime.from_iso8601("2017-01-23T23:50:07Z")
iex> {:ok, end_time, 0} = DateTime.from_iso8601("2017-02-23T23:50:07Z")
iex> ExAws.Cloudwatch.get_metric_statistics("namespace", "metric_name", start_time, end_time, 1)
%ExAws.Operation.Query{action: :get_metric_statistics,
params: %{"Action" => "GetMetricStatistics",
"EndTime" => "2017-02-23T23:50:07Z", "MetricName" => "metric_name",
"Namespace" => "namespace", "Period" => 1,
"StartTime" => "2017-01-23T23:50:07Z", "Version" => "2010-08-01"},
parser: &ExAws.Cloudwatch.Parsers.parse/2, path: "/", service: :monitoring}
list_dashboards(opts \\ [])
list_dashboards(opts :: list_dashboards_opts()) :: ExAws.Operation.Query.t()
list_dashboards(opts :: list_dashboards_opts()) :: ExAws.Operation.Query.t()
Returns a list of the dashboards for your account.
If you include dashboard_name_prefix, only those dashboards with names starting with the prefix are listed. Otherwise, all dashboards in your account are listed.
Examples:
iex> ExAws.Cloudwatch.list_dashboards()
%ExAws.Operation.Query{action: :list_dashboards,
params: %{"Action" => "ListDashboards", "Version" => "2010-08-01"},
parser: &ExAws.Cloudwatch.Parsers.parse/2, path: "/", service: :monitoring}
list_metrics(opts \\ [])
list_metrics(opts :: list_metrics_opts()) :: ExAws.Operation.Query.t()
list_metrics(opts :: list_metrics_opts()) :: ExAws.Operation.Query.t()
List the specified metrics.
You can use the returned metrics with get_metric_statistics/1
to obtain
statistical data. Up to 500 results are returned for any one call.
To retrieve additional results, use the returned token with subsequent
calls.
After you create a metric, allow up to fifteen minutes before the metric
appears. Statistics about the metric, however, are available sooner
using get_metric_statistics/1
Examples:
iex> ExAws.Cloudwatch.list_metrics(
...> [namespace: "namespace",
...> metric_name: "metric_name"])
%ExAws.Operation.Query{action: :list_metrics,
params: %{"Action" => "ListMetrics", "MetricName" => "metric_name",
"Namespace" => "namespace", "Version" => "2010-08-01"},
parser: &ExAws.Cloudwatch.Parsers.parse/2, path: "/", service: :monitoring}
put_dashboard(dashboard_name, dashboard_body)
put_dashboard(dashboard_name :: binary(), dashboard_body :: binary()) ::
ExAws.Operation.Query.t()
put_dashboard(dashboard_name :: binary(), dashboard_body :: binary()) :: ExAws.Operation.Query.t()
Creates a dashboard if it does not already exist, or updates an existing dashboard.
If you update a dashboard, the entire contents are replaced with what you specify here.
You can have up to 500 dashboards per account. All dashboards in your account are global, not region-specific.
A simple way to create a dashboard using put_dashboard/2 is to copy an
existing dashboard. To copy an existing dashboard using the console, you
can load the dashboard and then use the View/edit source command in the
Actions menu to display the JSON block for that dashboard. Another way to
copy a dashboard is to use get_dashboard/1
, and then use the data
returned within dashboard_body as the template for the new dashboard
when you call put_dashboard/2
.
When you create a dashboard with put_dashboard/2 , a good practice is to add a text widget at the top of the dashboard with a message that the dashboard was created by script and should not be changed in the console. This message could also point console users to the location of the dashboard_body script or the CloudFormation template used to create the dashboard.
Examples:
iex> ExAws.Cloudwatch.put_dashboard("dashboard_name", "dashboard_body")
%ExAws.Operation.Query{action: :put_dashboard,
params: %{"Action" => "PutDashboard", "DashboardBody" => "dashboard_body",
"DashboardName" => "dashboard_name", "Version" => "2010-08-01"},
parser: &ExAws.Cloudwatch.Parsers.parse/2, path: "/", service: :monitoring}
put_metric_alarm(alarm_name, comparison_operator, evaluation_periods, metric_name, namespace, period, threshold, statistic, opts \\ [])
put_metric_alarm(
alarm_name :: binary(),
comparison_operator :: binary(),
evaluation_periods :: integer(),
metric_name :: binary(),
namespace :: binary(),
period :: integer(),
threshold :: float(),
statistic :: binary(),
opts :: put_metric_alarm_opts()
) :: ExAws.Operation.Query.t()
put_metric_alarm( alarm_name :: binary(), comparison_operator :: binary(), evaluation_periods :: integer(), metric_name :: binary(), namespace :: binary(), period :: integer(), threshold :: float(), statistic :: binary(), opts :: put_metric_alarm_opts() ) :: ExAws.Operation.Query.t()
Creates or updates an alarm and associates it with the specified metric.
Optionally, this operation can associate one or more Amazon SNS resources with the alarm.
When this operation creates an alarm, the alarm state is immediately set to INSUFFICIENT_DATA . The alarm is evaluated and its state is set appropriately. Any actions associated with the state are then executed.
When you update an existing alarm, its state is left unchanged, but the update completely overwrites the previous configuration of the alarm.
If you are an IAM user, you must have Amazon EC2 permissions for some operations:
ec2:DescribeInstanceStatus and ec2:DescribeInstances for all alarms on EC2 instance status metrics ec2:StopInstances for alarms with stop actions ec2:TerminateInstances for alarms with terminate actions ec2:DescribeInstanceRecoveryAttribute and ec2:RecoverInstances for alarms with recover actions If you have read/write permissions for Amazon CloudWatch but not for Amazon EC2, you can still create an alarm, but the stop or terminate actions are not performed. However, if you are later granted the required permissions, the alarm actions that you created earlier are performed.
If you are using an IAM role (for example, an EC2 instance profile), you cannot stop or terminate the instance using alarm actions. However, you can still see the alarm state and perform any other actions such as Amazon SNS notifications or Auto Scaling policies.
If you are using temporary security credentials granted using AWS STS, you cannot stop or terminate an EC2 instance using alarm actions.
You must create at least one stop, terminate, or reboot alarm using either the Amazon EC2 or CloudWatch consoles to create the EC2ActionsAccess IAM role. After this IAM role is created, you can create stop, terminate, or reboot alarms using a command-line interface or API.
Examples:
iex> ExAws.Cloudwatch.put_metric_alarm(
...> "alarm_name",
...> "greater_than",
...> 1,
...> "metric_name",
...> "namespace",
...> 2,
...> 3.1,
...> "sum")
%ExAws.Operation.Query{action: :put_metric_alarm,
params: %{"Action" => "PutMetricAlarm", "AlarmName" => "alarm_name",
"ComparisonOperator" => "greater_than", "EvaluationPeriods" => 1,
"MetricName" => "metric_name", "Namespace" => "namespace", "Period" => 2,
"Statistic" => "sum", "Threshold" => 3.1, "Version" => "2010-08-01"},
parser: &ExAws.Cloudwatch.Parsers.parse/2, path: "/", service: :monitoring}
put_metric_data(metric_data, namespace)
put_metric_data(metric_data :: [metric_datum(), ...], namespace :: binary()) ::
ExAws.Operation.Query.t()
put_metric_data(metric_data :: [metric_datum(), ...], namespace :: binary()) :: ExAws.Operation.Query.t()
Publishes metric data points to Amazon CloudWatch.
CloudWatch associates the data points with the specified metric. If the specified metric does not exist, CloudWatch creates the metric. When CloudWatch creates a metric, it can take up to fifteen minutes for the metric to appear in calls to ListMetrics .
Each PutMetricData request is limited to 40 KB in size for HTTP POST requests.
Although the Value parameter accepts numbers of type Double, CloudWatch rejects values that are either too small or too large. Values must be in the range of 8.515920e-109 to 1.174271e+108 (Base 10) or 2e-360 to 2e360 (Base 2). In addition, special values (for example, NaN, +Infinity, -Infinity) are not supported.
You can use up to 10 dimensions per metric to further clarify what data the metric collects. For more information about specifying dimensions, see Publishing Metrics in the Amazon CloudWatch User Guide.
Data points with time stamps from 24 hours ago or longer can take at least 48 hours to become available for GetMetricStatistics from the time they are submitted.
CloudWatch needs raw data points to calculate percentile statistics. If you publish data using a statistic set instead, you can only retrieve percentile statistics for this data if one of the following conditions is true:
- The SampleCount value of the statistic set is 1
- The Min and the Max values of the statistic set are equal
Example
iex> metric_data = [
...> [metric_name: "My Metric Name", value: 1.0],
...> [metric_name: "My Metric Name", value: 1.5],
...> [metric_name: "My Metric Name", value: 2.0],
...> ]
iex> ExAws.Cloudwatch.put_metric_data(metric_data, "My Name Space")
%ExAws.Operation.Query{
action: :put_metric_data,
params: %{
"Action" => "PutMetricData",
"MetricData.member.1.MetricName" => "My Metric Name",
"MetricData.member.1.Value" => 1.0,
"MetricData.member.2.MetricName" => "My Metric Name",
"MetricData.member.2.Value" => 1.5,
"MetricData.member.3.MetricName" => "My Metric Name",
"MetricData.member.3.Value" => 2.0,
"Namespace" => "My Name Space",
"Version" => "2010-08-01",
},
parser: &ExAws.Cloudwatch.Parsers.parse/2,
path: "/",
service: :monitoring,
}