AWS Health monitoring integration

New Relic infrastructure integrations include an integration for reporting your AWS Health data to New Relic. This document explains how to activate this integration and describes the data that can be reported.

Features

This integration collects information from AWS Health about events that can affect the AWS resources and services globally or in a specific account. This data can help you anticipate potential application outages.

AWS Health reports three types of events:

Open issues: Shows issues that might affect your AWS infrastructure.
Scheduled changes: Informs you in advance of scheduled activities that might have an impact on AWS services and resources.
Notifications: Provides additional information.

Health events will be linked to existing entities for AWS EC2 resources and will inherit all the entity metadata available such as region, availabilityZone, resource tags and more.

To see the complete list of attributes available use the keyset function:

FROM AwsHealthNotification SELECT keyset()

Requirements

This integration is available only for AWS customers who have a Business or Enterprise support plan, because this is a requirement for using the AWS Health API.

Activate integration

To enable this integration follow standard procedures to Connect AWS services to New Relic.

Dica

Only health events that occurred after AWS Health Integration was activated will be collected. Health events that have occurred in the past will not be collected.

Configuration and polling

You can change the polling frequency and filter data using configuration options.

Default polling information for the AWS Health integration:

New Relic polling interval: 5 minutes

Explore integration data

To use this integration's data:

Go to one.newrelic.com > All capabilities > Infrastructure > AWS.
Select any of the available AWS Health integration links.
To view a timeline when an AWS health event is created, modified, or deleted, use the Events page.

Events monitoring and alerts

AWS Health events are ingested as AwsHealthNotification events. You can query, create widgets, and define NRQL alert policies based on these events.

The following table shows the main attributes available for AwsHealthNotification events:

Event attribute	Description
`affectedEntityArn`	The AWS resource ARN.
`arn`	The ARN of the AWS health event itself.
`affectedRegion`	The AWS affected region.
`affectedResources`	Number of affected resources. Auto-generated metric that can be used to define New Relic conditions.
`description`	Detailed description of the event.
`eventTypeCategory`	AWS Health category: Issue, ScheduledChange, AccountNotification, Investigation.
`eventTypeCode`	A list of unique identifiers for event types. For example,`AWS_EC2_SYSTEM_MAINTENANCE_EVENT` or `AWS_RDS_MAINTENANCE_SCHEDULED`.
`service`	The AWS services associated with the event. For example, EC2, RDS.
`statusCode`	The AWS health event status: `Open`, `Closed`, `Upcoming`.
`startTime`	The date and time that the event began (in string format).
`startTimestamp`	The epoch timestamp (in seconds) for event began.
`endTime`	The date and time for event resolution (in string format).
`endTimestamp`	The epoch timestamp (in seconds) for event resolution.
`lastUpdatedTime`	The date and time for the last event update received (in string format).
`lastUpdatedTimestamp`	The epoch timestamp (in seconds) for the last event update received.

NRQL alert conditions can be defined to receive notifications when health events are reported by AWS.

For example, the following query monitors any open issues on EC2 by resource:

SELECT uniqueCount(affectedEntityArn) FROM AwsHealthNotification where statusCode = 'open' and eventTypeCategory = 'Issue' and service = 'EC2'