Logs in Sentry 🚀 - Open Beta

[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.

You can find the SDK instructions to send logs here:

JavaScript SDK instructions here.

Python SDK instructions here.

See other supported SDKs here

Just head to Explore->Logs to view your logs !

We're working on supporting more SDKs and will keep this discussion updated as we iterate. 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.

Try Logs in Sentry

Just head to Explore->Logs to view your Logs. You can get started with sending Logs by following SDK 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.

[gg-kialo]

It would be ideal if sentry were a fluentbit output, so I can just change the fluentbit config and get all my logs cluster wide sent to sentry with no application changes.

Only having first-party application logs in sentry would be a real let-down. That would split my logging across two systems. I can barely remember the query syntax for the logging system I use as it is.

[Dhrumil-Sentry]

Thanks a lot for this feedback - Currently, we're focussed on building an application logging solution that is connected to all other telemetry - errors, spans, replays etc via our trace id so developers get the full context needed for debugging their code.

We may support such generic sources in the future but that is not something we're prioritizing until we're able to make these Logs generally available to all our users.

[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 ❤️

[lwpamihiranga]

Hi there,

What is the correct way to send a JSON formatted log and get it parameterized in sentry logs? I'm trying to do that but it is not getting parameterized in sentry. Our current logs are JSON formatted. What is the recommended way to get the logs to sentry in a way that can be parameterized?

I'm using the python SDK. Using the logger function in the SDK is not possible due to we have to update everywhere.

If anyone can give a insight much appreciated!

[AbhiPrasad]

responded here: getsentry/sentry-python#4220 (reply in thread) - we can continue the convo in that thread.

[huven]

It looks like Sentry applies data scrubbing server side, as I see some [Filtered] values. Which is great.

Except, I have one field which I want to exclude from scrubbing, so I've added that to the safe fields in the project, yet it is still being scrubbed. Is that expected behavior or am I doing something wrong?

[colin-sentry]

The safe fields setting should work - is this a sentry-sent field or a custom field?

We are improving the scrubbing logic to include a user-visible reason so that you can see what rule dropped the value. Expect that to land by GA later in this summer.

[huven]

It's a custom field, like in

Sentry.logger.info("...", { my_field: "password" });

[vlad-ampm]

Would there be a possibility to export logs? 👀

[colin-sentry]

We're working on it!

[Dhrumil-Sentry]

We've shipped improvements to the trace waterfall - You could already see all the logs for a given trace id and now you can see the logs associated with a single span as well

We're working on a bunch of stuff right now including allow users to aggregate logs and build dashboards/alerts , live tailing of logs and improved SDK support

So please keep the feedback coming !

[joshdales]

Is this change on the Sentry side or do we need to update the SDK version that we are using?

[Dhrumil-Sentry]

This should just be a Sentry side change, no SDK updates needed

[vlad-ampm]

Would it be possible to permanently delete/remove entities from Sentry logs base on search/filtering criterias? Either via API or via Sentry UI would work. (Question related to GDRP compliance in our case)

[Dhrumil-Sentry]

@vlad-ampm - Currently there is no way to conditionally delete your data in Sentry based on filters - this applies to errors, spans, replays and logs too. If you need to delete data you will need to delete the project

[Jonathanm10]

Hey, at liip-qq I can't see the "Logs" link on the "Explore" menu. I heard it was activated for all users? Thanks for your help

[Dhrumil-Sentry]

@Jonathanm10 Your org is on a pretty old legacy rate plan - Could you please write to [email protected] - they can help update the plan so you have access to the latest features like Logs.

[Jonathanm10]

That was it, thanks a lot!

[Dhrumil-Sentry]

We've rolled out the ability to freely aggregate your logs and build dashboard widgets on them

If you see the "Aggregates" tab you see the results of your aggregations and you can use the >> button to expose the group by and chart controls

You can also create log based widgets for your dashboards

Please let us know if you have any feedback ! We're gonna make the UX better in the coming days

[seth-govalidate]

Will logs have a different quota value than the error reporting? Currently, I'm using SentrySdk.CaptureMessage(.., .., SentryLevel.Info) liberally in my app and we blew through the quota limit on day one. I'm wondering if I can just convert all of those to Logs?

Also, can errors and logs be linked or referenced in anyway? If a user has a bunch of log entries and then they get an unhandled exception, is there anyway those can be seen together vs just comparing users and timestamps manually in both and hoping for the best?

[Dhrumil-Sentry]

Logs will have a different quota from errors. If you don't care about a stacktrace , then you can certainly send these captureMessage() as logs.

Errors and Logs should already be automatically linked together - our SDKs add a trace id and our UX shows the related Logs for the Error in our UX itself - There is a section to see related Logs in our Issues UX. Here's an example :

[Dhrumil-Sentry]

All customers can now create Log based alerts - Business plan customers can also define anomaly detection based alerts for their Log Metrics

Please try this out and let us know if you have any feedback !

[danlamanna]

👋 I'm trying to gauge how much of Sentry Logs is to aid the other things Sentry is good at as opposed to being a wholesale competitor to something like Papertrail.

To what extent is this intended to be used with particularly noisy things like access logs? In particular, if my application is emitting logs to Sentry in lieu of something like Papertrail, can/will it also support exfiltrating those logs to an S3 bucket for more permanent storage (e.g. https://www.papertrail.com/help/permanent-log-archives/)?

Similarly, are there plans for Sentry to be able to be used as a syslog drain to collect logs from services (e.g. https://render.com/docs/log-streams) instead of just applications via SDKs?

I'm trying to see if Sentry logs is adequate for the sort of prototypical Heroku/Render app that is non-trivial but not significant enough to justify an ELK stack setup.

[Dhrumil-Sentry]

Hi - We will be a full fledged logging solution, But we're iterating our way to that goal 😄

Similarly, are there plans for Sentry to be able to be used as a syslog drain to collect logs from services (e.g. https://render.com/docs/log-streams) instead of just applications via SDKs?

We will support log drains - Here's the tracking issue : #96266. We will invest in supporting log drains from other sources too but this work is planned once we are out of the beta sometime in September.

can/will it also support exfiltrating those logs to an S3 bucket for more permanent storage

We don't have specific plans for this but are considering letting users purchase additional retention

[olegsinavski]

Hello! Is there a way to query logs via the API? I can't quite figure out how to do that.. My usecase - exposing sentry errors and logs to a coding agent.

[AbhiPrasad]

Hey @olegsinavski.

Our MCP server should expose logs: https://mcp.sentry.dev/. If you connect your coding agent to sentry via the MCP you'll get this working.

We're also actively building this into sentry-cli: getsentry/sentry-cli#2661. Please subscribe to that issue so you know when that will be released.

[Dhrumil-Sentry]

Hi All,

We just wanted to publish a reminder note that you need to send a Log message/body when you send Logs to Sentry. Sending empty strings or null value as the log message is not supported and will lead to Logs getting dropped as invalid events on the Sentry server side.

[Syed-RI]

Any updates on the business model? i.e. Pricing, quota and retention policy?

[Dhrumil-Sentry]

Pricing discussions are ongoing but can share the following:

• A free volume of logs will be included in each plan
• Sentry intends to give beta customers notice before logs are available for purchase to aide in organizational decision making
• Log pricing will be based on per Gb usage for 30 days retention (No additional charges for querying or alerting)

We're still working through the per Gb price point and will share it once it's available

[Dhrumil-Sentry]

We just released live auto-refresh for Logs ! Toggle on the auto-refresh option and see your logs come in live. Please let us know if you have any feedback

Logs-AutoRefresh.mp4

[huven]

Nice. The pull-down to refresh (manually) seems not to work anymore, was that intended?

[vlad-ampm]

Is it possible to "subscribe" to a certain log entries and get notified (e.g. in browser) when a certain event is there? Let's say I want to be notified when a log entry containing "payment" in its message arrives.

[Dhrumil-Sentry]

Hi, You can create an alert rule that notifies you whenever a certain threshold of matching logs is observed in a time interval