Am I the only one who thinks blogs were in their prime in the mid-2010s, before the internet began consuming content at wicked fast rates (thanks, Instagram and TikTok)? When someone says the word blog, I think of the chokehold 2015 southern American female fashion bloggers had on the internet. Pure pumpkin spice latte fashion. And though those blogs have, probably for the best, slipped away from the limelight, blogs are still alive and well.

You might already know that OpenTelemetry is the future of instrumentation. It’s an open-source and vendor-neutral instrumentation framework that frees you from the trap of using proprietary libraries simply to understand how your code is behaving. Best of all, you can instrument your applications just once and then take that instrumentation to any other backend system of your choice. This blog shows you exactly how to use OpenTelemetry to ✨break the vendor lock-in cycle.✨

Managed service providers have to manage complex and diverse customer environments that typically include hybrid infrastructure and multiple monitoring feeds. They need to be able to discover and monitor these environments, correlate alerts from multiple systems into single events, and map business services to the infrastructure and application services that support them, building customer-centric dashboards for real-time service and application health in the process.

I have always found data collection to be a fascinating area of work at Sumo Logic. Collecting data is a critical first step for all the solutions we develop for our customers. After all, to observe the health and performance of your applications, you must first collect all relevant data. It's also an area that has seen some significant activities by the open-source community over the years, which is completely changing the landscape of observability as we know it.

It’s a common belief that once we purchase a domain, it’ll be ours for as long as we like. Big mistake. Mainly because there are genuine threats to your domain online that mostly go unthought of. For example, hackers can gain access to your system and take your domain for ransom or cause malicious damage to you and your business. Surprised? Well, we have 5 examples of exactly when this has happened, and how hackers have managed to gain access to domains and cause mass disruption.

Here at StatusCake, we get asked a lot of questions about server monitoring, and more specifically, when we know your server has exceeded your set limits, for example. Understanding how we know can show you why server monitoring is so important to your website, and that’s why we’ve collated the most frequently asked questions so you can see for yourself!

How many servers can be managed by one system administrator? This question is not an easy one since it definitely depends on the tasks that need to be operated. However, it´s quite clear that the amount of servers one engineer can manage has increased enormously over time, and is still growing. Yet, public and private clouds, combined with automation tools, enable us to automate many daily tasks. In a modern IT infrastructure almost everything can, and should, be automated.

Consider the following question: Why do most teams face pressure to rethink traditional logging and observability approaches? Asking this question to most engineers would likely result in answers centered on the challenges posed by microservices apps. Because microservices are more complex than monoliths and involve more moving parts, they require more sophisticated, granular log collection, correlation, and analysis.

When your internet connection times out and you can't access a specific webpage, it's one of the most annoying errors. The message "The webpage not available" ERR_CONNECTION_TIMED_OUT will appear on the screen. This error usually occurs when there is an issue with the internet connection and the website does not load. The name of this error can be seen in the notification on your screen.

We all know the importance of cataloging, organizing, and breaking down the data in your logs. That process, parsing, makes information easier to find and simplifies subsequent analysis. Now, with Logz.io’s upgraded self-parsing tool, custom parsing rules, and log organization is easier than ever. What’s important is parsing that data out correctly. The better parsed, the easier to query.