# System Logging

**System logs** generated across all components can be monitored via the logging pipeline shown below. The logs can be searched, sliced and diced for analytics. **Fluentd** and **OpenSearch** are used to collect, parse, display and search logs.

## Logging pipeline

{% embed url="<https://miro.com/app/board/uXjVKZsLZhk=/?embedAutoplay=true&share_link_id=265139863172>" %}

## Log files

This is a simple method where the Python logging module is used to write system event logs in JSON or other format in log files directly. These log files are shunted to OpenSearch for indexing, searching and querying.

## Dashboards

Several dashboards can be created using [OpenSearch Dashboards](https://opensearch.org/docs/latest/dashboards/). Some default dashboards are provided by OpenG2P and may be customised.

<figure><img src="/files/GrBkYJQU1VchPsncL4P5" alt=""><figcaption></figcaption></figure>

## Installation

Refer to [Deployment->Fluentd & Opensearch](/operations/deployment/scaling/base-infrastructure/openg2p-cluster/fluentd-and-opensearch.md).


---

# 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.openg2p.org/platform/platform-services/monitoring-and-reporting/logging.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.