From the discovery of fire to the development of the internet, society’s need to communicate and live as a social unit has inspired endless innovation. Soon we'll be witness to the pinnacle of wireless technology: fifth-generation wireless networks (5G). By allowing users to communicate and share data at breakneck speed, 5G could prove to be a paradigm shift in information consumption and sharing.

Several months ago, Bryan Boreham introduced a few changes to Cortex that massively reduced its storage requirements. The changes were quite simple and altogether had a nice benefit of using almost 3x less data storage than prior versions. Since Loki shares a lot of code with Cortex, could we use these ideas to the same effect? (Spoiler alert: Yes, we can!)

Today, we’ll dive deep into monitoring hosts. The good news is that we’ll point you to some shortcuts on how to set up host monitoring in an easy way. The bad news is that we won’t be doing any percussive maintenance on any host. To monitor hosts, you have to set a few layers in place. Doing all this by yourself would be the hard way. You may ask: “How hard could it be?”.

In the fast-moving world of software development, as your product and organization grow and evolve, there are almost always competing priorities. Zeroing in on what is most important to your business in order to take it to the next level can at times seem like a non-stop process of trial and error. Oftentimes the customer who screams the loudest becomes a priority and gets the most focus.

Kinesis is a managed, high-performance and large-capacity service for real time processing of (live) streaming data. Prominent users include Netflix, Comcast and Major League Baseball. Its design to let it grab data from multiple sources at the same time and to scale processing within EC2 instances.

Kubernetes and containers are changing how applications are built, deployed and managed. Rancher makes application deployment simple and easily portable regardless of location or infrastructure. At Citrix, we operate on the same core principle. We provide application delivery and load balancing solutions for a high-quality user experience, to any device, across any network, for your web, traditional and cloud-native applications regardless of where they are hosted.

Remember that old commercial from the eighties of the actor Chris Robinson saying “I’m not a doctor, but I play one on TV”? (Yes, I know it’s an old commercial, but the catchphrase has definitely outshone the original product placement.) Well, I would like to start this blog post by changing things up and saying that “I’m not a Database Administrator, but I like to play one on TV!” Or, um, well, at least I like to pretend to be a DBA. Sometimes.

It is finally ready for launch – the first final release v1.0 of Icinga for Windows. The past months were quite challenging: Analyzing, troubleshooting and fixing issues reported by our awesome community and customers: Your support made it possible that we can celebrate the release of our new foundation for Windows monitoring. Scalable. Simplified. Extendable.

Services are the backbone of our systems. Whether they’re functional microservices or logical components of a traditional application, they are the pieces that make up our businesses. We can’t do the computer thing without services. But who’s responsible for owning a service in your company or organization? The cast of characters involved in the lifecycle of a service is more than just software engineers.

In this previous article we learned to create our own Docker images to test and distribute our applications regardless of their dependencies. As we know, Docker is a wonderful tool for collaborative programming work, allowing to work in a virtually identical environment regardless of the operating system you are in.