New Relic Servers is no longer available. For your infrastructure monitoring needs, you are recommended to use New Relic Infrastructure.
This guide explains the benefits of using New Relic Infrastructure, and provides tips on switching from using the deprecated New Relic Servers product to using Infrastructure.
For public discussion and questions about New Relic Servers going away, see the Servers end-of-life post on the Explorer's Hub.
Get started with Infrastructure
Infrastructure is designed to monitor complex environments, whether you use a physical datacenter, a large number of Amazon EC2 instances, or a combination of on-premises and cloud-based hosts. Infrastructure is designed for modern operations teams with dynamic, frequently changing systems.
Infrastructure pricing depends on your Infrastructure subscription. There is a free trial period.
If you have a large, complex environment, it's recommended you install the Infrastructure agent on at least 25 hosts, in order to get a sense of the power and level of detail Infrastructure can provide.
Here are some recommendations for getting started using Infrastructure:
- 1. Install the Infrastructure agent
To install New Relic Infrastructure on individual hosts:
- Review the compatibility and requirements checklists.
Follow installation procedures as applicable for your operating system:
To simplify rollout with your automation tools, use New Relic's configuration management modules to automate installation on multiple hosts:
- 2. Configure the Infrastructure agent
Installation is quick, requiring minimal additional configuration. You only need to configure your New Relic license key and any other settings as needed; for example, adding custom attributes or editing log file settings.
- 3. AWS EC2 monitoring and other integrations
If you use AWS, you can set up an Amazon EC2 integration and other AWS integrations. The EC2 integration only requires a read-only role, and it automatically imports your EC2 tags. It also automatically imports metadata about all the AWS services that you choose to monitor.
If you use Elastic Beanstalk, see Install Infrastructure for AWS Elastic Beanstalk.
There are also integrations for Microsoft Azure, Google Cloud Platform, and many other services. See Infrastructure integrations for more information.
- 4. Set up your alert configuration
You can configure new, flexible alert conditions directly from the hosts you are monitoring in Infrastructure. If you previously used legacy alerts or New Relic Alerts with New Relic Servers, you will need to set up new alert configurations.
- 5. Optional: Explore your Infrastructure data in New Relic Insights
Replacing the New Relic REST API queries for New Relic Servers, you can now query and share comprehensive Infrastructure data via New Relic Insights. If you'd previously used the REST API to query Servers data, you can now use the Insights API to retrieve equivalent data.
- 6. Optional: Uninstall New Relic Servers
The Servers installation has a very small overhead. To completely eliminate that overhead, you may wish to uninstall it even if it no longer available in the UI.
Operating system Uninstall New Relic Servers Linux
Windows Windows Server
You can also use the REST API to delete servers.
Infrastructure UI vs Servers UI
If you are accustomed to using New Relic Servers, here are some tips for starting out using the Infrastructure UI.
- Use Infrastructure's custom attributes to assign classes of servers. This will help identify specific hosts or instances important to your business and reduce long lists of servers in the UI.
- Use unique hostnames. You can filter on complete or partial names.
Here are some explanations of how Infrastructure features replicate and improve upon Servers features:
- Servers index = Infrastructure Inventory and Events
New Relic Servers provided a long index of individual or tagged groups of servers.
Use the Infrastructure Inventory page to view detailed configuration information per host for your entire inventory at a glance, including system modules, configuration files, metadata, packages, services, user sessions, etc.
In addition, take advantage of the Infrastructure Events page as a live feed for all your host metrics and log analytics events, to understand correlations between them and your environment. Search and filter through your events to decrease the mean time to repair and the mean time to detect issues.
- Servers Overview = Infrastructure Hosts
The New Relic Servers Overview page provided summary and detail information about a specific server.
Use the Infrastructure Hosts page to better understand your CPU, load, and memory for a host or a grouping of hosts.
- Servers Processes = Infrastructure Processes and Storage
The New Relic Servers Processes page provided memory or by CPU usage for an individual server.
Use the Infrastructure Processes page to examine CPU percentage, I/O bytes, and memory usage for individual processes or groupings of processes, then use this information to:
- Pinpoint processes that are causing performance issues.
- Create alerts directly from this page for conditions such as CPU percentage and memory usage.
In addition, use the Infrastructure Storage page to monitor the capacity and efficiency of your resources. This can help you:
- Examine unexpected patterns; for example, a cluster of mirrored machines that do not process I/O tasks uniformly.
- Monitor usage levels before disk space completely runs out.
- Set alert conditions to notify you about problems with one or more hosts; for example, long processing times for read or write operations, disk availability or utilization based on percentage or bytes, etc.
- Make informed decisions about where to redistribute hosts with higher or lower than normal processing requests.
- Use data to help plan for additions or changes to your infrastructure budget before an emergency arises.
- Servers Network = Infrastructure Network
The New Relic Servers Network page provided information about bandwidth, packets per second, and errors.
Use the Infrastructure Network page to measure and compare capacity. For example:
- Examine saturation levels across your network or filter sets.
- Compare load balances between specific resources.
- Identify unexpected differences in capacity patterns between similar hosts.
- Evaluate the top five network errors that New Relic Infrastructure automatically presents for the selected time period.
For problems activating New Relic Infrastructure, see Infrastructure troubleshooting.
Here are a few of the advanced features of New Relic Infrastructure. For an index of all Infrastructure documentation, see New Relic Infrastructure.
|Near real-time data||New Relic Servers collects metric timeslice data every minute. By comparison, New Relic Infrastructure collects and presents its event-based data every five seconds, allowing for flexible real-time analysis.|
|Powerful integrations||Infrastructure Integrations connects to Amazon AWS services like EBS, ELB, IAM, RDS, SQS, and more. This allows you to monitor every part of your infrastructure in one place. Infrastructure also connects to New Relic APM, so you can connect app performance data with the underlying architecture.|
|Tag-driven filters and alerts||With native support for Amazon EC2 tags, custom attributes, and a host of default attributes, Infrastructure allows you to filter and group your hosts according to your own criteria. New hosts automatically appear in the correct filters and alerts, and old hosts are automatically removed.|
|Change tracking||Infrastructure tracks change events on your host in near real-time. This allows you to correlate performance issues with events like a new user session, package installation, or configuration change. For more, see Infrastructure Events page.|
|Searchable inventory||Infrastructure tracks the packages, config files, and more on all your hosts. You can then search across every host to find vulnerable package versions when a zero-day is announced, or when outdated packages need updating. For more, see Infrastructure Inventory page.|
|Flexible alerting conditions||
With New Relic Infrastructure, you can create alert conditions directly within the context of what you are currently monitoring with New Relic. For example, if you want to be notified when New Relic has stopped receiving data from an Infrastructure agent, use the host not reporting feature.
Unlike the legacy availability monitoring feature for New Relic Servers, this allows you to dynamically alert on groups of hosts, configure the time window from 5 to 60 minutes, and take full advantage of New Relic Alerts.
|Data analysis and sharing||Because all Infrastructure data is event data, you can use New Relic Insights and NRQL to view and query the raw data.|