サクサク読めて、アプリ限定の機能も多数！
トップへ戻る
参議院選挙2025
blog.sentry.io
Unless you’ve been living under a rock, “MCP” is probably a term you’ve heard thrown around in the AI space. Each of the editors and LLM providers have been racing to add and enhance their MCP support. Sentry was fortunate enough to be included in Anthropics release announcements for MCP. VS Code and GitHub Copilot recently expanded their MCP options, Cursor just released their 1.0 (congratulation
Introducing the Functional Source License: Freedom without Free-riding Sentry started life in 2008 as an unlicensed, 71-line Django plugin. The next year we began publishing it under BSD-3, and ten years later we switched to the Business Source License (BSL or BUSL). Last year we purchased Codecov, and a few months ago we published it under BSL/BUSL as well. That led to some vigorous debate becaus
We released a critical security advisory today for Sentry’s Next.js SDK. In the SDK versions 7.26.0-7.76.0 (inclusive), when the tunnelRoute option is enabled, this vulnerability allows malicious actors to forge requests and responses from your Next.js application (this is commonly understood as Server-side Request Forgery - SSRF). We have no evidence that this vulnerability was exploited. We have
Sentry Profiling now supports Browser Javascript, React Native, and Ruby Profiling is an essential component of a developer’s toolkit for identifying and addressing the thorniest performance bottlenecks. Whether you’re a backend developer looking to cut down cloud infrastructure costs, a frontend developer trying to speed up page load times, or a mobile app developer working to ensure smooth scro
Yesterday we announced that Codecov is now “Open Source”, and we messed up in two ways: We wrongly used the term Open Source; while unintentional, we should have known better We let our emotions get the best of trying to explain our position, rather than stepping back and addressing the problem I want to talk about both of these, how we made the mistake, why it’s important to us, and what we plan
If you're using Sentry for JavaScript error tracking, you might be suffering from a common affliction: noisy, low-value errors that make it harder for you and your team to identify high-priority issues. This happens because browser JavaScript is perhaps the single most complex environment from which to capture errors – because it's not just one environment! There are multiple major browsers, JavaS
We like to think Sentry is an interesting and, in many ways, unique company. We started as an open source project which operated as a small business in our spare time for many years. While we look pretty similar to every other tech company these days, we've always maintained our commitment to building a viable business, and doing it with open source. What does Open Source actually mean? It's a fre
Sentry processes billions of errors every month. We've been able to scale most of our systems, but in the last few months, one component has stood out as a computational chokepoint: Python's source map processing. Starting last week, the infrastructure team decided to investigate the scaling shortcomings of our source map processing. Our Javascript client has jumped to become our most popular inte
onerror is a special browser event that fires whenever an uncaught JavaScript error has been thrown. It’s one of the easiest ways to log client-side errors and report them to your servers. It’s also one of the major mechanisms by which Sentry’s client JavaScript integration (raven-js) works. You listen to the onerror event by assigning a function to window.onerror: window.onerror = function (msg,
These days, the code you use to write your application isn’t usually the same code that’s deployed in production and interpreted by browsers. Perhaps you’re writing your source code in a language that “compiles” to JavaScript – like CoffeeScript, TypeScript, or the latest standards-body-approved version of JavaScript, ECMAScript 2015 (ES6). Or perhaps more likely, you’re minifying your source code
After nearly 2 months of beta testing, bug fixing, and implementing feedback-driven improvements, we're excited to announce that we have finally pushed the latest version of Sentry live for everybody. In case you haven't tried Sentry 8 yet, below we're going to highlight some of the new things you'll find to improve your [error monitoring]. And hang in there - there's a lot of them. The first thin
このページを最初にブックマークしてみませんか？
『blog.sentry.io』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
