People are misinterpreting me, thinking I mean that it's not even possible to intermingle equipment. That is not the case.
The specific issue I ran into was that I had a non-ubuiqiti router and AP on my network, and there was absolutely no way to set firewall rules on the Ubiquiti gateway for any clients connected through the non-ubiquiti equipment. This should obviously not be a problem. The gateway provided those clients IP addresses through DHCP and they are in its ARP table, so it should be supported.
Yelp | Site Reliability Engineer | San Francisco or London | Onsite | Full time
We’re looking for people with a passion for uptime - people with the tenacity to make meaningful contributions, solve hard problems, and have fun while doing it!
You’ll design monitoring and alerting patterns that keep us stable. You’ll build autoscaling infrastructure to meet our ever-increasing demand. You’ll empower engineers with the tools to safely push code multiple times a day. And you’ll play a key role in keeping Yelp fast, stable and growing.
I do the same using jrnl (http://maebert.github.io/jrnl), which lets you do things like star, tag, and view entries from specific days - while still keeping everything in a plain text file.
And while you're roughing it with a temporary passport and a cheap windows laptop, count your blessings:
I'd bet >10% of the readers here have had any of the following: Cancer or similar shitty disease or disability in self or family, lost >50.000$ in natural disaster, accident or financial turmoil and/or are in a permanent state of stress due to job, relationships, legal battles or similar.
PL is an enormous library so its really superseded by a few different libraries. The stuff I used most often were the functional tools and Moses (https://github.com/Yonaba/Moses/) blows the doors off of PL in that regard.
This is a summary / cheat-sheet for diagnosing performance problems with the "USE" method. It's explained in much more detail here: http://www.brendangregg.com/usemethod.html
Worth checking out the rest of the site too, really useful stuff for performance engineers.
For reference, the definitions are:
* utilization: the average time that the resource was busy servicing work
* saturation: the degree to which the resource has extra work which it can't service, often queued
