> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.3/pbms/functionality/monitoring-and-reporting/logging.md).

# Logging

## Introduction

In OpenG2P logging is performed at various levels:

* **System logs** for monitoring and debugging
* **Audit logs** for business process auditing
* **Change logs** for recording changes to data

## System logs

Each module outputs system logs for different levels:

* INFO, ERROR, DEBUG, WARNING

Logs from all modules are channelized and indexed for viewing on dashboards and triggering alerts. Refer to [Logging](/1.3/monitoring-and-reporting/logging.md) for further details.

## Audit logs

For Odoo modules [Odoo's Audit Log](https://github.com/OCA/server-tools/tree/16.0/auditlog) package is used.

For FastAPI modules, audit logs are implemented using [MOSIP's Auditmanager Service](https://github.com/mosip/audit-manager/tree/release-1.2.0).

## Change logs

For PBMS, change logs are implemented using [Odoo's Audit Log](https://github.com/OCA/server-tools/tree/16.0/auditlog) package. Rules are added against the models to record field level changes.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.openg2p.org/1.3/pbms/functionality/monitoring-and-reporting/logging.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.