Sentry

Make your logs queryable, not just readable

console.log("here") doesn’t cut it in production. Structured logs do.

Use this tutorial to connect LogTape + Sentry and make every log searchable, queryable, and connected to your traces. When something breaks, you’ll get the full picture: log events, error context, and Session Replay, all linked by trace ID.

See the full recipe ➡️

Free Workshop: Debug React Apps With AI From Dev to Prod

Seer is Sentry’s AI debugging agent. It root causes errors, suggests fixes, and catches bugs in code review before they hit production.

This free 4-part workshop series covers the full workflow: production error triage, root cause analysis, AI code review, and debugging via MCP. Each session goes hands-on with a specific feature so you can actually set it up and use it in your own projects. No fluff, just walkthroughs you can follow along with.

Register today.

Next.js Source Maps: From Random Chunks to Real Code

When Next.js builds your app, it compiles and minifies your code into chunks like static/chunks/12345-something.js. When errors happen, your stack traces point there. Not to the code you actually wrote.

This blog walks through how source maps and debug IDs wire things together, and how to configure Sentry to show real file names and line numbers in production.

Read the guide ➡️

Trying to debug a request that touched 5 services? (Partner)

Distributed systems help you move faster…until you have to debug them.

This blog shows how to use Sentry tracing and logging to follow a request end-to-end. You don’t need prior microservices experience to follow these steps.

Read the blog and start fixing