> For the complete documentation index, see [llms.txt](https://sre.peerplays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sre.peerplays.com/introduction/service-level-agreements-slas/log-aggregation.md).

# Log Aggregation

Our log aggregation SLA defines the standards and targets for log collection, processing, storage, and accessibility. It serves as a foundation for ensuring the availability, reliability, and performance of the log aggregation service to support the operational needs of our organization.

In this section, you will find information on the key components of our log aggregation SLA, including:

1. **Log Collection and Ingestion:**

   * Supported log formats:  Plain Text, JSON, or structured logs.
   * Ingestion mechanisms: Log forwarding

2. **Processing:**

   * Processing time: Immediately

3. **Storage and Retention:**

   * Data retention period: 90 days
   * Storage capacity: 750GB 
   * Backup Schedule: Weekly

4. **Search and Retrieval:**

   * Search capabilities: Plain Text, LogQL, Regex

5. **Performance and Scalability:**

   * Ingestion rate: 4MB/s per log stream
   * System availability: 99.9%

6. **Monitoring and Alerting:**
   * Metrics and thresholds:
     *  Storage utilisation, with rocketchat notifications at 80% usage.
   * Alerting mechanism: Rocketchat/Telegram webhook to monitoring-channel


---

# 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 dynamically by asking a question.

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

```
GET https://sre.peerplays.com/introduction/service-level-agreements-slas/log-aggregation.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.