To stay competitive, companies who want to run an agile business need log analysis to navigate the complex world of Big Data in search of actionable insight. However, scouring through the apparently boundless data lakes to find meaningful info means treading troubled waters when appropriate tools are not employed. Best case scenario, data amounts to terabytes (hence the name “Big Data”), if not petabytes.

In the past I used to use the right tool for the right purpose. This led me to employ a lot of tools, and with most turning out to use subscription-based billing, increasing our costs much more that I would have hoped for. So, I adopted a new strategy: Use as few tools as possible, but use them as much as possible.

Stan Lee believed in the power of strength in numbers, that a group working together can create a force so powerful it’s unstoppable; from “X-Men” to “Avengers”, these teams had a pioneering spirit, heroic work ethics, and group thinking that surpasses individual brainpower almost every time. Today marks that day when the LogDNA superhero team becomes even stronger. I’m excited to announce that we have closed our Series B round of financing.

Protecting your data, and that of your clients, should be central to all of your business practices. Customers entrust companies with often very sensitive data, and it should be used and stored safely. Cyber security should be a priority in companies of any size, but when you’re a small business without a big security budget, how do you keep yourself protected?

In case you missed it, Sensu Go is here! And, as I wrote about previously, one of the hurdles with migrating workloads from the original version of Sensu to Sensu Go are the changes in the internal event data structure. The existing handlers and mutators in the community maintained Sensu Plugins collection might not work as expected in Sensu Go because of these event data model changes. But friends, I’m here to tell you that we’ve got this problem licked.

Before I hop right in, it’s important to understand a bit about diabetes. Diabetes is what happens when your body cannot produce (type 1) or respond (type 2) to insulin effectively. The impact on the body is frequently quite severe — people who have difficulty controlling their blood sugar levels run the risk of losing feeling in their fingers and/or toes or even going into a coma if their blood sugar is either too high or too low.

With the recent panic over the zero-day Kubernetes vulnerability CVE-2018-1002105, Kubernetes administrators are scrambling to ensure their Kubernetes clusters are upgraded to a version that is patched for the vulnerability. As of this writing, the minimum versions that have the patch are 1.10.11, 1.11.5, 1.12.3, and 1.13.0-rc.1.

Now that companies depend on the cloud for access to key services and business operations, downtime has a larger impact on productivity. Uptime is just as critical to small businesses as it is to major ecommerce retailers on Black Friday. Even the public relies on various services like Alexa and email to be available throughout the day. Looking at major outages over the past year provides insight into how companies prepare to handle these events.

I’ve lived in the virtualization and cloud world for a really long time. During that time, I’ve also seen the impacts on users when you don’t have a good performance monitoring and troubleshooting system in place. That said, what if you have managed services? Do you understand what challenges managed services providers (MSPs) face when working without a monitoring and troubleshooting tool? How are you effectively resolving common VDI performance as well as connectivity issues?