> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infinity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infinity/user-guide/infraon-configuration/log-management.md).

# Log Management

Logging is an integral part of IT infrastructure management and process. Logs are generated from Routers, Switches, firewalls, IDS/IPS, Servers, Databases, and Web Servers across the IT infrastructure. They can be a generic live status of the end system or a detailed log of the running processes.

Log Management, a part of Infraon Infinity, helps in real-time analysis that can be used for security, compliance, audit, and IT operations.

Log Management enables reacting to anomalies based on log events and patterns, which play a crucial role in application troubleshooting, business analytics, marketing insights, resource management, and regulatory compliance.

## Access Control <a href="#toc177053561" id="toc177053561"></a>

This guide is intended only for Infraon Infinity operators/users with access based on selected roles and privileges assigned by the administrator.

Access depends on the type of license purchased by the portal operator.

{% hint style="info" %}
**Note:** The administrator drafted this document after accessing all the operator/user portal modules.
{% endhint %}

Administrators are responsible for adding or editing user roles and privileges to manage logs. Similar to other modules, specific roles will be configured for the Log Management module. The log management system will update These roles and permissions to ensure appropriate access control.

Users can log in with the assigned credentials and perform tasks within the Log Management module based on their privileges and permissions. Access to various features within the module will depend on the Roles and Privileges the administrator enables. (Click here to view the guide on how to add or edit users with specific roles and permissions.)

## How does it work? <a href="#toc177053562" id="toc177053562"></a>

Log management collects, stores, analyses, and monitors log data generated by systems, applications, and services within an IT infrastructure. This module will log assets uploaded to our system.

This module enables users to access network device logs via the Syslog server. For Windows-specific logs, utilize the Winlogbeat server. To collect Linux logs, employ the Filebeat server.

Logs will be saved in the Elasticsearch database, and Logstash can be used as a pipeline to dump data into it.

Log Management will fetch data from the elastic database and show it in the Infraon interface based on configuration.

Monitoring, documenting, and analyzing system events are crucial to security intelligence (SI). Regarding compliance, regulations such as PCI have specific mandates relating to audit logs. &#x20;

Log management software automates many of the processes involved. For example, an event log manager (ELM) tracks organizational IT infrastructure changes. These changes are reflected in audit trails that must be produced for a compliance audit. &#x20;

## Log Management Sub-modules:

Log Management is then configured in the sub-modules below:

Let’s see each one in detail:

* [Pipeline Configuration](https://docs.infraon.io/infinity/user-guide/infraon-configuration/log-management/pipeline-configuration.md): Configure log pipelines to collect, process, filter, and route incoming log data to the appropriate destinations.
* [Grok Pattern](https://docs.infraon.io/infinity/user-guide/infraon-configuration/log-management/grok-pattern.md): Define and test patterns to extract structured fields from unstructured log messages, making log data easier to search and analyze.
* [Log Search](https://docs.infraon.io/infinity/user-guide/infraon-configuration/log-management/log-search.md): Search and investigate log data to identify events, troubleshoot issues, and analyze system activities.
* [Export Configs](https://docs.infraon.io/infinity/user-guide/infraon-configuration/log-management/export-configs.md): Manage log export configurations to support the transfer of log data to external destinations.
* [Log Management Overview](https://docs.infraon.io/infinity/user-guide/infraon-configuration/log-management/log-management-overview.md): View an overview of log management information to monitor the status and activity of the log management environment.
* [Stream Retention](https://docs.infraon.io/infinity/user-guide/infraon-configuration/log-management/stream-retention.md): Configure log retention settings to manage how long log data is stored.

**Prerequisites**&#x20;

Before configuring Log Management, ensure that the following components are configured as required:

* [Log Agent Configuration](https://docs.infraon.io/infinity/user-guide/infraon-configuration/log-management/log-agent-configuration.md): Configure the log agent settings required to collect and forward log data from the relevant systems.
* [Log Rule](https://docs.infraon.io/infinity/v7.5.2/user-guide/infraon-configuration/it-operations/rules/log-rule.md): Configure log rules as required to define log-related conditions and processing or alerting behavior.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infraon.io/infinity/user-guide/infraon-configuration/log-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
