3 ms·
Practitioner of what? What is a "wide event"? In what context is this concept relevant? It took several sentences before I was even confident that this is somet
by zahlman 2y ago
Practitioner of what? What is a "wide event"? In what context is this concept relevant? It took several sentences before I was even confident that this is something to do with programming.
- djhope99 2y agoIt’s about observability and strongly related to Honeycombs o11y 2.0 vision.
- zahlman 2y agoOkay, so a web search and some looking around gives me https://www.honeycomb.io/frontend-observability https://www.honeycomb.io/frontend-observability. I guess this is something to do with tools for sending telemetry back from web applications and then doing statistics on them and giving the user some nice reports. "Observability" seems like a weird term for that to me, but okay. But I don't understand why not just give the appropriate context in the submission, rather than keeping a title that only makes sense to a very specific niche audience and then not saying up front what the niche is. The concept of an "event" is coherent in many other programming contexts, so the possibility that one could be coherently "wide" is at least plausibly interesting. But then I get there and find myself completely disoriented, and eventually figure out that it's not actually relevant to anything I do. And anyway it looks like a lot of this jargon is really just not necessary to convey the core ideas... ?
- jitl 2y agoIf the entire contents of the article was in the title, you’d still have to read all the words
- zahlman 2y agoIf the title had said something like "A guide to using Wide Events in website telemetry for [insert objective here]", I wouldn't have had the original objection.
- valyala 2y agoWide events aren't limited to website analytics. Thy are useful for observability of any application types - databases, services, microservices, web servers, application servers, mobile apps, industrial apps, IoT, etc.
- Etheryte 2y agoThey link to three separate articles right at the start that cover all of this. Not every article needs to start from first principles. You wouldn't expect an article about a new Postgres version to start with what databases are and why someone would need them.
- zahlman 2y ago>Not every article needs to start from first principles. Sure, but it would be nice if title submissions made it feasible to predict the topic category of the article for people who are not already in the relevant niche.
- Etheryte 2y agoWide events are a very well known approach, especially if you do any work with observability, and articles about it have been on the HN front page too. You not knowing about something does not automatically make it a narrow niche.
- zahlman 2y agoFrom my point of view, "it has something to do with web dev" already makes it a niche. And as a rule of thumb, if you're using letter-number-letter abbreviations like "o11y" and assuming everyone knows what you're talking about, you're in a niche. (E.g.: I could parse "i18n" and "l10n" already, but I wouldn't expect random HN readers to. When I first saw "k8s" and looked it up I thought "man, really?".)
- antonvs 2y agoNone of this is web dev specific. It applies most strongly to distributed systems, of which web systems are a subset, but in principle it can apply to any system with non-trivial requirements around logging and metrics.
- cookie_monsta 2y agoI felt like I got the gist after the first two: > Adopting Wide Event-style instrumentation has been one of the highest-leverage changes I’ve made in my engineering career. The feedback loop on all my changes tightened and debugging systems became so much easier.
- zahlman 2y ago>I felt like I got the gist after the first two: What I get is: here's a thing that made a big improvement to how I debug systems. Except, it turns out that the systems in question are very specific ones. > The tl;dr is that for each unit-of-work in your system (usually, but not always an HTTP request / response) you emit one “event” with all of the information you can collect about that work. Okay, but... as opposed to what? And why is it better this way? >“Event” is an over-loaded term in telemetry so replace that with “log line” or “span” if you like. They are all effectively the same thing. In the programming I do, "event" doesn't mean anything to do with logging or telemetry.
- treyfitty 2y agoThat doesn’t really give an objective definition of what wide events are, just an opinion and example in this one persons life. I had to lookup wide events in the middle of the article, and I can’t say I can viscerally see and feel the benefits the OP was espousing. Just felt like an adderall-fueled dump of information being thrown at me.
- s1mplicissimus 2y agoyou just read an advertisement article and some people don't like you pointing that out. hence the downvotes i assume
- valyala 2y agoWhile the article is written by observability vendor, it contains an excellent information about wide events, without annoying advertisement of the vendor.
- deleted 2y ago[deleted]
- masterj 2y agoIt is not written by an observability vendor, nor is it an advertisement. Source: I wrote it and do not work at an observability vendor: https://jeremymorrell.dev/about/ https://jeremymorrell.dev/about/ (I wrote it mostly so I could stop re-explaining this concept from first-principles and how to go about implementing it over-and-over again )
- esafak 2y ago"[An Observability] Practitioner's Guide to Wide Events" That's how I would have titled it.
- zahlman 2y agoOkay, and why would people who aren't already in the field have any idea about your specific jargon meaning of "observability"? My browser's spellcheck underlines that. My understanding of ordinary English turns it into "the fact, of something which can be observed, that it can be observed" which is... supremely unenlightening. I get that HN isn't appealing to the general population, but the world of programmers etc. is still quite broad.
- esafak 2y agoIt seems to be the primary meaning in software: https://en.wikipedia.org/wiki/Observability_(software) https://en.wikipedia.org/wiki/Observability_(software)
- throw-qqqqq 2y agoYou’ve made a lot of critical comments here. You are obviously the one who is not understanding or is perhaps misunderstanding something. Observability is a pretty standard term in software development. Events have nothing per se to do with logging or tracing, but you can visualize/trace events with logs/spans. From my perspective, you seem to misunderstand a lot in the article, I am not judging you for that, just observing this. I suggest you try to understand the gist of the article instead of scolding the language used.