> For the complete documentation index, see [llms.txt](https://fugolungo.gitbook.io/fugolungo-docs/Sw9EnGkWPJZdpbTYFR6Q/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fugolungo.gitbook.io/fugolungo-docs/Sw9EnGkWPJZdpbTYFR6Q/network-insight-tools/traffic-monitor.md). # Traffic Monitor {% embed url="" %} ### What is the Traffic Monitor? Traffic Monitor is an Onomondo feature that captures all traffic packets to / from the device in real time. Moreover, it helps you analyze traffic without installing anything on your device. This can prove helpful in understanding how your device communicates with the server. ### How to use it Once your device is online and transmitting data, go to the individual SIM page in the Onomondo app and open the Traffic Monitor tab. There you will see all packets flowing through the network, as well as source / destination IPs, packet length and additional details. The Traffic Monitor shows you a mere preview of the packets sent / received by the device. If you would like to dive deeper, you can download the traffic trace as a PCAP file and open it in [Wireshark](https://www.wireshark.org/) or a similar tool for further investigation. {% hint style="info" %} Note: The packets will only be available for as long as you keep the individual SIM page open in your browser. Onomondo does not store this data, so the logs will disappear once you leave the page. {% endhint %} You can also use the `onomondo-live` CLI tool to access the Traffic Monitor data. This is recommended in cases where you programmatically want to capture traffic to / from a device, or if you want to do so over a longer period of time. You can read more about how to use the `onomondo-live` CLI tool in the following link. {% content-ref url="/pages/9uu2uCgUtL0EDpRauYjV" %} [Traffic Monitor CLI](/fugolungo-docs/Sw9EnGkWPJZdpbTYFR6Q/reference/traffic-monitor-cli.md) {% endcontent-ref %} --- # 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, and the optional `goal` query parameter: ``` GET https://fugolungo.gitbook.io/fugolungo-docs/Sw9EnGkWPJZdpbTYFR6Q/network-insight-tools/traffic-monitor.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.