> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/anynet-sim/connectivity/monitoring-and-diagnostics.md). # Monitoring and diagnostics Monitor connectivity across all deployments, especially those with intermittent or mobile connections. Early detection of underperforming networks or routing problems helps you reduce service impact and costs. The [AnyNet Connectivity Management Platform](/anynet-sim/connectivity/about-the-connectivity-management-platform.md) provides automated and self-service tools for managing IoT estates and device connectivity. ### Monitoring tools The CMP helps you: * Identify service issues early. * Find the cause of common issues, such as supplier or routing failures. * Report performance by service. Eseye provides applications that store and display connection performance in different ways. You can also use APIs to create visualisation tools or machine-learning applications for device connectivity insights. --- # 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.eseye.com/anynet-sim/connectivity/monitoring-and-diagnostics.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.