Neil Manvar

Solutions Engineering Manager at (@getsentry)

[Neil Manvar @ndmanvar]

@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) [:

[Neil Manvar @ndmanvar]

@kentcdodds @getsentry aw yahhhhh bammm

[Node Congress🔥March 26 & 27, 2026 @NodeCongress]

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

[Neil Manvar @ndmanvar]

@vesper8 @getsentry @vueschool Re. __SENTRY_RELEASE__ -> I believe that should be defined if `release` is specified when Sentry.init'ing (https://t.co/7m3KTyTLUc)

[Neil Manvar @ndmanvar]

@vesper8 @getsentry @vueschool re. vue-cli -> here is an example that might help -> https://t.co/TDZnZnLyL7

[Neil Manvar @ndmanvar]

@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)

[Neil Manvar @ndmanvar]

@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 (:

[Neil Manvar @ndmanvar]

@getajobmike @honeybadgerapp https://t.co/1KoKRKgZdJ shows whats up in node/js land

[Neil Manvar @ndmanvar]

@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

[Neil Manvar @ndmanvar]

@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 (:

[Neil Manvar @ndmanvar]

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

[Neil Manvar @ndmanvar]

@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 (:

[Neil Manvar @ndmanvar]

@Cypress_io @OpenViewVenture Congratulations Cypress team!

[Neil Manvar @ndmanvar]

@cnorthwood @tdp_org @getsentry https://t.co/QVUALplfWk

[Neil Manvar @ndmanvar]

@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

[Neil Manvar @ndmanvar]

using angular? if yes, then using sentry? if not, then join in at https://t.co/w4lHbDJpK2 (I'll be stepping through how to get that all wired up)

[Neil Manvar @ndmanvar]

thats right. just a few more days (:

[Sentry @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

[Neil Manvar @ndmanvar]

@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

[Neil Manvar @ndmanvar]

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

[Neil Manvar @ndmanvar]

@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 (: