Every attribute sent on an event should be searchable, not just indexed tags

Problem Statement

Native and game-client SDKs attach a large amount of structured context to each
event: device and driver properties, build metadata, module state, platform-specific
fields from crash reporters. Today only values promoted to indexed tags are
searchable in the issue stream and in Discover. Everything else is visible on the
event detail page but cannot be searched, filtered, aggregated, or alerted on.

For teams operating high-volume clients across many hardware configurations, the
useful question during an incident is almost always a filter on a field that was
never promoted to a tag. Engineers end up either scanning individual events by hand,
or duplicating the same data into a tag purely to make it queryable, which inflates
cardinality for a reason that has nothing to do with the data model.

The underlying problem is that tag promotion is a decision made at instrumentation
time, before anyone knows which field will matter during an incident. The tag
namespace is finite and cardinality-sensitive, so teams self-censor and
under-instrument, and then cannot answer the question when it arrives.

Solution Brainstorm

• Make all event attributes first-class queryable fields, using the same search
  grammar as tags.
• Expose them consistently: issue search, Explore, alert conditions, dashboard
  group-bys.
• Where cardinality is a real constraint, allow per-attribute opt-in to indexing at
  the project or organization level, so the decision can be made after the fact
  rather than requiring an instrumentation change and a client release.

Product Area

Issues

Requested by Saad Khan.

--

View Junior Session [Sentry]

The issue names no files, tests, or entry points, so first map how event attributes and indexed tags flow through issue search, Explore, alerts, and dashboard group-bys. Done would mean defining and implementing a consistent query model for all event attributes while addressing cardinality through project- or organization-level indexing controls.