New Relic Infrastructure is an agent which provides flexible, dynamic server monitoring. Infrastructure empowers modern operations teams to make intelligent decisions about complex systems, from a physical datacenter to thousands of Amazon Elastic Compute Cloud (Amazon EC2) or Microsoft Azure instances.
Real-time metrics and powerful analytics reduce your mean-time-to-resolution (MTTR) by connecting changes in host performance to changes in your configuration. Hosts are automatically added and removed from the interface as they are created and destroyed, and a powerful Events page lets you see every change.
The Infrastructure UI covers your entire architecture:
- Unified performance charts combine all your hosts into a single view.
- Filter sets let you isolate the components most relevant to you, such as a particular Amazon EC2 region or a custom attribute identifying a dev team.
- Inventory lets you track and search every package on every host.
- Integrated alerting ensures you are notified about problems relevant to you or your team before they become critical situations.
Installation: Install and configure Infrastructure
There are three ways to install Infrastructure: default, assisted, and manual install. For most users, we recommend the default process. The default process uses a package manager, and requires no additional configuration.
The default New Relic Infrastructure install requires only three steps:
- Create a config file with your license key.
- Download the agent.
- Run the install script.
You can also customize your installation process with the assisted install, or a full manual installation:
- Assisted install
If you opt for an assisted install for Linux or Windows, we provide you with an installation script and a configuration file, which you can edit to suit your preferences. With this method you are able to change the location of the PID, log, and config files, among other values, or set the agent running mode.
Assisted install is not supported.
- Manual install
- Place the log and config files in the correct folders.
- Provide the correct parameterized configuration values.
- Ensure that the agent has all the permissions to execute.
Manual install is not supported.
The agent has minimal performance impact. If needed, you can manually start, stop, restart, or check the agent's status.
Integrations for more visibility
Infrastructure integrations give you more visibility into popular systems, including Amazon Web Services (AWS), Azure, MySQL, and Cassandra. You can also use open-source integrations, such as Collectd, Memcached, and more; or make your own custom integrations using the Integrations SDK. After you connect your integrations to Infrastructure, your alerts and dashboards automatically scale to provide you with complete coverage.
With the AWS integrations, you can monitor your AWS accounts, giving you a view of your entire architecture in one place. The AWS integrations are available depending on your subscription level. For example:
- All Infrastructure accounts: New Relic automatically connects your EC2 data to Infrastructure agent data, to provide enhanced filtering and grouping in the Infrastructure UI.
- Infrastructure Pro accounts: With Infrastructure Pro, you gain unprecedented understanding of AWS usage by using New Relic Insights with your AWS integrations.
Filter sets: Slice and dice your hosts
Filter sets allow you to organize your hosts based on criteria that matter most to you. You can filter your hosts by any Infrastructure attribute, such as geographic location, hostname, or Linux distribution.
You can also filter on Amazon EC2 attributes, such as AWS region or instance type. In addition, you can add custom attributes to define unique metadata, such as what team manages the host or the services running on that host.
Workflow: Correlate metrics with change events
Reduce your mean-time-to-resolution (MTTR) with Infrastructure's unique event-based workflow.
Here's an example of solving a specific app performance issue:
- You're notified of a slowdown in your login service by an Infrastructure alert, or by noticing one of your Filter Sets is having performance issues.
- You click through to the Hosts page to view performance information for a custom filter set labeled Login Service, and you see that CPU usage has spiked.
- Above the Hosts CPU chart, the events feed shows that a package was modified right before CPU usage spiked. By clicking on those packages, you drill down to the relevant time on the Events page.
- From the Events page, it appears that a particular package version is causing the issue.
- Switching to the Inventory page, you search your infrastructure for servers running that particular package version and downgrade them to a more stable release.
For more information, check out New Relic University’s tutorial Improving Performance with New Relic Infrastructure. Or, go directly to the full online course Getting started with Infrastructure.
Other key features
New Relic Infrastructure also includes these features:
|New Relic Insights support||
With access to New Relic Insights, you can:
|New Relic APM integration||
If you have New Relic APM installed on Infrastructure-monitored hosts, APM data will show up in Infrastructure. This gives you the ability to troubleshoot performance issues, no matter where the issue occurs: server-side or application-side.
|Inventory search||The Inventory page allows you to search across your entire infrastructure, to find exactly which of your hosts contain particular packages, config files, or startup scripts. For example, you could search for hosts containing versions of OpenSSL affected by the Heartbleed security bug.|
|Events log||Infrastructure Events track config changes, restarts, SSH sessions, and other key event changes to each of your hosts. A real-time feed gives you a changelog for your entire infrastructure.|
|Near real-time data||Infrastructure securely collects and displays your data in five seconds, so your monitoring never lags behind reality.|
|Alert conditions created directly from relevant charts||
You can create, view, or update alert settings directly from the relevant Infrastructure chart. For example, if you want to be notified when New Relic has stopped receiving data from an Infrastructure agent, you can create a host not reporting alert condition.
The associated alert policy respects your current filter set, so you can create alert conditions tailored to specific teams, services, or components in your environment. New Relic Alerts automatically adds new instances to matching alert conditions, so you don't need to manually tweak existing alert policies.
|Other UI features||