Tagging: Use tags to organize and group what you monitor

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.

In July 2020, labels for APM and synthetic monitors were replaced by tags. Learn more.

Add, edit, and manage tags

You can create and manage tags with New Relic NerdGraph. Then you can use the tags to filter, facet, and organize the elements of your complex systems in New Relic One.

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
Metadata Description

Account ID

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

Account name

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 name in the global search or entity index to see a list of entities on a specific account.

Agent version

APM only

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.)

App ID, Browser ID, Mobile ID

The New Relic application ID for the specific type of entity.

Entity GUID

The globally unique identifier for a specific entity in New Relic. Also referred to as a universally unique identifier (UUID).

Language agent

APM only

For APM agent's programming language. Specific language agents may offer additional features to view in the New Relic UI or to query your data.

Tagging examples

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 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

New Relic One tags in UI
one.newrelic.com > Entity explorer: After you apply tags to entities, you can easily search for them in the UI.

After you apply tags using the NerdGraph GraphiQL explorer, you can use them for searching and filtering in the UI. Select tags to filter entities across accounts to focus on just the data and system statuses you care about.

To use tags, search for your tagged terms anywhere you see the Filter field. Filtering with tags will surface all entities that have the tag attached, across the accounts you have access to.

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 and synthetic monitors

In July 2020, the label feature for APM and synthetic monitors was replaced by tagging (described in this doc). For an explanation of this transition, see this Explorers Hub post.

If you have pre-existing labels for APM or synthetic monitors, you can use them in the same ways you use tags when searching and filtering. To search for your pre-existing labels as tags:

  1. Go to one.newrelic.com and click Entity explorer.
  2. In the Filter with tags field, enter your APM or Synthetics label.

Filter by infrastructure attributes

If you use attributes with infrastructure monitoring, our infrastructure-monitoring agent registers some attributes as tags. These tags are available by default for searching and filtering in the UI.

Examples of default tags created for a host include:

  • hostname:production-app1.my-corp.net
  • operatingsystem:linux
  • agentversion:1.1.7

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.

For more help

If you need more help, check out these support and learning resources: