“Hands up if you’re using #flamegraphs ” - 80% of the room #sre-next
#sre
2 posts1 participant0 posts today
It is completely appropriate that Brendan is speaking with 3 adorable plushies on the podium (of the conference mascot, a penguin wearing a frog hat) #sre-next
What tools do you use for your on-host #FreeBSD|#BSD system metrics collection and monitoring? #Sysadmin #DevOps #SRE #Monitoring #Systems #Observability #Metrics
Yesterday I was suddenly fired. Not a RIF. No PIP. All signals pointed in the opposite direction. "Your skills are no longer needed" just out of the fucking blue.
Last night I had the first nightmare I've had in well over a year, if not more. This is the 11th time I have been kicked from a company. And that's the part that's hitting me the hardest.
(psst I am looking for a job!)
I'm looking for some people to help me collaborate on writing technical documentation for Django, Python and Debain.
There will be image diagrams that help convey the layer of abstraction to think in to bring django to production while managed with systemd
If that is interesting, please interact with this post.
It drives me fucking bananas that SREs at my company are not considered Engineers and are not included in DevEx. On purpose. For the love of all that's holy!!!!!!!1
Brought to you by: a longish motivational thing the VP of Engineering dropped in their channel today that really showed some care for helping people in their careers and learn.
But it's that this stuff was made explicit, by a leader, that really sets it apart and illustrates how dysfunctional the TechOps side of the org is growing without any leadership. They've flattened the entire thing out so that managers are reporting directly to the CTO and are taking on 10-15 reports, minimum. It's a ticket factory, not a collaboration.
Dear Fedi,
For 3 years, I've been working with friends from the #FOSS world as a team of freelancers and it's been great: we love what we do and our clients are happy and stay with us for years.
But the terrible state of the world has badly affected our clients financially, and we find ourselves suddenly in need of more #work
We focus on systems design, development, and administration. We offer SRE-level quality and processes for companies that cannot afford a whole #SRE team
Boosts welcomed
#OverUnder 025 with @monospace !
He share his point of view on:
- Split #keyboards
-#Arch Linux
- #Fish the shell
- #DevOps
- #Cider
#blog #fediverse #mastodon #GNU #Shell #Linux #SRE #MechanicalKeyboards
#100DaysToOffload : 068/100
lazybea.rsOver/Under #25 with Jochen Lillich
More from 
Hyde 
I always appreciate a good write-up of outages and Google had one for their outage on the 12th. They put in new policies around quota handling, but then that had some unexpected side effects. Since they didn't have a feature flag to turn it off quickly, recovery took a little bit longer.
One reason I like this is it makes you think of what features need to go into APIs/services and how everything fits together. Google runs planet-scale infrastructure, but I think there are takeaways for projects of any size in write-ups like these.
https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW
status.cloud.google.comGoogle Cloud Service Health
Learn how you can prioritize service incident troubleshooting with #opensource by sorting applications by SLO risk in one view (automatically populated with #eBPF! 
)
Try it out for yourself: https://t.ly/__UBr
New #DevOps or #SRE team members overwhelmed by observability? This cheatsheet has them covered 
Learn more about critical observability concepts and their relation to #Coroot, an #opensource tool that can improve uptime: https://t.ly/Vdj4Z
Looking for a remote position in #OpenSource? Browse hundreds of jobs in technical and non-technical roles on #OSJH
https://opensourcejobhub.com/jobs/?q=remote&utm_source=mosjh
#career #sysadmin #engineer #sales #security #marketing #developer #DevSecOps #SRE #FOSS
Effortlessly improve system uptime, optimize workloads, and catch availability and security risks. Explore no-code, automatically configured system visibility with #RCA insights, #opensource or enterprise.
Dig into the #Coroot Enterprise sandbox: https://t.ly/gU-2I
Map your services completely with #FOSS: https://n9.cl/kfm0rw
Manually digging through metrics, logs, and traces can be time consuming and prolong expensive outages. Learn how you can improve service uptime with automatic, #AI-powered #RCA: https://t.ly/LBjEM
Learn essential eBPF #Linux command line tools to improve your service observability with #opensource: https://t.ly/wNy6b
Check out #Coroot (we’re #FOSS!) to turn manual service analysis into instant root cause insights. Resolve issues and deploy faster with #eBPF: https://n9.cl/kfm0rw
Replied in thread
System Administration
Week 12, System Security IV: Crypto means #Cryptography
In this video, we discuss the three areas cryptography can provide threat mitigations in -- confidentiality, integrity, and authenticity -- and what some common pitfalls are with each.
Replied in thread
System Administration
Week 12, System Security III: From the Attack Life Cycle to Zero Trust
In this video, we continue approaching System Security from an attacker's point of view by understanding their common processes, following the Attack Life Cycle (with doggos!) and then identifying how our defenses, supported by the Zero Trust model, can interrupt each stage.
Replied in thread
System Administration
Week 12, System Security II: Defining a Threat Model
In this video, we look at the concept of a Threat Model and how the attack economics may shift based on your adversaries capabilities and motives. We introduce the STRIDE and DREAD models and draw a few circles, of course.
Replied in thread
System Administration
Week 12, System Security I: Risk Assessment
In this video, we begin our dedicated discussion of System Security with a look back at how we've talked about security relevant aspects in previous videos and then moving forward to defining how we can begin to assess risk rather than attempt to "secure" a system.
