Operations | Monitoring | ITSM | DevOps | Cloud

As the Trump Administration comes to a close, there is no better time than the present to reexamine the Department of Defense Digital Modernization Strategy and its potential sustainment beyond January 2021.

Recently, I saw a video from a really great developer and YouTuber, Ben Awad, where he discussed Serverless not make any sense. Even though I really enjoyed the video, I am not sure if the author’s points about serverless are entirely valid, and I want to discuss them in this article.

Today we finally have great news to share for everyone using Icinga to monitor Hyper-V and Windows Cluster environments. For quite some time we’ve been working on multiple new plugins to provide better monitoring option for Hyper-V and Windows Cluster. The new plugins are based on our PowerShell framework provided by Icinga for Windows. For the new plugins we decided to provide a preview first, in favour of a final release.

In this tech tip, we are focusing on HLS (HTTP Live Streaming), a streaming protocol released by Apple in 2009. HTTP Live Streaming is widely used and it isn’t just limited to streaming services like Netflix or YouTube – it’s an important protocol for all content providers and CDNs. You’ll basically find HLS anywhere people want on-demand streaming.

While managers may not be the most technical colleagues in the building—or online, in the case of 2020—dismissing their lack of monitoring knowledge isn’t always helpful. Managers who understand the tasks their teams deal with daily can be a great asset to any company. But how can we know what managers need to know to sound like monitoring experts? Simple. Just ask.

Yup – we've now got a health explorer for Azure VMs! Health Explorer… now why does that sound familiar? You’ve probably guessed it by now, but here’s another hint: Hmm…now where have I seen that before? Right – in SCOM!

In order to continuously improve your Ruby application, you need to understand everything your code touches. That means visibility into how your frontend responds to the database queries that are central to your Ruby application. Sentry’s new Ruby SDK collects and monitors the data surrounding your traces, logs, and key metrics. With it, you now have the context to connect backend issues to frontend performance.

A couple of days ago, Elastic announced that it will change the licensing of Elasticsearch and Kibana as of the 7.11 release to a proprietary dual license (under the SSPL license) and away from the open-source Apache-2.0 license. This move has caused extensive turmoil and frustration in the open-source community, especially with organizations that rely on Elasticsearch. Let me start with the end in mind.

As a customer-focused company, which pays a lot of attention to its client’s needs and requests, while keeping pace with the market dynamics, VirtualMetric has always followed the approach of continuous product development. Our ongoing improvement process allows us to develop, test and release new features and product capabilities of your all-in-one monitoring software at short time intervals.

Let’s say you get an alert that one or more queries is slow. Or that your users complain, whichever comes first 🙂 We’ve all been there… How do you find the root cause for this slowness and then fix it? In this article, I’ll go through my usual thought process: first, I’d try to find which queries are slow. Then, I’d dig deeper: Let’s take a specific example and run through each step.