sentry-javascript VS relay

I hope this tone comes across correctly as just a suggestion: I get a lot of mileage out of the "Send Feedback" option in DDG, which they claim actual humans do read. It can help move bug reports out of these HN threads into a more context-aware flow, and also makes me feel like any bad outcome has the possibility of improving, unlike systems that don't provide a "I feel bad about this experience" button

If you were thus inclined, https://gitlab.com/glitchtip/glitchtip#glitchtip is the actual open source Sentry implementation which (as far as I know) would enable gluing https://docs.sentry.io/platforms/javascript/user-feedback/#u... to the search results (which itself is still MIT: https://github.com/getsentry/sentry-javascript/blob/7.102.1/... )

Sentry JavaScript - Sentry, renowned for its comprehensive solutions in frontend monitoring and error logging, recently adopted Nx for their official JavaScript SDK. This move integrates Nx's capabilities into their monorepo, containing packages for popular frontend and Node.js backend integrations. They also published a blog post on the benefits they've seen following the adoption of Nx in their monorepo (hint: reducing CI times by 35%).

Running Sentry Wizard... version: 3.13.0 | sentry-cli version: 1.75.2 Sentry Wizard will help you to configure your project Thank you for using Sentry :) Skipping connection to Sentry due files already patched ┌ Sentry Next.js Wizard │ ◇ ────────────────────────────────────────────────────────────────────────────╮ │ │ │ The Sentry Next.js Wizard will help you set up Sentry for your application. │ │ Thank you for using Sentry :) │ │ │ │ Version: 3.13.0 │ │ │ ├───────────────────────────────────────────────────────────────────────────────╯ │ ◇ Are you using Sentry SaaS or self-hosted Sentry? │ Sentry SaaS (sentry.io) │ ◇ Do you already have a Sentry account? │ Yes │ ● If the browser window didn't open automatically, please open the following link to log into Sentry: │ │ https://sentry.io/account/settings/wizard/authtoken123/ │ ◇ Login complete. │ ◇ Select your Sentry project. │ myproject-126kk132c/javascript-nextjs-f9 │ ◇ Installed @sentry/nextjs with NPM. │ ◆ Created fresh sentry.server.config.ts. │ ◆ Created fresh sentry.client.config.ts. │ ◆ Created fresh sentry.edge.config.ts. │ ◆ Added Sentry configuration to next.config.js. (you probably want to clean this up a bit!) │ ◆ Created src\app\sentry-example-page\page.jsx. │ ◆ Created src\app\api\sentry-example-api\route.js. │ ◆ Created .sentryclirc with auth token for you to test uploading source maps locally. │ ◆ Added .sentryclirc to .gitignore. │ └ Everything is set up! You can validate your setup by starting your dev environment (`next dev`) and visiting "/sentry-example-page". If you encounter any issues, let us know here: https://github.com/getsentry/sentry-javascript/issues 🎉 Successfully set up Sentry for your project 🎉

We've just started this initiative and have already been able to help Sentry get optimized with task caching and task pipeline optimizations for their workspace!

In addition to the network call data we already attached, that does go through data PII scrubbing on the edges as you mentioned, we're discussing capturing request/response body. We even talked about it today: https://github.com/getsentry/sentry-javascript/issues/7103

Avoiding any PII from getting into the system is always top of mind. And we're considering this as an opt-in regardless of scrubbing on the edge ingestion service.

Add Sentry’s Next.js SDK to your next.js projects.

Get started with Sentry for Electron and drop us a line on GitHub, Twitter, or our Discord. And if you’re new to Sentry, you can try it for free today or write to [email protected] to get started.

Great idea! #4118

It's probable the core will always remain closed. That's both a business and practical decision. However, much like how Sentry have some of their services open-source, we may follow that route.

There's rust stuff too: https://github.com/getsentry/relay

Sentry uses Rust in their backend, check out relay.

Sentry (sentry.io) | senior software engineer, Rust | Vienna, Austria OR Remote (EU) | https://sentry.io/careers/4635809/

As a Senior Software Engineer on our client infrastructure team, you'll join a cross-functional group of Software Engineers that is responsible for the client-facing operation of Sentry. This includes building and maintaining our event ingestion and processing pipeline, most notably Relay (https://github.com/getsentry/relay). This means you will be involved in the design and evolution of both external and internal services, as well as create new mission-critical software at Sentry.

If you like system programming, know Rust (or another systems programming language) and want to work on mission-critical high-volume services, this is the role for you. And your contributions are open source!

Apply here: https://sentry.io/careers/4635809/

Try https://docs.sentry.io/product/relay/

We have no Nim usage in the company. One of our engineers nominated it as something they find personally interesting, and we wanted to give at least a little bit to every project that our employees nominated.

By contrast, we use Rust quite heavily, including our core ingest component: https://github.com/getsentry/relay.

That's why there's such a discrepancy in this case.