A tag is a key-value pair that can be added to an entity. Tags help you group, search, filter, and focus your data to troubleshoot and understand your environment. For example, you can use tags to:
- Organize all your entities efficiently.
- Identify teams, roles, or regions so you quickly know who is responsible for what.
- Easily find dashboards that visualize the entities or data you care about.
Add, edit, and manage tags
You must have a paid account to filter tags in the New Relic One UI. However, all account types can use the NerdGraph GraphiQL explorer at api.newrelic.com/graphiql to organize tags by API.
If you're already familiar with the NerdGraph GraphiQL explorer, see the following tutorials for sample queries:
- Manage tags: add, delete, view, and replace tags for entities
- Query entities: search for and see relationships between entities
View tags and metadata for an entity
After you create tags, it's important to know which tags have been added to various entity types. You can see all the tags that have been added to an entity in two ways:
- UI: From the entity explorer, select an entity from the index. On the Summary page you can see all the tags that have been added to the entity, as well as the entity's guid, account ID, and App ID.
- API: Use NerdGraph to read the existing tags for an entity.
After you select an entity from the entity explorer, New Relic automatically shows corresponding metadata about it. Depending on the type of entity (services, hosts, browser or mobile apps, etc.), you can tag, view, facet, search, or query the metadata in several ways, such as:
- Metadata descriptions and examples
The New Relic account ID associated with an entity defines what permissions someone has to view or manage data.
For example, if you know the
Account ID, you can:
- Add colleagues to an account so they can see entities
- Navigate to more specific troubleshooting experiences for an account
The New Relic account name associated with this entity. This can help provide context for which business unit manages the account.
For example, you can use the
Account namein the global search or entity index to see a list of entities on a specific account.
Browser apps only.
Identifies your subscription level (Pro, Pro + SPA, or Lite). Your subscription level determines whether additional Browser features are available.
The language agent version currently installed for this application. (If you want to check whether you have the most up-to-date version, see the specific agent's release notes.)
The New Relic application ID for the specific type of entity.
The globally unique identifier for a specific entity in New Relic. Also referred to as a universally unique identifier (UUID).
The programming language you used to install your application. Specific language agents may offer additional features to view in the New Relic UI or to query your data.
You can use tags to organize entities across your organization in the following ways:
|Use case||Tags to use|
Form entities into logical groups
Group your entities by applications, names, roles, or regions. Using different tags for various groups allows for more specific filtering in the New Relic One UI.
Indicate ownership of the entity
Use tags for teams, account names, or priority levels to know what needs to be fixed by which team.
Rank entities by criticality
Create tags for criticality levels, then add them to your entities so you can easily keep track of your most important ones.
Indicate the environment the entity is deployed to
Use tags to keep track of all your AWS integrations or containers.
Indicate facts about the entity
Use tags to indicate operating system, agent type, technology platform, or what application an entity is running.
Formatting and parameters
When using tags, be aware of the following parameters:
An entity can have a maximum of 100 key-value pairs tied to it. This is valid whether you have 100 values for one key, or 100 separate keys that each have a single value.
A key can have a maximum of 128 characters.
A value can have a maximum of 256 characters.
Use tags in New Relic One
After you apply tags using the NerdGraph GraphiQL explorer, you can use them for searching and filtering in New Relic One. Select tags to filter entities across accounts to focus on just the data and system statuses you care about.
To use tags in New Relic One, search for your tagged terms anywhere you see the
Filter with tags field. Filtering with tags will surface all entities that have the tag attached through cross-account search.
Use consistent naming for tags across your organization. Consistent tags make it easier for everyone in your account to filter across complex systems.
Use labels from APM or Synthetics
As of July 20, 2020, the New Relic One tagging functionality will replace Synthetics labels and the ability to organize Synthetics and APM tags into groups. You can start migrating to this change now. (As of July 8, 2020, automatic migration begins for existing Synthetics tags.) For more information, including how to migrate your existing tags through the UI or NerdGraph tagging API, see New Relic's Explorers Hub post.
APM and Synthetics use labels to organize your data, similar to how tags work in New Relic One. If you have pre-existing labels for APM or Synthetics, you can automatically use them in the same ways you use tags when searching and filtering.
To search for your pre-existing labels as tags in New Relic One:
- Go to one.newrelic.com.
- Click Entity explorer.
- In the
Filter with tagsfield, enter your APM or Synthetics label.
Filter by Infrastructure attributes
If you use attributes with New Relic Infrastructure, the Infrastructure agent registers some attributes as tags in New Relic One. These tags are available by default for searching and filtering in the New Relic One UI.
Examples of default tags created by Infrastructure attributes for a host include:
Tags drawn directly from Infrastructure attributes cannot be edited with NerdGraph. However, you can add additional tags for your Infrastructure entities, and edit or remove them with NerdGraph. For example, if you want to associate a given host with a team, you could apply
team:my-team as a tag, then later edit or remove it as needed.