> 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/signaling-logs.md). # Signaling Logs {% embed url="" %} ### What are Signaling Logs? Signaling Logs is an aggregation of all the control plane traffic that occurs between Onomondo and the RAN whenever a device connects to a network. Signaling Logs allows you to see all of that communication in real time. The control plane traffic includes information around authentication, authorization, and accounting (AAA). This takes place between different components of the telecommunication network (HSS, HLR, VLR, SGSN, SGWs, and so on). More specifically then the different protocols that are encompassed in these logs are [Diameter](https://en.wikipedia.org/wiki/Diameter_\(protocol\)), [GSM MAP](https://www.gsma.com/coverage/), [GTP,](https://en.wikipedia.org/wiki/GPRS_Tunnelling_Protocol) and [GTPv2](https://intercom-help.eu/onomondo/en/articles/159039-what-are-signaling-logs-and-how-to-read-them), which relates to the different cellular technologies in the following way. | Protocol | Technology | Connection Sequence | | -------- | ------------------ | ----------------------------- | | GSM MAP | GSM, 2G, 3G | Authentication, SMSs | | Diameter | LTE, LTE-M, NB-IoT | Authentication and accounting | | GTP | 2G, 3G | Registration | | GTPv2 | LTE, LTE-M, NB-IoT | Registration | Interpreting the information displayed in Signaling Logs requires some knowledge of telecommunication and networking. You can [learn more about how to interpret the logs here](https://intercom-help.eu/onomondo/en/articles/159039-what-are-signaling-logs-and-how-to-read-them). ### How to use them You are able to see the Signaling Logs in the platform, no matter where in the world the device is. The logs are also stored historically, so you can always go back and dive into it later. Watch the video above for more information around how to access them. {% hint style="info" %} Historical data regarding Signaling Logs is stored for up to three months. {% endhint %} --- # 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/signaling-logs.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.