> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/management-and-operations/dashboard-and-monitoring/system-logs.md). # System Logs System logs from the Agent and the containing operating system. Frends platform provides logs to monitor the systems that are running your Frends Tenant. ## Agent Logs Agent event logs, accessible under Administration and Environments, show system and Frends Agent events, showing what is happening in the background. Any unhandled errors from integrations, system errors and possible causes of more widespread issues are shown here for each Agent in your Tenant.

Picture shows Frends Agent's events from a development environment. — Filterable list of events from the Agent are shown under Environment administration.

## API Monitoring In order to monitor what is happening with your Frends APIs, the **API Monitoring** page shows you all the connections made into your tenant, and what happened with them.

You can easily filter the log by API operation, status code of the response, and what method was used, to figure out what is happening. The logs include events for all requests made against your tenant, and not only the specified API endpoints, so you can also see all the unsolicited attempts made against your environment. --- # 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.frends.com/management-and-operations/dashboard-and-monitoring/system-logs.md?ask=&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.