> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/management/logging.md). # Logging **Category**: Management **Version**: 1.0 **Last Updated**: June 1, 2026 **Author**: Any2Info *** ### Description The **Logging page** allows administrators to view application logging within the Any2Info platform. This page shows the raw log data that is captured by the application. It can be used to inspect application activity, monitor logged events, and investigate behavior across services, modules, users, collections, and objects. The Logging page is an administrative page and is available to administrators only. *** ### Location The Logging page can be found in the menu under: **Management → Logging** *** ### Access | Role | Access | | ----- | ------ | | Admin | Yes | *** ### Log overview The page displays log lines in a table. Each row represents a logged event or message from the application. The following columns are shown: | Column | Description | | ------------ | ------------------------------------------------------ | | Time | The date and time when the log line was created. | | Service | The service that created the log line. | | Module | The module or component where the log line originated. | | Duration(ms) | The duration in milliseconds, when applicable. | | Message | The logged message or event details. | | User | The related user, when applicable. | | Collection | The related collection, when applicable. | | Object | The related object, when applicable. | By default, the Logging page can show log lines for all collections. Administrators can filter the logging to a specific collection by using the filter options. *** ### Toolbar actions The Logging page contains several toolbar actions. | Action | Description | | --------- | ------------------------------------------------------------------------------------ | | Filter | Opens the filter dialog for advanced filtering and sorting. | | Export | Exports the current filter settings. | | Import | Imports saved filter settings. | | View live | Starts real-time logging. The log view continues to refresh until the user stops it. | | Reload | Reloads the log lines manually. | The page is read-only. Log lines cannot be edited from this page. *** ### Filter options The filter dialog allows administrators to narrow down the visible log lines and configure sorting. #### Filtering | Filter option | Description | | ---------------------- | --------------------------------------------------------- | | Between | Filters log lines between a start and end date/time. | | Messages containing | Filters log lines based on text contained in the message. | | Show requests with ids | Filters log lines by one or more request identifiers. | | Filter by collection | Filters log lines for a specific collection. | | Filter by object | Filters log lines for a specific object. | | Filter by user | Filters log lines for one or more selected users. | #### Types The **Types** tab allows filtering based on log levels, services, and modules. | Type filter | Description | | ----------- | ------------------------------------------------- | | Log levels | Filters log lines by level of detail or severity. | | Services | Filters log lines by application service. | | Modules | Filters log lines by module or component. | Available log levels include: | Log level | Description | | ----------- | ----------------------------------------------------------------- | | Trace | Very detailed diagnostic information. | | Debug | Diagnostic information useful during debugging. | | Information | General informational messages about normal application behavior. | | Warning | Messages that indicate a possible issue or unexpected situation. | | Error | Messages that indicate an error occurred. | | Critical | Messages that indicate a serious failure or critical issue. | | None | Log lines without a specific log level. | #### Sorting The **Sorting** tab allows administrators to configure the order in which log lines are displayed. | Sorting option | Description | | -------------- | ---------------------------------------------------------------------- | | Column | Selects the column used for sorting. | | Order | Defines whether the selected column is sorted ascending or descending. | Multiple sorting rules can be added when needed. *** ### Usage Use the Logging page when you need to inspect raw application logging. Typical use cases include: * Reviewing application activity. * Investigating application behavior. * Filtering logs by collection, user, object, service, module, or message. * Viewing logs in real time while reproducing an issue. * Exporting and importing filter settings for repeated investigations. *** ### Tips & Best Practices * Use filters before reviewing large amounts of log data. * Filter by collection when investigating behavior for a specific collection. * Filter by user or object when investigating a specific action or record. * Use **View live** when reproducing behavior and watching the logging in real time. * Use **Export** to save useful filter settings for later reuse. * Use sorting to show the most relevant log lines first, for example by timestamp descending. * Keep in mind that this page shows raw application log data and may include technical messages intended for administrators. *** ### Changelog | Version | Date | Change | | ------- | ------------ | ------------------------------------ | | 1.0 | June 1, 2026 | Initial documentation version added. | --- # 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: ``` GET https://academy.any2info.com/any2info-academy/no-code-platform/management/logging.md?ask= ``` 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.