You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Semantically equivalent deprecated attributes have deprecation status null #570
I think this is an issue and makes cross-attribute-key lookups like we need to do in the sentry frontend (via #569 and #508) harder than necessary. My guess is, these attributes were added prior to backfilling/normalization but I might also lack context here.
Here's a list:
Old
Replacement
Note
code.filepath
code.file.path
code.lineno
code.line.number
db.name
db.namespace
http.client_ip
client.address
http.flavor
network.protocol.version
http.scheme
url.scheme
http.server_name
server.address
http.status_code
http.response.status_code
http.url
url.full
http.user_agent
user_agent.original
net.host.ip
network.local.address
net.host.name
server.address
net.host.port
server.port
net.peer.ip
network.peer.address
net.protocol.name
network.protocol.name
net.protocol.version
network.protocol.version
net.sock.host.port
network.local.port
net.sock.peer.addr
network.peer.address
Old was IP-only; still a valid value of the target
net.sock.peer.port
network.peer.port
net.transport
network.transport
runtime.name
process.runtime.name
runtime.raw_description
process.runtime.description
Target brief states it is equivalent to raw_description
runtime.version
process.runtime.version
sentry.browser.name
browser.name
sentry.browser.version
browser.version
sentry.user.email
user.email
sentry.user.geo.city
user.geo.city
sentry.user.geo.country_code
user.geo.country_code
sentry.user.geo.region
user.geo.region
sentry.user.geo.subdivision
user.geo.subdivision
sentry.user.id
user.id
sentry.user.ip
user.ip_address
sentry.user.username
user.name
url
url.full
I propose we set backfill or normalize to these attributes or call out why they should not be migrated
Activity
linear-code commentedon Aug 13, 2026
CON-104