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 (https://t.co/7m3KTyTLUc)
@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)
@jeanqasaur warning / shameless plug (https://t.co/PIPiznJAtf) 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 (:
@orlyjamie@rollbar@raygunio@getsentry@datadoghq Sentry can deploy a single-tenant instance in the AU region - https://t.co/FRzpeqnfoq
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 (https://t.co/O6GGyQ2tKV). Not as advanced/full-featured as sessionstack+fullstory but does get you the session replay video (:
@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 (:
@cnorthwood @tdp_org @getsentry Hm.. hoping this webinar/video helps -> https://t.co/S9TAjXMmF1 (goes over some approaches to eliminating the noise + making sure actionable stuff makes it to sentry
Every developer’s been there: a user’s spinning pinwheel turns into your own personal panic spiral. During Sentry’s Future of Frontend’s Am I Normal? session, you’ll listen to top developers from Github, Twitch, and Riot Games talk through their issues. https://t.co/zstZBGKhkS
@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!
- https://t.co/zY7EQdLHBN
- https://t.co/fJEzonKbdL
@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.
https://t.co/ZOvZl8KQER
https://t.co/6WjWD9KLXt
Happy to provide more information/discuss (: