Recently we noticed a part of our web application wasn't working. After some hours of looking into it (it's an old, convoluted application), it became clear another part of the application timed out trying to get a connection from the db connection pool.

We call db admins, they respond "oh yeah looks like the DB CPUs are at 100% load. I'll do something about it." and a short while later everything was working. So now I think, our hours of looking into it and a lot of people not being able to work could have been avoided if the DB admins had some form of alerting. But also we could improve our monitoring too, had we tracked calls made to our DB.

Question: Do you think I should call the DB guys, telling them they need alerting, or should I add tracing/monitoring around our DB calls, or both? Do you think I should consider any additional actions I haven't thought of?

Rant about other people ranting about people ranting about Microsoft/GitHub, you really need to stop telling people about what they're allowed to rant about, your rants about other people's rants are taking over devRant and it's annoying as hell!
We get it, you're against people ranting about certain topics, but at some point you've got to move on.

(How meta can we get?)

Rust, because if we can eliminate all security issues because of buffer overflows or other memory-related problems without a GC and still be as fast as with C, that would be pretty dope for everyone.

Just found this little duck on my desk. Is someone trying to send me a message?

It was so frustrating setting this one up. Lots of shouting in front of my monitors. But I think now I'm slowly getting somewhere with my first i3 setup.

Now to see if it will actually improve my workflow somehow.