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 are used to group, search, filter, and focus your data in a way that's useful for troubleshooting and understanding your environment. You can use tags to effectively manage and monitor your complex modern software:

  • Use tags to organize all your entities. Create tags for teams, roles, or regions to know who is responsible for what.

  • Add tags to dashboards that visualize your entity data. Easily find dashboards related to the data or entities you care about.

Tags are created and managed via the GraphQL API. Once they've been created, you can use tags to filter, facet, and organize the elements of your complex systems in New Relic One.

Tags are available for filtering in the New Relic One UI, which is only available for paid accounts. All account types can use the GraphQL Explorer for organizing tags via API.

Organize your entities, services, and teams

Tags are used to organize every entity you monitor with New Relic. By applying tags to various entities, you can organize all your data in ways that make sense for your environment. For example, you can use tags to organize entities by the teams responsible for them, or by the applications they support.

Add, edit, and manage tags via the GraphQL API

Use the New Relic GraphQL Explorer to create, edit, and delete tags. Once tags are created, they are available for searching and filtering in the New Relic One UI.

If you have not used the GraphQL Explorer, read the Introduction to the New Relic GraphQl API for information on authentication, endpoints, and terminology.

If you're already familiar with the GraphQL 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've created 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:

  • In the 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.
  • Via API: use GraphQL 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 features

Browser apps only.

Identifies your subscription level (Pro, Pro + SPA, or Lite). Your subscription level determines whether additional Browser features are available.

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.

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.

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

Each tag is key-value pair. 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

Filter by tags in New Relic One
one.newrelic.com > Entity explorer > Filter by tags: after you've applie dtags to entities, you can easily search for them in New Relic One.

After you've applied tags using the GraphQL API, 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

APM uses labels to organize your data, similar to how tags work in New Relic One. If you have pre-existing labels for APM, 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:

  1. Go to one.newrelic.com.

  2. Click on the Entity explorer.

  3. Enter your APM label in the Filter with tags field.

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 might include:

  • hostname:production-app1.my-corp.net

  • operatingsystem:linux

  • agentversion:1.1.7

Tags drawn directly from Infrastructure attributes cannot be edited with GraphQL. However, you can add additional tags for your Infrastructure entities, and edit or remove them via GraphQL. 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.

To search for your pre-existing attributes as tags in New Relic One:

  1. Go to one.newrelic.com.

  2. Click on the Entity explorer.

  3. Enter your APM or Synthetics label in the Filter with tags field.

For more help

Recommendations for learning more: