Logs in Sentry 🚀

[Dhrumil-Sentry]

TL;DR

Sentry is adding support for structured logs, so you can view and query your logs alongside your traces and errors—all in one place.

Want early access? Comment below with your org slug or email [email protected] with your org slug, and we’ll get you set up.

For more details, keep reading or join the discussion below!

---

One of the biggest asks we've heard from our users is that you'd like to have the ability to send logs to Sentry, to have a single pane of glass for all your observability needs.

For those of you that have been with us for a while, you know we've always had some opinions about logging and how we’re focused on errors-first troubleshooting. However, we recognize that for many developers, log statements often provide valuable context for identifying and correcting problems.

To that end, we're happy to announce that we're adding support for logs in Sentry. Soon, you'll be able to send logs to Sentry and view them alongside traces & errors.

Read more details on how we're implementing support for logs, the "Sentry way" (or, if you'd like, Sentry's version). ⬇️

What can you do with Logs in Sentry?

• View logs from across your application: Use our new Log Viewer to search and filter your application logs based on any attribute.
  
• Find relevant logs when debugging errors: View logs in context directly from an error in Sentry to quickly understand what led to the issue.
  
• (Coming Soon) Aggregate and analyze log patterns: Slice and dice logs to monitor patterns, unusual events, or any key behavior in your app. You can visualize these patterns in dashboards or set up alerts based on log data.
  

Why Logs in Sentry?

When debugging, logs, traces, and errors work better together. Logs provide the granular context—like retries, API failures, and internal state—that spans and errors can miss. But in most tools today, logs live in a separate system, forcing you to switch between tools to piece together the full picture.

With logs in Sentry, everything is in one place. You can see logs right alongside your errors and traces—no more context switching, just faster debugging.

Getting started is just as easy as adding a console.log or logger.info. Our SDKs handle the heavy lifting, automatically linking your logs to traces and errors so you get the full context with minimal setup.

Also - We're supporting structured logging that will support passing variables in a string template directly - We'll extract your variables and the template as attributes of the log that you can query

Supported SDKs: What’s Available and What’s Next

We’re kicking things off with JavaScript (including TypeScript and frameworks like NextJS, etc), and support for Python will be available in the next two weeks. More languages will follow as we expand logging support across our SDKs.

We’re also working on seamless integrations with popular logging frameworks. That means no major rewrites—just flip a switch at the SDK level, and your logs will start flowing into Sentry alongside your traces and errors.

Getting Access: Be the First to Try Logs in Sentry

We’re rolling out logs support to a limited set of customers first, and we’d love your feedback. If you want early access, reply to our GitHub discussion with your organization slug or email us at [email protected].

Here’s what to expect:

• The UX will be available in about two weeks to those who opt in.
• JavaScript support is live now; Python will follow in two weeks.
• We’ll work closely with early users to refine log search, cross event connectivity, and analysis before general availability.

How to Start Sending Your JavaScript Logs

Once you have access you can follow these instructions

Install the right SDK version:

npm install @sentry/browser@9.6.0-alpha.0

If you’re using a framework specific SDK then you can swap sentry/browser with sentry/nextjs or sentry/react

Start logging with the new APIs mentioned in these release instructions

What Feedback Are We Looking For?

• Does the log search experience meet your needs?
• How easy was it to get set up?
• Are there specific features or capabilities you’re missing?

Your input will help us refine our Logs as we work towards general availability.

Drop your thoughts below, or email us directly at [email protected]. We’re looking forward to hearing from you!

[tcurdt]

For us search isn't really that super important. Triggering alarms would be the main thing we would be interested in.

[Dhrumil-Sentry]

@tcurdt thanks a lot for this feedback - Would love to understand what type of aggregate queries do you write on top of Logs

[tcurdt]

TBH ... we tweak our our logs so that ERROR really means error. We try to log as little as necessary.
What would be nice if types log lines could be automatically (or semi automatically) be grouped.

"something happened to [foo]"

So all except what is in between [] could contribute to the grouping fingerprint.

