> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/mosip-docs-1.1.5/modules/kernel/audit-manager-functionality.md).

# Audit Manager Functionality

The Audit Manager in MOSIP captures all the information about the actions performed by various MOSIP applications. This information can further be used for data analysis which will help in inspecting, cleansing, transforming, and modeling data to discovering useful information, informing conclusions, and decision-making.

## Audit Log Parameters

The following parameters are captured as a part of the audit service,

| Parameters           | Description                                                                  | Example                                                        |
| -------------------- | ---------------------------------------------------------------------------- | -------------------------------------------------------------- |
| **Event ID**         | The ID of the Event that triggered for which the audit action has happened   |                                                                |
| **Event Type**       | Type of event that triggered the audit log                                   | System, User                                                   |
| **Event Name**       | Name of the event                                                            | Create, Register, Update, Processing                           |
| **Log Description**  | Detailed description of the audit event captured                             |                                                                |
| **Module ID**        | Application Module ID that triggered for which the audit action has happened |                                                                |
| **Module Name**      | Name of the application module                                               | Packet Service, Resident Service, and MISP Management Service) |
| **Ref ID**           | Reference ID for any cross-reference purpose relevant for audit tracking     | userid, rid, prid, app id, app or module id, etc.              |
| **Ref ID Type**      | Type of reference id entered                                                 |                                                                |
| **Application ID**   | Application Id of audit action happened and logged                           |                                                                |
| **Application Name** | Name of the application                                                      | Admin, Resident Services, Partner Management etc.              |

## Application-Specific Audit Details

* [Admin Service Audits](/1.2.0/mosip-docs-1.1.5/modules/kernel/audit-manager-functionality/admin-service-audits.md)
* [Resident Service Audits](/1.2.0/mosip-docs-1.1.5/modules/kernel/audit-manager-functionality/resident-service-audits.md)
* [Partner Management Audits](/1.2.0/mosip-docs-1.1.5/modules/kernel/audit-manager-functionality/partner-management-audits.md)
* [Registration Client Audits](/1.2.0/mosip-docs-1.1.5/modules/kernel/audit-manager-functionality/registration-client-audits.md)
* [Registration Processor Audits](/1.2.0/mosip-docs-1.1.5/modules/kernel/audit-manager-functionality/registration-processor-audits.md)
* I[D Repository Audits](/1.2.0/mosip-docs-1.1.5/modules/kernel/audit-manager-functionality/id-repository-audits.md)
* [ID Authentication Audits](/1.2.0/mosip-docs-1.1.5/modules/kernel/audit-manager-functionality/id-authentication-audits.md)
* [Pre-registration Audits](/1.2.0/mosip-docs-1.1.5/modules/kernel/audit-manager-functionality/pre-registration-audits.md)

## Abbreviations

| Abbreviation | Definition                            |
| ------------ | ------------------------------------- |
| ADM          | Admin                                 |
| AUTH         | Authentication                        |
| BLK          | Bulk                                  |
| EVT          | Event                                 |
| EXPT         | Export                                |
| MISP         | MOSIP Infrastructure Service Provider |
| NAV          | Navigation                            |
| PKT          | Packet                                |
| PMS          | Partner Management System             |
| PRT          | Partner                               |
| RES          | Resident                              |
| RID          | Registration ID                       |
| SCH          | Scheduler                             |
| SYNC         | Synchronization                       |
| UIN          | Unique Identification Number          |
| UPL          | Upload                                |
| VID          | Virtual ID                            |


---

# 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.mosip.io/1.2.0/mosip-docs-1.1.5/modules/kernel/audit-manager-functionality.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.