AWS System Manager Distributor

Install New Relic's infrastructure agent on your AWS EC2 instances with a single click through our integration for AWS System Manager Distributor. This document explains the integrations features, how to activate it, and what data can be reported.

Features

Collect and send telemetry data to New Relic from diverse AWS instances with a single click. New Relic's AWS System Manager Distributor integration installs our infrastructure agent on your AWS instances and allows you to quickly monitor your services, query incoming data, and build dashboards so you can observe your system at a glance.

Prerequisites

Complete the setup recommended by AWS at AWS Systems Manager documentation to configure roles, user accounts, permissions, and initial resources.

Activate integration

You can use the AWS Systems Manager console to install or update the New Relic infrastructure agent distributor package one time or you can set an install schedule.

• When you configure a one time installation, the Distributor package uses the AWS Systems Manager Run Command, a capability of AWS Systems Manager, to perform the installation.
• When you schedule package installation or update, Distributor uses AWS Systems Manager State Manager to install or update.

New Relic also provides automated process for monitoring of EC2 and can be found here

Install or update the agent

1. Open the AWS Systems Manager console. In the navigation pane, choose Distributor, select Third party and select the New Relic infrastructure agent tile.

2. Select the installation mode. You can install or update the New Relic infrastructure agent package one time or schedule the installation. For detailed information on installing the Distributor packages, see AWS Systems Manager Distributor documentation.

3. For Action, choose Install.

4. For Installation type, choose either Uninstall and reinstall: The package is completely uninstalled, and then reinstalled. The New Relic agent is unavailable until the reinstallation is complete In-place update. The application remains available throughout the update process.

5. For Additional Arguments, paste the code featured below. Be sure to replace YOUR_NEWRELIC_LICENSE_KEY with your New Relic API Key.

   {
     "SSM_NR_LICENSE_KEY" : "YOUR_NEWRELIC_LICENSE_KEY"
   }

   コピー

   Sample variables can also be specified in Additional Arguments as shown below:

   { "SSM_NR_LICENSE_KEY" : "YOUR_NEWRELIC_LICENSE_KEY",
    "SSM_NRIA_METRICS_NETWORK_SAMPLE_RATE" : "SOME_INTEGER_VALUE",
    "SSM_NRIA_METRICS_PROCESS_SAMPLE_RATE" : "SOME_INTEGER_VALUE",
    "SSM_NRIA_METRICS_STORAGE_SAMPLE_RATE" : "SOME_INTEGER_VALUE",
    "SSM_NRIA_METRICS_SYSTEM_SAMPLE_RATE" : "SOME_INTEGER_VALUE", 
    "SSM_NRIA_METRICS_NFS_SAMPLE_RATE" : "SOME_INTEGER_VALUE" }

   コピー

   If not specified, they will take the default values.

6. In the Targets section, choose the managed nodes on which you want to run this operation by specifying tags, selecting instances or devices manually, or by specifying a resource group. If you don't see a managed node in the list, see these AWS docs.

7. For Rate Control for Concurrency, specify either a number or a percentage of targets on which to run the command at the same time.

   ヒント

   If you selected targets by specifying tags or resource groups and you aren't certain how many managed nodes are targeted, then restrict the number of targets that can run the document at the same time by specifying a percentage.

8. For Error threshold, specify when to stop running the command on other targets after it fails on either a number or a percentage of managed nodes. For example, if you specify three errors, then Systems Manager stops sending the command when the fourth error is received. Managed nodes still processing the command might also send errors.

9. Verify the installation. After you run the installation, check the progress in the Command status area. When you see the Success status it means the installation was successful.

10. Explore your app's data in the our UI.

Configuration and polling

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

Default polling information for the AWS integrations:

• New Relic polling interval: 5 minutes
• Amazon CloudWatch data interval: 1 minute or 5 minutes

Find and use data

After you installed the New Relic infrastructure agent, you can adjust and tune the data flow coming from your instances.

To read more about how to find your data, see our Introduction to AWS integrations.