"something happened to [*]"

That would be the aggregating I could imagine. And that's also what could be used for the basis of different alarm triggers.

[Dhrumil-Sentry]

Thank you for sharing these details - We're going to support structured logging - so you will have access to the template you used to log in your code as a searchable attribute too and you should be able to write a query that gives you the count of logs matching that template over a time interval and alerts would be supported too - We're just a few more weeks away from enabling that but we def plan to have it when Logs become generally available 😄

[JoshFerge]

could you add the org joshys-testing-stuff to the beta? 🙏🏼 <3

[zleight1]

Hi, looking forward to seeing what you do with this feature 🤩 !

Can you add this to our org torq-dp?

[Dhrumil-Sentry]

@zleight1 We'll add you org when we roll this out and will drop a note here too

[carolineartz]

looks great! Interested in the beta :) cutover-pg org

[Dhrumil-Sentry]

@carolineartz We'll let you know once we release it for you, Would love to understand how you search logs today? Do you search by attributes of a structured log or do you use wildcard matching over the entire message

[RationalRank]

Will you support mobile SDKs in the future? If so, will you also consider processing everything on-device, and allow us to configure settings such that logs are pushed only when there's an error, and not simply push all logs to Sentry?

Use case: When there is an Exception captured by Sentry, I would see a consolidated list of breadcrumbs + logs to get the full picture. Right now, we have a breadcrumbs section, but a combined view would be great.

Example:

• java.lang.NullPointerException: null
  • LOG: W: Order does not have an ID
  • BREADCRUMB: HTTP call
  • BREADCRUMB: User clicked order
  • BREADCRUMB: App lifecycle - Launched

[Dhrumil-Sentry]

@RationalRank We will support Mobile SDKs as a quick follow up once we launch for JS and Python. Also we're planning to gradually consolidate breadcrumbs and logs but that's a longer term effort for us once logs are generally available so users will get a consolidated view.

We plan to support SDK APIs to allow for client side filtering of logs but we don't have plans to support sending logs only when there is an error - Is your main reason to control the volume of logs you send to Sentry?

[RationalRank]

@Dhrumil-Sentry Yeah, that's right

[jtmaveryk]

Can’t wait, always wish this was integrated, it’s really an AIO now! Would love to participate in the beta (airplo) 😊

[Dhrumil-Sentry]

@jtmaveryk - Thanks for the interest! Any must-have use cases or capabilities you'd like to see in Logs?

[jtmaveryk]

Nothing that you guys haven't already thought of, haha. The logs would be a crucial part helping link errors to issues/events.

[talas9]

Hi, could you add skycrew please? we are very interested in testing this in JS and Python

[Dhrumil-Sentry]

@talas9 Will def add you in and let you know soon - Would love to understand if you write custom log query based alerts today already ? Or are you mainly interested in search and seeing errors and all related logs together?

[talas9]

I don't have any retention implementation at the moment, some projects are GCP and some are on Heroku so might be good to have the ones on Heroku handled professionally

[zhiyan114]

I'd love to try out logging as well @ furrynet

Perhaps, some kind of pattern matching (regex?) alert would be really useful.

[Dhrumil-Sentry]

@zhiyan114 Thanks! Would love to understand what type of regex queries do you run - We're going to have support for wildcard matches similar to a contains operator and iterate.

[zhiyan114]

I'm thinking something like [Log]: Error Code {1 to 128} where we might only want to send a notification if the error code is between 1 to 64, for example.

In this case, instead of writing multiple notification conditions, we could use \[Log\]: Error Code (?:[1-9]|[1-5][0-9]|6[0-4])\b to filter it. Though, I think there's probably more efficient way to do this than using regex.

[Dhrumil-Sentry]

@zhiyan114 Thanks for sharing this use case. We're going to be supporting structured logging - So you can just log like this

Sentry._experiment_log.info(fmt user ${username} just bought ${item}!);

And Sentry would store the template and the username both as attributes in your log and you can directly query for these attributes