Recently, after I switched to FreeBSD on my server, I decided to pay more attention to the temperatures. As I’m using Prometheus with node_exporterthe CPU temperatures are exported as node_cpu_temperature_celsiusautomatically. They didn’t, however, show any values (only NULL). It turned out that the special
I realized that I did status updates for security fixes in NGINX Extended... 1.14 (sic!). The thing is that in the meantime the entire stable 1.16 went through and here we are now, 1.18 is ready. I did communicate subsequent releases on Twitter, but there were a
Latest 3.1.1 update broke a lot for me (fzf integration under ⌃ + R as one example). How to downgrade? Depends on the answer of the following command: brew list --versions fish fish 3.1.0_1 3.1.1 If you see both versions as above, you may just
One of my New Year’s resolution was to get back a bit closer to the lower level parts of Linux. And what’s there lower than the kernel itself? I always preferred vanilla kernel, even when I was fooling around with Gentoo, and this hasn’t changed. In December
I'm following Brendan Gregg's performance-related content for years now. I started when he was still in Joyent, later on I bought his Systems Performance book and I get back to it whenever I'm doing any profiling. Now I follow closely all of the latest
I already briefly wrote about the idea of having dynamically discoverable upstreams in NGINX when I covered the topic of NGINX Extended. With the boom of microservices and containers scattered all over the place there was suddenly a need for something that would serve as a single source of truth.