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.
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.
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 > 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 in New Relic One 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 |
|---|---|
| The AWS resource ARN. |
| The ARN of the AWS Health event itself. |
| The AWS affected region. |
| Number of affected resources. Auto-generated metric that can be used to define New Relic alert conditions. |
| Detailed description of the event. |
| AWS Health category: Issue, ScheduledChange, AccountNotification, Investigation. |
| A list of unique identifiers for event types. For example, |
| The AWS services associated with the event. For example, EC2, RDS. |
| The AWS health event status: |
| Date and time the event began. |
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'Inventory data
EOL NOTICE
After March 2022, we're discontinuing support for several capabilities, including inventory data for cloud integrations. For more details, including how you can easily prepare for this transition, see our Explorers Hub post.
Inventory data provides information about active AWS Health events. New Relic's AWS Health integration generates three types of entities, each of which have the same inventory data:
aws/health/issue/aws/health/scheduled-change/aws/health/notification/
Name | Description |
|---|---|
| The AWS Availability Zone of the event. |
| The ARNs of the entities that are affected by the event. Entities can refer to individual customer resources, groups of customer resources, or any other construct, depending on the AWS service. |
| The AWS region of the affected entities. |
| The unique identifier for the event. |
| The Personal Health Dashboard region. |
| The most recent description of the event. |
| The date and time that the event ended. |
| The category of the event type. Possible values are |
| The unique identifier for the event type. |
| The AWS service that is affected by the event. |
| The date and time that the event began. |
| The most recent status of the event. Examples of possible values are |