neilgilbert.bsky.social
17 posts
14 followers
55 following
Conversation Starter
comment in response to
post
Then mobile development, merge into one massive app, released every 2 weeks and no one knows when it's actually in prod so no one really monitors and people are reluctant to roll back.... Observability is non-existent. Surely we can do better!
comment in response to
post
After being paged at 1 in the morning today.... Use SLO's people!, Also the mind shift needs to be a company one rather than just a team (ask me how I know 😴)
comment in response to
post
Helped by other great startups such as clickhouse
comment in response to
post
Bring back Ms visual SourceSafe - when people would forget to check in files, go on holiday meaning you can't work on the project... Good times ,
comment in response to
post
This makes me feel old
comment in response to
post
I'll have to check with the powers that be, but let's make this happen in the new year! Thanks as ever with your help on this 🙏
comment in response to
post
Imagine making cars without garages/mechanics/dealerships etc
comment in response to
post
Software isn't only about creating code! (Amongst other things) Someone has to understand it and support it during its lifetime in production
comment in response to
post
It's the linear bit I think. We aggregate all the 'info', request/response logs into one. I'm not sure that's needed if you can group them by traceid or if that even falls under the definition of canonical logging.
comment in response to
post
I think I need to fire up some other tooling to see how it works.
I know I'm trying to shoe horn something that possibly isn't the right fit but trying in ways to push things forward.
I'm just struggling to get my head around it with the current setup and if it can bring value.
comment in response to
post
I just assumed that you would sample within a domain. If you want a trace say end to end of a customer journey then, well, yeah, good luck I guess!
comment in response to
post
It doesn't help when the o11y tooling we use is geared towards logging over tracing (more functionality etc 🐕)
comment in response to
post
I'd really like to see examples of how people are doing this in DotNet with Logs (if at all)
comment in response to
post
I'm struggling to get wide logs in DotNet. To keep the context throughout a request and log everything at the end, it just doesn't feel like a natural fit. We have a package that aggregates all log events into one but it feels a bit wrong.
Tracing is the answer but it's hard to get folks to shift.