Operations | Monitoring | ITSM | DevOps | Cloud

I think we’ve all been there before – you log on to a server remotely via RDP, and do the needful – but don’t immediately log off. But then you get distracted by a phone call, an email, a chat, or a good old-fashioned physical interaction with another human being. So when it comes time clock out for the night, you shut down your computer or log off. Or maybe you’ve been working on a laptop and your VPN got interrupted.

Redis is an in-memory key-value data store that offers fast performance, flexible data structures, and multi-model databases, allowing it to handle a variety of use cases. Redis Enterprise enhances open source Redis with features designed to run distributed applications at scale, such as multi-tenancy, tiered data storage, active-active cluster replication, and support for up to five 9s of availability.

Since we launched Grafana Mimir — the most scalable, most performant open source time series database in the world — we have answered many of your questions about our latest open source project, including how to pronounce it. (All together now: /mɪ’mir/.) We have walked through how we scaled Grafana Mimir to 1 billion active series. And we will be hosting webinars to showcase cutting-edge features like query sharding and the two-stage compactor.

Ah, good question! TL;DR: Trace instead of log. Traces show connection, performance, concurrency, and causality. Logs are the original observability, right? Back in the day, I did all my debugging with `printf.` Sometimes I still write `console.log(“JESS WAS HERE”)` to see that my code ran. That’s instrumentation, technically. What if I emitted a “JESS WAS HERE” span instead? What’s so great about a span in a trace? Yeah, and so do logs in any decent framework.

Lots of organizations do not pay attention to their assets and pieces of equipment, who is using them and where are they located. These are particularly important questions but usually, they are ignored as a result assets are lost and nowhere to be found when they are required. Lots of employees waste their time finding the required assets and pieces of equipment. It also leads to delayed production work. Overall, the top line and bottom line suffer.

When it comes to IT, you can’t do anything with an asset you can’t see. When it comes to your networking, monitoring offers the eyeballs to know what is going on. But IT and network pros don’t spend all day staring at a dashboard waiting for something to happen. Like your local police department, they rely on notifications of trouble. Instead of 911 calls, IT depends on network alerts.

If you’re involved in IT, you’ve likely come across the word “Kubernetes.” It’s a Greek word that means “boat.” It’s one of the most exciting developments in cloud-native hosting in years. Kubernetes has unlocked a new universe of reliability, scalability, and observability, changing how organizations behave and redefining what’s possible. But what exactly is it?

Over the years, I found that building out monitoring scripts and using them properly has proven to be a challenge. When I look back at my internal IT days using platforms like Whatsupgold, PRTG, or N-central, the question always remained the same: how can I monitor efficiently and get alerts that matter? In this blog post, I thought I’d tackle something that is a challenge for a lot of people: monitoring Hypervisors.

The late 1990s were a crazy time in the technology industry. Apple converted a blueberry into a computer, Google still had a “new search engine” smell, and while Y2K loomed over our heads Napster was showing everyone how bad Metallica’s music sounded. Meanwhile, in a garage in Tulsa, Oklahoma, brothers Donald and David Yonce launched a network monitoring software company and named it SolarWinds.

The same concept holds true for AIOps, which needs a steady diet of data to feed the analytics that drive key functions like diagnostics and automation that can turn your IT operations team into AIOps champions.