Acceldata
AIO

Last updated: Nov 17, 2026 16:52 UTC

Turn on attribute keys in a project's Attribute Tags settings, and each new span that carries one of those attributes gets a tag made from the attribute's value.

For example, if you turn on the key user.tier, a new span with user.tier set to gold gets the tag user.tier:gold. To learn how attribute tags relate to tags set in code and tags added by hand, see Tags overview.

Prerequisites

  • You need permission to modify the project. Without it, the page is read-only. For details, see Who can change attribute tags.
  • The project needs spans from the last 24 hours. The page offers only attribute keys it has seen on the project's spans in that time.

Open the Attribute Tags page

  1. Go to the Projects list.
  2. Next to the project, select the gear icon (Settings for followed by the project name).

Project settings for a project, open on the Attribute Tags page

The Attribute Tags page opens. It shows how many keys are on out of the project's limit of 20, for example 3 of 20 enabled.

The table has three columns:

Column What it shows
Attribute The attribute key.
Spans, last 24h How many of the project's spans carried the key in the last 24 hours. A key that's on but wasn't seen in that time shows —.
Enable A switch for the key, labeled on or off.

Keys that are on come first. The keys that are off come after them, with the most common first, up to 50 keys. The table shows 10 rows per page by default. You can switch to 20 or 50.

Attribute Tags page with the enabled count, the Search attributes box, and the table of attribute keys with their switches

Turn on an attribute key

  1. On the Attribute Tags page, in Search attributes, enter part of the key name. The search isn't case-sensitive.
  2. In the key's row, turn on the switch in the Enable column.

The label changes to on. While a change is saving, all the switches are unavailable.

Some keys can't be turned on, and they never appear in the table:

  • Keys that start with aio..
  • Keys that contain , or |.
  • Large text attributes: gen_ai.workflow.input, gen_ai.workflow.output, gen_ai.tool.call.arguments, gen_ai.tool.call.result, mcp.request.payload, mcp.response.payload, gen_ai.retrieval.documents, gen_ai.retrieval.query.text, gen_ai.system_instructions, and gen_ai.tool.definitions.

A key also can't be turned on if it had 1,000 or more distinct values in the last 24 hours. A key with that many values is too varied to be useful as a tag.

Turn off an attribute key

  • On the Attribute Tags page, in the key's row, turn off the switch in the Enable column.

New spans stop getting the tag. Tags that spans already have stay on them.

Which spans get the tag

An attribute key that's on applies:

  • Only to new spans. Spans ingested after you turn on the key get the tag, starting with the next batch of spans the project receives. Spans recorded earlier don't get it.
  • Only in this project. Each project has its own set of attribute keys.
  • Only when the value fits. A span gets the tag only if it carries the attribute with a value of 1 to 200 characters. A span with an empty value or a longer one gets no tag for that key. Long values aren't shortened.

Attribute tags are read-only in the UI. You can't remove one from a trace, session, or span. To find traces, sessions, and spans by their tags, see Filter by tags.

Who can change attribute tags

  • Users who can modify the project can search keys and turn them on and off. A resource admin can modify every project.
  • Users who can only view the project see only the keys that are on, each labeled on, with — in the Spans, last 24h column. They don't see Search attributes or the switches. If no keys are on, the page says None enabled.

For more about these permissions, see Project permissions.

Troubleshooting

The switch for a key is unavailable, with the tooltip "Limit of 20 reached. Turn one off to enable this."
The project already has 20 keys on. Turn off a key you no longer need, and then turn on the new one.

The page says "That key changed on the server. The list has been refreshed."
The key was already turned off, for example by another user. The list reloads with the current settings.

The table says "No attributes in the last 24 hours."
The project has no spans with attributes from the last 24 hours. Send traces from your application, and then open the page again. To get started, see Instrument your code.

The table says "No matching attributes."
No key seen in the last 24 hours contains your search text. Check the spelling, or clear the search.

Next steps