logs attribute naming conflict

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Generate a log with something like:

const origin = "http://disallowed.com";
log.warn({ origin }, 'Received request from disallowed origin');

2. Try query logs with origin:

Expected Result

I can very clearly see the origin attribute in the individual logs, and the value is correct (not auto.log.pino). However, I should be able to filter/query by it in the dashboard without it being overwritten by what I assume is an internal origin field added by Sentry.

Actual Result

Product Area

Explore

Link

https://freecodecamp.sentry.io/explore/logs/?aggregateField=%7B%22groupBy%22%3A%22origin%22%7D&aggregateField=%7B%22yAxes%22%3A%5B%22count%28message%29%22%5D%7D&environment=api-org&logsFields=timestamp&logsFields=message&logsFields=origin&logsQuery=message%3A%22Received%20request%20from%20disallowed%20origin%22&logsSortBys=-origin&mode=aggregate&project=4508182869508096&statsPeriod=7d

DSN

No response

Version

No response

Reproduce the conflict using the TypeScript log example and the linked Sentry Explore query. Start by tracing how the origin attribute is displayed versus how the Explore dashboard aggregates and filters it. Done means user-provided origin values remain queryable without being overwritten by Sentry’s internal field.