Benjamin Coe @BenjaminCoe

Co-founded Attachments(dot)me, early employee at @npmjs, maintains yargs and Istanbul, created https://t.co/9qJ6kBLbDe. Product at @getsentry. github.com/bcoe Kitchener, Canada Joined March 2009

Tweets

6K
Followers

3K
Following

736
Likes

6K

Benjamin Coe @BenjaminCoe

3 months ago

@evanpurkhiser @g33kdev @sentry @g33kdev I installed the plugin and still seemed to have the /sentry-instrument-logging command. The skill itself was moved into a legacy folder in the repo. Are you getting a different experience? I'd love to know if you were given some good suggestions in your codebase.

0 0 0 42 0

View Details

Benjamin Coe @BenjaminCoe

3 months ago

@g33kdev @sentry I will get the link in the article updated and share.

1 0 2 42 0

View Details

Benjamin Coe @BenjaminCoe

3 months ago

@lesv I like that idea. Almost like having a mini-trace stored with each log in your application?

2 0 2 65 0

View Details

Benjamin Coe @BenjaminCoe

3 months ago

I've spent *maybe too much* time thinking about logging. At npm, logging was my main tool for debugging the registry. At Google, I learned to log proactively so debugging rarely required a deployment. Now, as a PM at Sentry, I get to learn how developers across many companies think about logging. I've collected my favourite lessons: blog.sentry.io/logging-best-p…

2 6 19 2K 8

View Details

Benjamin Coe @BenjaminCoe

5 months ago

@DanielGriff @dhrumil_parekh @austriker27 @sentry Hey, as @dhrumil_parekh points out, errors are absolutely available on dashboards. You may also be thinking of the project details page, which shows errors, and is available by clicking the org dropdown, in the upper left of Sentry, and choosing projects.

0 0 0 30 0

View Details

Benjamin Coe @BenjaminCoe

5 months ago

argument: dashboards are still applicable in a world where analysis of telemetry is being done with agents. they're just more ephemeral -- perhaps conveying info from a single investigation -- and *way* easier to build. blog.sentry.io/dashboard-upda…

0 0 7 138 0

View Details

Benjamin Coe @BenjaminCoe

5 months ago

@tannerlinsley @aboourka @GavinLiu0606 @sentry @tannerlinsley if you have Sentry set up already for errors, you might also consider enabling tracing, at least temporarily, docs.sentry.io/concepts/key-t… it can be good for spotting a performance outlier like this. hit me up with any questions.

0 0 2 71 1

View Details

Benjamin Coe @BenjaminCoe

5 months ago

with the ability to slice and dice Application Metrics on high cardinality fields, like user, they can answer many product questions. however they don't have features, like funnel analysis, user journeys, that you'd get out of a dedicated product analytics tool. That said, I believe they hit a sweet spot for many developers, being just right for tracking both app health and understanding users.

1 0 0 39 0

View Details

Benjamin Coe @BenjaminCoe

5 months ago

I agree that it's confusing that we called out don't use this for "infrastructure" and have the example of "memory.usage" 😬 To add some nuance, we think that Application Metrics won't be ideal at certain scales of metric collection common when monitoring, say, a giant Kubernetes cluster. Tools like Prometheus rely on pre-aggregation and compaction to collapse many samples into relatively cheap time-series storage, whereas we store a row per metric event. Using Application Metrics to track almost anything is absolutely viable up to a certain scale — we just wouldn’t position them as a replacement for dedicated infrastructure-monitoring systems.

0 0 3 42 0

View Details

Benjamin Coe @BenjaminCoe

5 months ago

Good sign: we immediately relied on Application Metrics @sentry while building them. They're launching today 👏 Why care? • dead simple to instrument • connected to spans, errors, logs → actually see why something’s off the rails • generous free tier — great for hobby projects blog.sentry.io/introducing-ap…

0 3 7 2K 1

View Details

Benjamin Coe @BenjaminCoe

6 months ago

I'm having far too much fun stress testing @sentry's new Application Metrics product. I can't decide if I like the "scrum_token" or "disruption_id" more.

0 1 5 248 0

View Details

Benjamin Coe @BenjaminCoe

6 months ago

@zeeg Jenkins would be a good choice. It's powers Node.js' CI.

0 0 0 44 0

View Details

Benjamin Coe @BenjaminCoe

6 months ago

scientists prove that deep music is the rhythm of the world (2hz = 120bpm). all those vocal samples in club bangers were right! openaccessgovernment.org/natures-univer…

0 0 2 151 0

View Details

Benjamin Coe @BenjaminCoe

6 months ago

👋 hey. our observability products, logs, metrics, tracing, are built with answering high cardinality, user-centric, questions in mind... is this metric, route, etc., slow for bob[at]example.com? We also have session replays, which let you see recordings of full user sessions. Happy to go deeper on any of these topics. Reach out in DM, or in this thread?

1 0 2 188 0

View Details

Benjamin Coe @BenjaminCoe

6 months ago

@Cool_Goose @sentry If it's a "Sentry Built" dashboard, you'll need to duplicate first, then you can edit. If it's your own just click edit. Here's a screenshot from my own project:

1 0 1 47 0

View Details

Benjamin Coe @BenjaminCoe

6 months ago

@bentlegen what does it say about yargs? not a single line of code is AI, but it's pretty sloppy.

0 0 1 70 0

View Details

Benjamin Coe @BenjaminCoe

7 months ago

my team @sentry just released a feature that lets you create killer dashboards for your app with an AI agent 🤖 it honestly feels a lot like magic -- see my example screenshots. If you use @sentry , try the feature out! feedback is appreciated 👏 github.com/getsentry/sent…

0 7 24 4K 9

View Details

Benjamin Coe @BenjaminCoe

7 months ago

@David28717353 @zeeg @sentry Oh, awesome we're fixing this 👏 Is exporting the whole payload as JSON sufficient for you, we're imagining that the JSON export will include all fields, CSV export will be as it is now (the configured fields).

0 0 0 39 0

View Details

Benjamin Coe @BenjaminCoe

7 months ago

@David28717353 @zeeg @sentry Hey, Can you give me some examples of attributes that are being dropped. Perhaps by sharing the payload set in Vercel logs and the payload you see in Sentry? We're trying to reproduce and having trouble. Feel free to send me a private message.