New Relic can collect detailed information about a system's configuration per host, including system modules, configuration files, metadata, packages, services, user sessions, and more. The Inventory page provides a real-time, filterable, searchable view into each host's configuration.
Use the Inventory page to:
Ensure a version update was applied successfully across all your hosts.
Audit version discrepancies across your hosts.
Quickly identify which hosts require an update to fix a security vulnerability.
The infrastructure inventory is a qualified namespace (structured like a directory) that organizes inventory items into names that resemble a source path. The inventory item name is comprised of three elements:
Element
Description
Category
Basic, top level type of data source, typically based on its role in the system. Common examples include config, package, kernel, user session, services, and modules.
Source
The specific data source for the inventory item.
Label
The name of the specific inventory item; for example, the filename, package name, or system setting name.
Tip
Use tagging for detailed metadata and other information about your hosts .
Page functions
Use Inventory page functions to find information about a particular item on your hosts:
Search for an inventory item using the search function.
For example, if you want to find information related to OpenSSL, search openssl. The search term is matched against the inventory item name.
Tip
If you want to find the Fluent Bit version being used on your system, in the Search Inventory search box, enter fluent-bit, then click > to expand the search results.
Inventory item details provide host and system information for each host it resides on according to the New Relic inventory item name. If you have different versions of the same item on other hosts, New Relic detects that and flags them on the Inventory page with the variant hosts label and lists each host running each version.
Item details are attributes (key/value pairs) that are dictated by their source. Specific attributes are generally stable over time, but new ones may be added and others could be deprecated. Attributes carry the critical metadata that are at the heart of each inventory item.
Common inventory item attributes include:
Variant hosts (hostname)
Architecture
Description
Essential
Priority
Status
Version
To view one or more host's alert threshold incidents, select the host's Critical
icon or Warning
icon.
Inventory data collection
Inventory is collected from the infrastructure agent's built-in data collectors, Amazon Elastic Compute Cloud (EC2) integrations, agent integrations provided by New Relic, and customer-built integrations. The data appears on the Inventory page and in other places in our infrastructure UI.
The infrastructure agent collects this data for Linux systems.
Category
Source
Data collected using...
applications
apm
APM language agent metadata.
APM metadata is created in the ingest pipeline when infrastructure and APM agents are running on the same host
config
selinux
sestatus -b, semodule -l
selinux-policies
sestatus -b, semodule -l
selinux-modules
sestatus -b, semodule -l
sshd
/etc/sshd_config (PermitRootLogin, PermitEmptyPasswords, PasswordAuthentication, and ChallengeResponseAuthentication only)
The infrastructure agent uses a combination of built-in instrumentation and the com.newrelic.winpkg integration to collect system information on Windows hosts.
The following table shows the data that is collected on Windows systems.
Category
Source
Data collected using...
applications
apm
APM language agent metadata.
APM metadata is created in the ingest pipeline when infrastructure and APM agents are running on the same host
The filter set UI component is used for filtering your hosts and creating saved views. It is only available on the Events and Inventory UI pages and is in the process of being deprecated. It has been replaced by the saved views feature. Any filter sets you create from this point onward will not be migrated to the saved views feature.
With New Relic infrastructure monitoring, you can combine filters into a filter set to organize hosts based on criteria that matter the most to you. Your account may have hundreds of hosts reporting to it, so focusing on what's important is crucial for being able to troubleshoot effectively.
See patterns within categories
You can create filter sets using available attributes or tags.
For example, you can organize your infrastructure into categories such as:
Regions
Operating system versions
Hosts associated with Docker containers
Test environments
You can share filter sets with other people in your account, and you can quickly identify infrastructure problems by checking the color-coded health status of each host in the filter set.
Create filter sets
The default infrastructure filter set is All hosts, and it serves as a template for you to create filter sets.
Click values individually or enter text to match multiple values.
Continue adding filters until you have the filter set you want.
To name your filter, click the
icon, type a name, and click Save.
Edit filter sets
To change an existing filter set:
In the sidebar, click Saved filter sets to open a list.
Locate the filter set by scrolling or by entering a search term.
Click the filter set to open it.
In the sidebar, click an option to update your filter set, and then save.
Filter set logic
When you create a filter set, you generate a list of attributes and/or tags that narrow the results. This section explains how filter sets apply various rules to the list.
Inclusion and exclusion
As part of building a filter set, you designate whether a filter should include or exclude entities that match certain values.
The way the inclusion or exclusion works depends on how you select values:
You can generate a list of values by entering a string that you want values to match. This is useful for matching multiple values.
Tip
String matching efficiently generates a list of values, and this approach scales as you add new entities.
Here is the logic filter sets use with string matching:
Comparator
Logic
Include
If you click Include and then enter a string that you want values to match, the filter uses the comparator LIKE, which means the results include any entities that are like the string.
For example, you could filter by the term East-, and all entities that contain that term are returned.
Exclude
If you click Exclude and then enter a string that you want values to match, the filter uses the comparator NOT LIKE, which means the results exclude any entities that are like the string.
For example, you could filter by the term West-, and all entities that do not contain that term are returned.
You can click through the list of attributes/tags to identify individual values.
Tip
This approach does not scale well if you add new entities.
Here is the logic filter sets use with individual value selection:
Comparator
Logic
Include
If you click Include and then click specific values, the filter uses the comparator IN, which means the filter looks for entities that exactly match one or more values in your list of selections.
Exclude
If you click Exclude and then click specific values, the filter set uses the comparator NOT IN, which means the filter returns all entities that do not exactly match one or more values in your list of selections.
And/Or
Filter sets use the logical operators AND and OR behind the scenes to join the data.
When you click values from multiple attributes or tags, they are joined by AND.
When you click values from within an attribute or tags, they are joined by OR.
The filter results display hosts for which both of the following are true:
Hosts containing any one of the selected infrastructure agent versions
Hosts in any one of the selected AWS availability zones