Operations | Monitoring | ITSM | DevOps | Cloud

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.

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.

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.

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.✨

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.

As organizations marshal their data to drive business value throughout the enterprise, it’s becoming more important than ever to ensure the quality of this data. Building data quality, data validation testing, and aligning the data with your organization’s master data (such as products, customers, assets, and locations) is critically important to ensure your reporting is consistent and accurate.

Visualizing log data is one of the biggest perks of using good log management software. Data is many businesses’ most critical asset. But, without proper use, a business’ data becomes just an artifact and no longer an asset. Visualization and analysis are the end goals of collating log data from their sources. The need for visualization arises from the fact that we intuitively process visual information faster than a random jumble of numbers and letters.

Log observability and monitoring are terms often used interchangeably, but really they describe two approaches to solving and understanding different things. Observability refers to the ability to understand the state of a complex system (or series of systems) without needing to make any changes or deploy new code.

We’re happy to announce a new update release of our Oracle Management Pack for SCOM. The 21.9.2568.0 release contains new features, fixes, and changes. On top of this, we have also released a new datasheet and a white paper that you can find more information about further down in this article.

Which data sources do DevOps teams need in order to achieve observability? At a high level, that’s an easy question to answer. Concepts like the “three pillars of observability”—logs, metrics, and traces—may come to mind. Or, you may think in terms of techniques like the RED Method or Google’s Golden Signals, which are other popular frameworks for defining which types of data teams should collect for monitoring and observability purposes.