Operations | Monitoring | ITSM | DevOps | Cloud

Root cause analysis, or RCA, is the process of identifying the cause of a problem so measures can be taken to prevent that problem from happening again. RCA assumes it’s more effective to resolve problems by addressing the underlying cause rather than just the symptoms.

IT networks generate large volumes of information in the form of security, network, system and application logs. The volume and variety of log data makes traditional network monitoring capabilities ineffective — especially for monitoring use cases that require proactive decision making. These decisions are based on things like: All of this makes large-scale and complex enterprise IT networks a suitable use case for advanced AI and machine learning capabilities.

New Integrations Provide Superior Digital Developer and User Experiences Our most recent release of Dexda demonstrates our commitment to harnessing the transformational power of Artificial Intelligence (AI) for hybrid observability. Using a variety of advanced machine learning and AI techniques, Dexda dramatically reduces alert fatigue. Our use of intelligence and automation continues to change the way IT teams work.

Businesses lose potential revenue, trust, and brand reputation every moment your website is down. Some of those things can never be earned back. Website outages sting whether you’re a blossoming startup or a seasoned enterprise. How often do they happen, and what’s the actual cost? That is exactly what we will explore together today!

As your applications grow, your teams may be faced with managing a complex, expanding mesh of potentially thousands of loosely connected APIs—each one a new point of failure that can be difficult to track and patch. API sprawl comes naturally in rapidly expanding, distributed applications, and the difficulty of maintaining centralized knowledge and toolsets for your APIs creates friction when teams need to leverage APIs they don’t own.

Today’s modern applications are made up of thousands of loosely connected private and publicly exposed APIs, each serving a specific function. This dynamic API landscape, in combination with the decentralized nature of microservice development, can be overwhelmingly challenging to manage—let alone govern or secure adequately. API sprawl is often created as a result, leading to fragmented or nonexistent internal API documentation, knowledge bases, and toolsets.

At observIQ, we've seen growing interest in observing the health of Windows systems and applications using OpenTelemetry. Requests on the SQL Server receiver continue to garner the most interest, so let's start there. Below are steps to get up and running quickly with the contrib distribution of the OpenTelemetry collector. We'll be collecting and shipping SQL Server metrics to a popular backend, Google Cloud.