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.

We currently support Logs from JavaScript and Python. You can find the SDK instructions below:

JavaScript SDK 9.11.0 or higher. Instructions here.

Python SDK 2.25.1 or higher. Instructions here.

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.

SDK Support

JavaScript SDK 9.11.0 or higher. Instructions here.

const { debug, info, warn, error, fatal, fmt } = Sentry.logger;

debug('Cache miss for user', { userId: 123 });
info(fmt(`Updated profile for user ${userId}`));
warn(fmt(`Rate limit approaching for endpoint ${endpoint}. Requests: ${requests}, Limit: ${limit}`));
error('Failed to process payment', { orderId: 'order_123', amount: 99.99 });
fatal('Database connection pool exhausted', { database: 'users', activeConnections: 100 });

Python SDK 2.25.1 or higher. Instructions here.

We'll be actively adding support for more SDKs over the coming weeks, but if you want to see a specific SDK prioritized, please leave a comment!

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

[edgariscoding]

This is awesome! Very happy to see logging added to Sentry!

[joshdales]

Could pockethealth please be added to the beta 🙏 Would love to try this out

[Dhrumil-Sentry]

@joshdales - Thanks a lot for this detailed feedback ! - we're going to addressing a lot of these soon and adding the ability to view count of logs as a chart too in that page

[AbhiPrasad]

It would be nice if the user id (maybe other user data but really at least that) from when we called Sentry.setUser could be included in the log, currently I'm just adding that property myself which is fine but it would be nice if there was a global setting that I could include for all logs so that I didn't have to pull in the logic to get that.

We're working on adding defaults attributes for logs like user id, browser, and device. For now you'll have to set it yourself until we define what the defaults should be for every platform we support, but we'll definitely make this easier for you!

If you want to add this to every single log but define it once, you can define a beforeSendLog function. JavaScript example:

Sentry.init({
  _experiments: {
    enableLogs: true,
    beforeSendLog: (log) => {
      log.attributes = {
        ...log.attributes,
        'user.id': getUserId(),
      };
      
      return log;
    }
  }
});

[joshdales]

Nice - would the chart apply to searches?
Just that I generally use the message field like this commonNameForLibOrFeatureOrSomething.entityThatWeAreDealingWith.actionBeingPerformed, so in your example rather than doing this:

Sentrylogger.info('Adding item to cart', { item: 'sneakers' });
// later
Sentry.logger.error('Failed to purchase item in cart', { item: 'sneakers', ...err });

We do

Sentry.logger.info('cart.add', { item: 'sneakers' });
// later
Sentry.logger.err('cart.purchase', { item: 'sneakers', ...err });

So that if I wanted to search for everything related to the cart I can just do log.body is "cart.*" or even log.body is "cart.*"|log.severity_text is "error" and get the count for how cart based events, or cart errors happened?

[Dhrumil-Sentry]

So that if I wanted to search for everything related to the cart I can just do log.body is "cart." or even log.body is "cart."|log.severity_text is "error" and get the count for how cart based events, or cart errors happened?

Yes - it will apply for searches too! That's exactly what we're building

[joshdales]

Amazing! Looking forward to it

[liamjones]

This is really nice to see.

Is this feature intended to only collect logs from the things integrated with the Sentry SDK? Or are there plans to ultimately support log shipping from other sources into the Sentry UI, too?

[Dhrumil-Sentry]

@liamjones - We're starting with logs collected from the Sentry SDK, would love to understand what other sources did you have in mind?

[liamjones]

@Dhrumil-Sentry It wasn't anything particularly concrete; I was just thinking about things that might be useful as extra context when investigating issues.

For instance, a scenario where we have a Sentry application that depends on another application which cannot be integrated with Sentry, such as a closed-source third-party app. In such cases, it would be potentially useful to have access to the logs of the closed-source application or the slow query logs of the database that the application utilizes.

[wichopy]

Please let me know if we can get some access at the slug qliktechnologies :)

[Dhrumil-Sentry]

@wichopy - We'll def enable this for your org as well - Stay tuned for an update sometime next week 😄

[gasparbrogueira]

Will it also be available in a self-hosted version?

[Dhrumil-Sentry]

Yes it will, You might find this issue in the self-hosted repo helpful: getsentry/self-hosted#3560

[fmod-andrew]

Sounds great! Can we use it from sentry-native? 🙏

[Dhrumil-Sentry]

Hi @fmod-andrew - We will be rolling out support for more SDKs including sentry-native but we don't have concrete timelines for that yet

[fmod-andrew]

Keen to help out testing early sentry-native support when the timelines firm up. Slug = firelight-technologies

[weedgrease]

would love to try this out with our team! proofteam is our slug ❤️

[dsschnau]

What an exciting feature! I have one concern: How will this affect data caps?

[Dhrumil-Sentry]

@dsschnau - During the Beta period we don't charge for these logs - Once logs are generally available they will be charged as a new product SKU - they would not impact your existing volumes for products like errors.

Does that answer your question?

[dsschnau]

It does, thank you!

[tony-garcia]

Can you please add us to the preview? Our slug is relaytx. Thanks!

[Dhrumil-Sentry]

@tony-garcia we'll add your org to the list 😄 - We're just working on some SDK fixes before we roll this out very soon

[tony-garcia]

awesome. thanks!

[keegandonley]

Looks great, can you please add kizen to the preview? Thank you!

[Dhrumil-Sentry]

@keegandonley - We'll add your org in -please let us know if there's any capability that you think is a must have

