Neil Manvar

@dhrumil_parekh @avindrafernando @kentcdodds @getsentry In regards to your exact ask ("common issues based on geo"), you can search/filter on geo.* to find relevant issues (in both issues + discover page) [:

@avindrafernando @kentcdodds @getsentry You can easily build such analytics with @getsentry's Discover feature: docs.sentry.io/product/discov… Here's a sample query that shows error and user counts of top issues users face by geo codes

For real though, @getsentry > logs

@kentcdodds @getsentry aw yahhhhh bammm

I've finally fixed my integration with @getsentry on my personal site and gosh why did I wait so long to do that? This thing's incredible.

Join @ndmanvar's pro workshop "Tracking Errors and Slowdowns in Node + JavaScript Using Sentry". February 15, 19:00-20:00 CET 🎟 Register now with your Full ticket! #NodeCongress

@vesper8 @getsentry @vueschool Re. __SENTRY_RELEASE__ -> I believe that should be defined if `release` is specified when Sentry.init'ing (docs.sentry.io/platforms/java…)

@getsentry @vueschool Nice tutorial but it would have been much more useful if you also explained how to set it up with vue-cli and not only with vite. I am struggling to figure out how to make the sourcemaps hidden with the vue-cli build, and how to define the __SENTRY_RELEASE__ variable

Our course on @Vueschool is live! Get a full introduction into Application Monitoring in Vue.js with Sentry in just under an hour. Share with your favorite Vue developer. buff.ly/3fHKKoA

@vesper8 @getsentry @vueschool re. vue-cli -> here is an example that might help -> github.com/sentry-demos/v…

@jeanqasaur workflow is important for developers, they don't want to sit in a tool and query/graph-watch. figure out the root cause and move on (alert -> relevant context -> fix -> than back to developing)

When people think about/look for dev tools, they often have simplification tools in mind. But for some purposes, what you need is actually a complexity-embracing tool. For example: monitoring can only take you so far. At some point, you need something to help you root cause.

When we talk about "developer experience," we really need to separate dev tools into two categories: ones that simplify things away and ones that help developers engage with complexity. DX needs are different for simplification tools vs complexity-embracing tools! Thread. 👇

@jeanqasaur warning / shameless plug (sentry.io) here: The way I see monitoring for developers (especially at the code/application-layer level), is that it should tell you what happened in the aggregate + all the relevant in-app context + even surface commit that caused it (:

@getajobmike @honeybadgerapp @sentry/browser-vs-honeybadger-js" target="_blank" rel="nofollow noopener">npmtrends.com/raven-js-vs-ra… shows whats up in node/js land

@orlyjamie @rollbar @raygunio @getsentry @datadoghq Sentry can deploy a single-tenant instance in the AU region - sentry.io/resources/sing… Also, if it's just that sensitive-data/PII can't make it out of that region, then you could have the events sent to a relay-hosted in AU which would scrub and forward accordingly

@daniel_levine @PredragGruevski @bahmutov @filip_hric @getsentry yep, and @getsentry also has a basic-screen-recording integration/solution for browser-js as well (docs.sentry.io/platforms/java…). Not as advanced/full-featured as sessionstack+fullstory but does get you the session replay video (:

@PredragGruevski @bahmutov @filip_hric @getsentry In fairness, @getsentry logs breadcrumbs leading to the error and does integrate with tools like sessionstack and fullstory to give you both!

Never see someone do the math on this 😂 great talk @bahmutov

@craigcartmell1 @getsentry also check both org + project settings (since data scrubbing can be configured at both levels)

Anyone know how to stop @getsentry from scrubbing none data sensitive info in logs? Even without data scrubbing enabled, I'm trying to track down an AWS exception code but it's showing [Filtered].

@tonydehnke @getsentry yep! it's b/c the sourcemapped and minified issues were merged, and now those fingerprints are all associated to one issue. When you're pulling you issue it usually loads the latest event which may or may not be source mapped b/c of merge You're hypothesis was correct (:

Any @getsentry pros out there with experience on getting source maps to work reliably? We seem to be having some issues with getting them working consistently. github.com/getsentry/sent… #sentry #javascript #js

@Cypress_io @OpenViewVenture Congratulations Cypress team!

We’re thrilled to announce our Series B! 🎉 $40M led by @OpenViewVenture to expand our testing platform and lead the way toward the next generation of testing. prn.to/37mFrry

@cnorthwood @tdp_org @getsentry docs.sentry.io/product/accoun…

@cnorthwood @tdp_org @getsentry Hm.. hoping this webinar/video helps -> sentry.io/resources/how-… (goes over some approaches to eliminating the noise + making sure actionable stuff makes it to sentry

using angular? if yes, then using sentry? if not, then join in at ng-conf.org/2020/sessions/… (I'll be stepping through how to get that all wired up)

thats right. just a few more days (:

@Anka213 @getsentry issue-state: ignore, this way they still come in and are saved but you're not alerted on them (: We also cover ignore conditionally / snooze in the webinar! - sentry.io/_/resources/ab… - #ignore" target="_blank" rel="nofollow noopener">docs.sentry.io/workflow/alert…

@getsentry Regarding point one, what is your recommendation about what to do with inactionable errors and logs that you still want to save, for the sake of statistics and context?

Your code is going to break — it's inevitable. We'll help you get it working again before anyone notices. Join us (digitally) on Thursday (5/28) at 10 am PST as we walk you through how to make the most of Sentry with our best practices and configurations. hubs.ly/H0qGV6h0

nice to meet you @starbuxman! thanks for taking the time today and discussing Sentry in spring-boot (:

@kwuchu @getsentry Hi @kwuchu! My name is Neil and I work at Sentry. You can filter/drop the event using the beforeSend hook (maybe based on stacktrace), then the error would not be shot up + consume quota. #before-send" target="_blank" rel="nofollow noopener">docs.sentry.io/error-reportin… #filter-events--custom-logic" target="_blank" rel="nofollow noopener">docs.sentry.io/platforms/java… Happy to provide more information/discuss (:

Downsides of letting users use JavaScript on their page. If they write it wrong and their site gets a lot of traffic, it blows through your @getsentry quota. 😭 Got 16k exceptions cause of it, free quota is 10k. RIP me.