Let Data Shed Some Light in the Midst of Uncertainty The burden the COVID-19 novel coronavirus has placed on the world is enormous. There’s a great thirst for information and clarity. So, we at Logz.io have decided to offer a Community COVID-19 Dashboard Project, so that everyone can better understand how the outbreak impacts the world and their region. We see that as a community effort.
Today, you probably wouldn’t blink at the idea of involving security in your development process. In fact, “shifting security left” has become so commonplace in the security industry, that there are conferences and job titles dedicated to SecOps (or DevSecOps or SecDevOps *eye roll emoji*). Yet, it wasn’t that long ago that the massive transition to this mindset took place.
In my last post I walked through a brief introduction to Application Insights, and APM tools in general, and hopefully the simple outside-in availability test I concluded the chapter with has been a useful starting point for you on your APM journey. In this post, I’m going to dig deeper into Application Insights and walk you through a use case that should make the purpose of Application Insights really clear.
With coronavirus (COVID-19) wreaking havoc across the globe, its disastrous effects are felt in the IT world, too. The lack of a complete work environment, as well as communication issues in development and production, will likely cause a total slowdown in every industry’s growth. Remote work is now mandatory in almost every enterprise.
With all the buzz surrounding user experience these days, I thought it might be worthwhile to start “at 50,000 feet” and dissect user experience into its component parts and see what all the fuss is about. User experience (UX) is somewhat different than customer experience (CX). Customer experience has been defined as the quality of all a consumer’s encounters with a company’s products, services, and brand. Today, user experience typically refers to the digital user experience.
In this article: Infrastructure monitoring systems have been undergoing massive change in the past few years. Before the proliferation of cloud computing, IoT and edge computing, mobile apps and SaaS apps, the practice was fairly static, albeit traditionally quite siloed. IT managers needed to get data on a set of standard metrics, from a handful of tools.
Over the past few months, we published a number of articles showing how to snap desktop applications written in different languages – Rust, Java, C/C++, and others. In each one of these zero-to-hero guides, we went through a representative snapcraft.yaml file and highlighted the specific bits and pieces developers need to successfully build a snap. Today, we want to diverge from this journey and focus on the server side of things.
You can utilize an SSL checker to troubleshoot the common SSL errors and vulnerabilities if you have installed an SSL certificate before. There is a plethora of tools you can choose from. You can also use a free SSL checker if you are working on a low budget. And using an SSL checker tool is quite simple. You simply must submit the domain name or IP address and the port number it requires to examine your website’s configuration and security.
“Remember that guy that gave up? Neither does anybody else.” Progress on the new Monitive has been slow as a snail in a marathon, but nevertheless the progress was there. Since the last update last year, a lot has been going on, and one day I woke up and just decided to write, even if small updates. Not only because Monitive is about transparency, but because I love writing.
In part one, we introduced the duality of observability, controllability. As a reminder, observability is the ability to infer the internal state of a "machine” from externally exposed signals. Controllability is the ability to control input to direct the internal state to the desired outcome. So observability is a loop problem. And we need to stop treating it as the end state of our challenge in delivering performant, quality experiences to our users and customers.
