> For the complete documentation index, see [llms.txt](https://docs.remote.it/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.remote.it/features/logging.md).

# Logging

Event logging in Remote.It — audit device, service and connection activity across your account.

Remote.It keeps an event log of activity across your account, so you can see when devices and services changed state and who connected to them.

## What gets logged

Each entry shows the date and time, an icon for the event type, and what happened.

* **Online and offline events.** When a device or one of its services goes online or offline. A device and each of its services are logged separately.
* **Connections.** When you connect to or disconnect from a service. Disconnect entries also show the data sent and received, and how long the connection lasted.

{% hint style="info" %}
If a device and all its services go offline and come back online together, it usually means the device lost power or its internet connection.
{% endhint %}

## Filter and download logs

Use the **Ending** date to choose the time period you see. The **filter** icon narrows the log to specific events, and the **download** icon exports the log so you can keep it or share it.

## Using the API

You can also query event logs in code. See [Event Logs](/developer-tools/api/usage/event-logs.md) for the GraphQL queries, event types, and attributes.


---

# 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.remote.it/features/logging.md?ask=<question>&goal=<user_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.