HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
getsentry
sentry
Python2012–2026
getsentry / sentry

sentry

Developer-first error tracking and performance monitoring

60Distinct people
88Mentions
0Explicit recommenders
45.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Developer-first error tracking and performance monitoring

GitHub

Where it is used

  • GitLab — GitLab uses Sentry to monitor frontend errors and performance on GitLab.com. Their production site is configured to send data to a GitLab-managed Sentry instance. Source

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 4:01:40 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year88 dated mentions

Observed mentions: 2012-10-01 16:28:41 UTC to 2026-02-07 15:56:46 UTC.

0510152012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 13 mentions; 0 submissions, 13 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC303
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC707
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC413
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC707
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC13013
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC615
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC808
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC716
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC303
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC606
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC505
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC808
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC615
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC404
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Users and logs provide clues. Sentry provides answers. What's Sentry? Sentry is the debugging platform that helps every developer detect, trace, and fix issues. Code breaks, fix it faster. Official Sentry SDKs Resources Documentation Discussions (Bugs, feature requests, general questions) Discord Contributing Bug Tracker Code Transifex (Translate Sentry!)
Read the full README on GitHub

What Hacker News says

6 sources
Sentry | Growth Engineer | San Francisco | Full time, on-site https://sentry.io Sentry is error logging. We're 100% BSD-licensed open source (https://github.com/getsentry/sentry). We're mostly Python and JS, with a dash of Rust. Sentry is deployed at just about every major technology company (teams at Dropbox, Uber, Airbnb, Pinterest, Twitter, Atlassian, Microsoft, Apple, etc). While Sentry is over 40 people, the growth team is small (3 people!) but focused. All of us are technical (everyone commits code), analytical (you measure and present your experiments), and organized (we are our own PMs). In people, we prefer action over pontification, honesty over polish. If you like developer tools, open source, and experimenting with SaaS economics, message me or apply below. I'm eric@. Growth engineer: https://sentry.io/jobs/807418/ We're also
Read the rest
hiring across the board engineering and some business positions. https://sentry.io/jobs/
In Ask HN: Who is hiring? (October 2017)
Sentry | San Francisco | Full-time, onsite | https://sentry.io | https://github.com/getsentry/sentry Sentry is an open source crash reporting tool trusted by thousands of organizations to notify them of software errors, and provide them with the debugging information and tools they need to resolve them. We are looking for experienced candidates in product engineering, operations, growth, and design. If you'd like to join a scrappy team (27 employees) that builds transparent, open software, we'd like to hear from you. More information here: https://sentry.io/jobs/
In Ask HN: Who is hiring? (April 2017)
I'm not sure, but you can look at GitLab, WordPress, and Sentry[1]. All of those can be run fairly seamlessly with a little bit of research. All of them have customer bases who choose to use the hosted option. There are some pros to the paid/hosted option that can never be replicated by self-hosting: - someone else handles crashes, bugs, and other emergencies - economies of scale (large, purpose-built operations with costs shared my many customers) - free (or cheap) customer support The biggest reason I see people moving to self-hosted options is to keep their data private. 1. https://github.com/getsentry/sentry
In Ask HN: Why isn't there more open source SaaS?
Sentry | San Francisco | Full-time, onsite | https://sentry.io | https://github.com/getsentry/sentry Sentry is an open source crash reporting tool trusted by thousands of organizations to notify them of software errors, and provide them with the debugging information and tools they need to resolve them. We are looking for experienced candidates in product engineering, operations, growth, and visual design. If you'd like to join a scrappy team (25 employees) that builds transparent, open software, we'd like to hear from you. More information here: https://sentry.io/jobs/
In Ask HN: Who is hiring? (February 2017)

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.