Video walkthrough: Configure a correlation engine. ►

Watch a video on Configuring a Correlation Engine in Moogsoft Observability Cloud.

Configuring A Correlation Engine in Moogsoft

Moogsoft’s correlation engine groups related alerts and forms incidents.This happens automatically with no configuration.  But in this video, you’ll learn how to create additional correlation settings to tailor it to your specific needs.

Image1-_GroupRelated.png

We are going to use a sample use case to step through the process of surfacing the requirements and configuring the product.

Suppose you are implementing Moogsoft to facilitate collaboration between the infrastructure team and the application team.

The infrastructure team is organized by region, and each regional team breaks down into a few service categories.

So, if the server that supports service A in the US suffers, you want this team (AMERICAS - service A) and this team (Application 1 - service A) to come together and investigate.  

Also, since the infrastructure teams are organized by location, you need to differentiate the events originated in different regions.  

So this means just because service A is impacted, you don’t want to bundle alerts from the AMERICAS and EMEA clusters together.

You also noted that in the CMDB some of the values are not spelled consistently, like this for example.  But we want to treat these as the same service.

Based on the analysis so far, here’s how we want to correlate our alerts for this use case.

  • Evaluate only the alerts whose class are Application or Infrastructure

  • Data Center - 100% match

  • Service - 80% match to accommodate the variation in spelling.

Now let me show you how to set this up.

Provide a name that makes sense to other administrators too.

What you put into the description field will be used as the incident description. (switch to a sample incident screenshot and highlight the description area) so you want to make it as helpful as possible.

Image2-_Discription.png

We are going to use macros to insert dynamic information here. We want the description to mention the impacted service and the Data Center location….

Image3-_Macro.png

Scope is basically an entry filter.  

Image4-_Scope.png

In our use case, this correlation only applies to the alerts whose class is application or infrastructure.

And we want to cluster alerts from the exact same location,

And the same service but considering the variation in spelling, we’ll set the similarity value at 80%.

Image5_-_Settings.png

We’ll set the time window to 15 minutes. To understand the correlation time window, watch the “Alert Correlation Method in Moogsoft” video.

Now, let’s also modify the default workflow, so the alerts evaluated by the new correlation setting won’t be evaluated by the default correlation, and end up in two separate incidents.

We are going to add a scope filter, and exclude the alerts whose class field values are application or infrastructure.

Image6_-_AddScopeFilter.png

Now let’s simulate what happens to the alerts with this new correlation definition.

Here’s the scenario.  The server in our San Francisco data center that supports a database query service has overheated and started to fail.  Of course no one knows that yet.

The first event comes in…

The event goes through enrichment to add value to the service field, and gets deduplicated into an alert.

Right now this is the first event of its kind so it simply becomes an alert, but of course if another event with the same dedupe key value arrives, it will be deduplicated into this alert.

Now it arrives at the correlation engine.

The class field value meets the scope, so it enters the correlation we just configured.

Since this is the very first one, it becomes an incident on its own.

Image7_-_Incident.png

The next event arrives.

It is also impacting the same service as the last event, but note that its class value is not Infrastructure or Application.

So, it is filtered by the correlation we set up.  Instead it goes into the default correlation, and becomes a new and separate incident.

Image8_-_Seperate_Incident.png

Here comes another event. It’s enriched, deduplicated, and...

Now, this meets the correlation criteria we’ve defined, so this alert is bundled together with the first alert, and becomes part of the incident 001.

Since we set the services match percentage to 80 rather than 100%, it accommodates the difference in capitalization.

Image9_-_Matched_Incident.png

Now, this incident contains an infrastructure alert and an application alert on the same service in one place, and the applicable infrastructure team and the application team have been notified.

Image10_-_Multiple_Alerts.png

Looking at the timeline together, they quickly identified the issue originated in the hardware.

Without this incident correlating the two alerts together, the application team would not have been able to rule out other potential causes.

Now you know how moogsoft correlates alerts. thanks for watching