# Monitoring Systems

This interface in question is designed to efficiently <mark style="color:green;">manage the monitoring systems associated with the company.</mark> It offers comprehensive compatibility, *<mark style="color:green;">**allowing integration with any vendor**</mark>*. This interface <mark style="color:green;">facilitates the management of each SIEM individually</mark>. Users can view all the integrations established with the company in an organized and paginated manner. Furthermore, the interface provides <mark style="color:green;">simplicity in editing the activation status, in deleting existing integrations, and in adding new integrations.</mark>

{% hint style="info" %} <mark style="color:green;">**Monitoring System**</mark> is designed to function as a <mark style="color:green;">central repository</mark>, <mark style="color:green;">collecting and processing all events</mark> from various data sources. It plays a crucial role in the organization and analysis of these events. A powerful correlation mechanism, built on the principles of <mark style="color:green;">Boolean algebra</mark>, continuously searches for patterns indicating anomalies. Once detected, these anomalies trigger alerts with unique identifiers based on the used Boolean algebra. These identifiers are <mark style="color:green;">integrated into our relational system to link the detected events to their respective correlation rules</mark>.
{% endhint %}

<figure><img src="https://2621223932-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLTQJomzpe5BTzHSLQPAt%2Fuploads%2FelvekwMUyg5g02ycKTFg%2FScreenshot%202023-12-11%20at%2020.03.56.png?alt=media&#x26;token=500a7562-61a7-4a48-b822-b3c1f82a7e73" alt=""><figcaption><p>Overview Monitoring System</p></figcaption></figure>

***

### Creating a new monitoring system integration

#### Identification

When creating a monitoring system integration, it's essential to provide <mark style="color:green;">a name and description</mark>.

<figure><img src="https://2621223932-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLTQJomzpe5BTzHSLQPAt%2Fuploads%2FWe6X8PmgTMEs1g7gXBsR%2FScreenshot%202023-12-11%20at%2020.20.28.png?alt=media&#x26;token=65037fb1-48d2-4441-bd43-c2ad66ee6c24" alt=""><figcaption><p>Identification Stage</p></figcaption></figure>

#### Vendor

Each vendor has their own standard for configuring integrations, and <mark style="color:green;">our system is versatile enough to connect with any SIEM.</mark>

<figure><img src="https://2621223932-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLTQJomzpe5BTzHSLQPAt%2Fuploads%2FkoDxaVH5YoDlBNZ7pLeR%2FScreenshot%202023-12-11%20at%2020.28.55.png?alt=media&#x26;token=ce653611-0130-4a89-9a5c-a89e51dc5a12" alt=""><figcaption><p>Vendor Options into Configuration Stage</p></figcaption></figure>

#### Servers

Our system enables the <mark style="color:green;">registration and continuous monitoring of the status of servers</mark> supporting the monitoring solution. This feature allows Inopli to have a detailed understanding of the architecture and function of each server. Management is optimized through a paginated listing interface, which includes advanced filtering features, as well as options to maintain, edit, or remove the 'active' status of servers.

Additionally, Inopli <mark style="color:green;">provides a specialized agent to be installed on the servers.</mark> This agent is responsible for <mark style="color:green;">constantly monitoring the server's health</mark>, ensuring its continuous operation. In case of any issues, Inopli <mark style="color:green;">automatically intervenes to make corrections</mark>, ensuring that the server remains functional without interruptions.

<figure><img src="https://2621223932-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLTQJomzpe5BTzHSLQPAt%2Fuploads%2F2skiLaWcpq0SuLgHPbdr%2FScreenshot%202023-12-11%20at%2020.45.15.png?alt=media&#x26;token=c46ed7ff-8b29-4c17-b7cb-0ede6ebf5026" alt=""><figcaption><p>Overview Servers Stage</p></figcaption></figure>

To register a new server in our system, it is necessary to provide essential information such as the <mark style="color:green;">agent's token, a fullname of the server, and its intended function.</mark> After this step, it is possible to link <mark style="color:green;">Threat Hunting and Health Check profiles</mark> to the server, as needed. These profiles are essential for ensuring efficient monitoring and maintaining the server's health.

<figure><img src="https://2621223932-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLTQJomzpe5BTzHSLQPAt%2Fuploads%2FzO0NrMrvoiKtqBjvC39q%2FScreenshot%202023-12-11%20at%2022.46.41.png?alt=media&#x26;token=7f9f1f58-7ae2-43bf-938d-2e138f9a3736" alt=""><figcaption><p>Adding a server</p></figcaption></figure>

***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.inopli.com/system-settings/managing-companies/monitoring-systems.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
