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
Ensure the Ruby SDK sets sentry.origin for Structured Logs according to the documentation #2747
User calls Sentry’s Logging API directly: SDKs MUST NOT send a sentry.origin. As logs are charged based on size, we want to minimize the size of logs, and we intentionally deviate from the original Trace Origin documentation.
Captured from a logging library: Use auto.log. format. where is the relevant integration. For example, the .NET Serilog library emits:
{ "sentry.origin": "auto.log.serilog" }
Auto-emitted logs from other instrumented systems: Use the auto.. format as outlined in Trace Origin documentation.
{ "sentry.origin": "auto.db.prisma" }
Feel free to close this issue if this is already aligned.
This is about aligning every SDKs so we have every sentry.origin set to auto.log.<name> when we capture a log created by a logging integration.
I see that in #2712 - and in master branch - we have sentry.origin set to auto.logger.rails.log_subscriber, and this is not aligned as per our new documentation.
Please review this again and let me know if you have any more questions!
Activity
linear commentedon Oct 9, 2025
RUBY-105
solnic commentedon Oct 13, 2025
This was addressed already via #2712
alexsohn1126 commentedon Oct 14, 2025
Hello @solnic!
This is about aligning every SDKs so we have every
sentry.originset toauto.log.<name>when we capture a log created by a logging integration.I see that in #2712 - and in
masterbranch - we havesentry.originset toauto.logger.rails.log_subscriber, and this is not aligned as per our new documentation.Please review this again and let me know if you have any more questions!