serverlessmom

Wow it's awesome that a number on a spreadsheet is so big, now to kick back in Ireland's affordable housing, convenient public transport, generous social safety net, and high quality healthcare system.

[Giving money]: helps people significantly improve their living conditions

All Media: is this experiment too extreme and weird to ever try out in practice? We ask these far out kooks if this off-the-wall moonshot could maybe someday happen in a dream land

If you're considering switching, you can definitely spend less by embracing OpenTelemetry. The right solution will depend on how much technical lifting you want to do/how much control you need. SigNoz does metrics, logs, and distributed traces; and has both a self-hosted open source OpenTelemetry backend and dashboard, and a new cloud offering.

There's also Honeycomb if you're more focused on tracing, and Prometheus/Grafana if metrics are what you care about most.

That is super interesting. I'm curious if you'd be interested in sharing more about your .NET experience with OpenTelemetry? There's really not a lot of writing out there, good or bad, about experiences with OTel on .NET

I had no idea that the Panama Canal required fresh water. Peak price being paid for canal passage is $900k

https://podcasts.google.com/?feed=aHR0cHM6Ly92aWRlby1hcGkud3...

Just found that if you're a startup (1-10 employees), it asks you one question and kicks you out

Huawei: "Stopped by one of my haters' funeral today"

Oh neat! (I was here to ask the same question as above) would love to share the project when OTel support is released!

Oooooh this is great feedback. When I started using SigNoz I too was surprised that there was no metrics tab. I wonder what you’d expect to see after clicking it: a list of service names collecting metrics? Or some high-level system wide infra metrics? Let me know!

SigNoz has pretty broad compatibility with whatever docker environment, if you're interested in trying it out you may want to join the community slack and get it working: https://signoz.io/slack

The vicious cycle I see so many teams in is, the costs have gotten so high with SaaS tools, and the management of those costs so poor, that the solution is telling all teams "Don't for gods sake add monitoring to any more services, we can't afford to monitor anything more"

Not only is this a bad way to decide what gets monitored, it's also going to bite you during an outage.

Thank you! I was amazed when I submitted this that it hadn’t already been posted.

Open source is always going to be a major selling point for Observability. Once you get to any scale the lock-in with a closed source SaaS product is going to make your budget HURT.

There's always going to be a large amount of data, especially observability data, that's never used to make significant decisions. However we want high cardinality data both to increase the chance that the information we're storing will be useful, and to make compression and other data management easier. For example if we're storing fully paramaterized URLs as metrics names we'll never be able to consolidate or average that data.

A brief guide with some examples since this seems to come up every time we discuss DIY metrics tools, structured logs, and parsing.

This great line:

This role is truly a Sociotechnical Engineer, in every sense of the term; they will expose the weaknesses of your company in ways you are not prepared for, and they will challenge the status quo in ways that are painful.

Reminds me of the creation of SRE and SRE teams: if they're not able to reform the process, they just end up taking the blame for broken systems. Systemic improvements means some challenging realizations

Kubernetes can slow down deployments massively, often leading to a state where 'working on my machine' is no predictor of a working deploy. This article talks about request-level isolation as a way to test your code on a shared cluster.

Definitely +1 for SigNoz, much more cohesive view of metrics, logs, and traces

that is an interesting case, it almost feels like you ended up with a highly specialized version of logging.

yeah the robustness of the collector is a big deal. I spent my first years in the tech sector working with a closed source agent, it was impossible to get half the features implemented, even with a dedicated team, that customers requested. With the OTel Collector it feels less like a few single-purpose features and more like a universal harvester.

Yeah I think that’s a fair contention: OTel language projects don’t start out with a few “golden signals”

I’ll check out your project tomorrow! Thanks for sharing.

This looks really cool! I'm going to try it out. And a neat stack too. FYI https://flashpost.stevennatera.com/ is performing really oddly on chrome, long flash of unformatted content, laggy scroll. Works fine on Safari.

my user agent:

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36

Seriously though cool project! I signed up and I'll be trying it out Tuesday.

How many of us have fond memories of the sound and sensation of typing on these?

Crowley knew a lot of magic but Yeats new his one weakness: getting kicked down a flight of stairs.

thank you for this! I'm saving this link to check out later!

A lot of my vegan friends really enjoy the meat substitutes- I am a meat eater and the meat substitutes tend to make me pretty nauseous.

Creating more spores from mushrooms is incredibly easy and cost effective, so is creating liquid culture which is a process that allows you to create huge amounts of mycelial growing base you can then introduce to more growth medium(corn syrup and water that's been sterilized).

I agree with this too, I think that the point of the article was to make it as easy to understand for people who aren't as familiar with our fungal friends.

This is the first decent criticism I've actually seen about the show. Netflix scraping for every penny is definitely hurting production value