Log profiles¶
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. |
- Add New, give a name, check the APIs, decide per API whether the response is kept, Save Log Profile.
- 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.
-
Open the Log Explorer to search them.
-
Logs live in the log database of the configuration (
logs.mongo_db_connection_logs) and are trimmed tomaxLogsCountby a daily job. - Log profiles go to Git.