# Experiment 12 – Event Correlation and Monitoring Automation

Objective: Investigate alerts generated by an application server and its network dependencies. Apply event filtering, deduplication, and time-based correlation to identify the probable root cause, then demonstrate automated remediation using Ansible.

## Viva Questions and Answers

1\. What is event monitoring?

Event monitoring is the process of collecting and observing events generated by infrastructure components such as servers, applications, and network devices. It helps detect failures, unusual activities, and performance issues.

2\. What is event correlation?

Event correlation is the process of analyzing multiple related events to identify relationships and determine a common cause. It helps distinguish the actual problem from its secondary symptoms.

3\. Why is event correlation important?

A single failure can generate multiple alerts across different systems. Event correlation groups related alerts and reduces noise, making it easier to identify the root cause.

4\. What is event filtering?

Event filtering selects relevant events based on conditions such as timestamp, severity, source, host, or event type. It removes unrelated information and simplifies investigation.

5\. What is event deduplication?

Deduplication identifies and removes repeated or identical events. For example, multiple identical server-down alerts can be grouped into one event to avoid alert flooding.

6\. What is time-based correlation?

Time-based correlation groups events that occur within a specific time window. For example, if a network failure occurs immediately before an application becomes unavailable, both events may be related.

7\. What is root cause analysis (RCA)?

Root Cause Analysis is the process of identifying the original reason behind a failure rather than just treating its symptoms.

Example: If an application becomes unavailable because its database server crashes, the database failure is the root cause.

8\. What is the difference between primary events and secondary symptoms?

- Primary event: The original event that causes a failure.
- Secondary symptom: An additional problem resulting from the primary event.

Example: A network failure may be the primary event, while application timeout alerts are secondary symptoms.

9\. What is monitoring automation?

Monitoring automation uses scripts and tools to automatically perform actions based on detected events. It reduces manual intervention and helps resolve recurring infrastructure problems.

10\. What is Ansible?

Ansible is an open-source automation and configuration management tool. It automates tasks such as service management, software configuration, deployment, and system recovery.

11\. What is an Ansible Playbook?

An Ansible Playbook is a YAML file containing instructions or tasks that Ansible executes on managed systems. It defines what actions should be performed and in what order.

12\. What is Ansible's check mode?

Check mode is a dry-run mode that allows us to preview the changes an Ansible playbook would make without actually applying them.

```
ansible-playbook playbook.yml --check
```

It is useful for safely testing remediation procedures.

13\. What is the difference between Ansible and manual troubleshooting?

Manual troubleshooting requires an administrator to investigate and execute corrective commands. Ansible automates predefined procedures, making operations faster, repeatable, and consistent.

14\. What is automated remediation?

Automated remediation is the process of automatically correcting an identified problem using predefined scripts or playbooks.

Example: Restarting a failed application service when a specific failure condition is detected.

15\. How do you verify recovery after automated remediation?

After executing the remediation procedure, check the service status, application logs, and monitoring alerts to confirm that the issue has been resolved.

For example:

```
systemctl status nginx
```

If the service is active and the related alerts disappear, recovery can be considered successful.

## Last-Minute Revision

| Term / Command         | Meaning                          |
| ---------------------- | -------------------------------- |
| Event Monitoring       | Observing infrastructure events  |
| Event Correlation      | Connecting related events        |
| Filtering              | Selecting relevant events        |
| Deduplication          | Removing repeated events         |
| Time-based Correlation | Grouping events by time          |
| RCA                    | Root Cause Analysis              |
| Primary Event          | Original cause of failure        |
| Secondary Symptom      | Result of another failure        |
| Ansible                | IT automation tool               |
| Playbook               | YAML automation instructions     |
| Check Mode             | Dry run without applying changes |
| Remediation            | Corrective action                |
| `ansible-playbook`     | Executes an Ansible playbook     |
| `systemctl status`     | Checks service status            |

## Important for Practical Viva

Focus especially on:

1. Difference between event monitoring and event correlation.
2. Filtering, deduplication, and time-based correlation.
3. Identifying root causes from multiple related events.
4. Difference between primary events and secondary symptoms.
5. Ansible and its role in infrastructure automation.
6. What an Ansible Playbook is and why YAML is used.
7. Check mode and its command: `ansible-playbook playbook.yml --check`.
8. How to verify recovery after remediation.

Remember the practical flow: Inspect event dataset → filter events → remove duplicates → correlate by timestamp → identify root cause → demonstrate Ansible remediation in check mode or a controlled sandbox → verify recovery.

Based on Experiment 12 of your CS414 lab question bank.&#x20;

CS414_ITIMM_Lab_ESE.pdf
