# Log Profiles

> Choose which APIs of an API Maker account write a log entry for every call - tables, custom, system and third party APIs, events, schedulers, WebSocket events - with or without the response, and read them in the Log Explorer.

Source: https://docs.apimaker.dev/v1/docs/logs/log-profile.html

A log profile says which calls are written to the log database. Several profiles can be active ; a call is logged when any active profile selects its API.

| | |
|---|---|
| Page | `Utility → Log Profile` : the profiles on the left, the tree of the account on the right. |
| Selects | Tables and their APIs, custom APIs, system APIs, third party APIs, events, schedulers, WebSocket events. |
| Per API | **Save this API's response in the log** keeps the answer next to the request. |
| Active | Only active profiles log. **Clone** copies a profile ; a **default** profile can be marked. |
| Read | [Log Explorer](https://docs.apimaker.dev/v1/docs/logs/log-table.html). |

1. **Add New**, give a name, check the APIs, decide per API whether the response is kept, **Save Log Profile**.
2. Make it active. From now on every call of those APIs, on every server, writes an entry : who called, from where, how long it took, the payload and the console output of your code.
3. Open the Log Explorer to search them.

- Logs live in the log database of the [configuration](https://docs.apimaker.dev/v1/docs/am-resources/api-maker-configurations.html) (`logs.mongo_db_connection_logs`) and are trimmed to `maxLogsCount` by a daily job.
- Log profiles go to Git.

## Related

- [Log Explorer](https://docs.apimaker.dev/v1/docs/logs/log-table.html) · [API Maker configuration](https://docs.apimaker.dev/v1/docs/am-resources/api-maker-configurations.html)