[Dhrumil-Sentry]

Question for everyone - How important is the ability to attach stacktraces to your logs? Do you do this often today?

[tony-garcia]

We don't do this currently and I can't say it's terribly important to us. Though at this point we are using a separate system to view logs and we're used to matching them to error messages by timestamp/system.

[ntindle]

I'd like this

[Dhrumil-Sentry]

@ntindle - Would you want to see logs with stacktraces become info/warning level issues in Sentry or do you want to just see the stacktraces while browsing logs ?

[thafryer]

This is exciting to see. We use pino as our logging library and send these to New Relic. How do you all see this integrating with libraries like pino or winston?

[AbhiPrasad]

Hey @thafryer we're planning logging integrations for pino, winston as well as the console object via the console.X APIs for the JavaScript SDK. We'll add this soon (I'm actively working on it 😄). You can track support for these in the following GitHub issues:

1. console: Add consoleLoggerIntegration sentry-javascript#15917
2. pino: Add pinoIntegration sentry-javascript#15952
3. winston: Add winstonIntegration sentry-javascript#15953

[aldy505]

@thafryer You can use something like this while waiting for the official SDK integration: https://gist.github.com/aldy505/2d0b6ac49a888924b2252ef356e7ff53

[dogweather]

I am super happy to see this! I just spent a full day trying—and being disappointed by—the logging services I used to use like Papertail and Loggly. Both are now Solarwinds products and are basically being killed off, as far as I could tell.

I did check the Sentry current docs and didn't see anything yet, so I set up a trial at Datadog. It definitely works, but I'd much prefer to keep everything at Sentry.io.

My use case is web apps and console apps written in:

• Ruby / Rails
• Python
• Elixir / Phoenix

My organization's slug is public-technology. I use the logging to, e.g., debug my Content Security Policy code. Datadog doesn't directly support Ruby or Rails, so my stack is:

Rails -> Dokku -> Vector -> Datadog

I configured Rails to create JSON-formatted logs, which Datadog can use and optionally map to its vocabulary. They have a blog post which I followed. Here's an example log entry from my Rails app:

{"method":"GET","path":"/statutes/tex._health_and_safety_code_section_144.026","format":"html","controller":"StatutesController","action":"show","status":"INFO","allocations":13981,"duration":31.69,"view":17.5,"db":7.24,"host":"Dokku","source":"ruby","service":"website","version":"2.1.65","hostname":"texas.public.law","message":"GET /statutes/tex._health_and_safety_code_section_144.026","code":200,"subdomain":"texas"}

It'd be nice to support Vector, because it's pretty easy to use with Dokku.

[Dhrumil-Sentry]

@dogweather Thanks a lot for this detailed feedback - We'll add you to the beta list- We don't have concrete timelines for Ruby/Elixir yet but will keep you posted !

[dogweather]

Thanks @Dhrumil-Sentry I'm looking at what it'd take to create a Vector sink for Sentry. That would turn an order(N) problem into order(1).

https://vector.dev/docs/reference/configuration/sinks/

[ntindle]

i'd love for significant-gravitas to get access :)

[lesderid]

We, celescare, would love to get access too!

[vboginskey]

Count us (ottiinc) in too!

[lucasrcezimbra]

Want early access? Comment below with your org slug

ceztech

[mark-vn]

Is Go support being discussed at all? We're intrigued about this idea but we couldn't fully use it until it supports both JavaScript and Go at minimum.

[Dhrumil-Sentry]

We will support more SDKs including Go 😄 , we're just starting with JS and Python so we can iterate on the UX based on early feedback and then roll it out more widely to other SDK communities

[Dhrumil-Sentry]

Hi Everyone !!

We have rolled out Logs to everyone who asked for access on this discussion or emailed us! 🚀 🚀

You should see this under Explore->Logs in the UX

To get started, you will need to make a few (small) changes to your code. Setup Instructions are here:

Javascript instructions
Python instructions

If you have questions or feedback, we’d love to hear from you - You can also join us on Discord to chat with us live

[tryforceful]

If it's still possible to be added to the list, can hde be added to the early access for the feature? 🙏🏼

[Dhrumil-Sentry]

@tryforceful - We just enabled the feature for your org, please let us know if you have any feedback/questions

[sgarner]

Could org equalogic be added please?

Also I wish to second the request for Vector support. It is more reliable to ship logs from process output rather than relying entirely on an SDK-based integration in application code; this allows logging of startup errors that occur before app initialisation, for example. Plus there's all kinds of server processes (web servers, databases, etc) that users may want to capture logs from but which aren't their own source code.

[Dhrumil-Sentry]

@sgarner We added your org to the Beta list so you should be able to get started !

Thanks for your feedback about Vector, We're focussing on application logs first so developers have all their code related telemetry well connected in Sentry but we will revisit support for other use cases like post that

[Dhrumil-Sentry]

Hi All,

We're iterating based on your feedback ! So please keep the feedback coming 🙏

We've shipped the following today:

• Saved the state of the logs table based on your column selection preferences (You can reset to defaults too)
• The Logs table will always be sorted by latest timestamp
• We caught a bug in Environment filtering - It was related to the JS SDK and we'll have an SDK release for that soon

Next set of items we're looking at

• Allowing auto refresh in the UX so you continue seeing latest logs
• Support for count based charts
• Winston and Pino SDK integrations for JS

Lots more to come!

[sgarner]

Keen to see the Winston integration!