# Telemetry

MemGQL sends **anonymous, statistical** usage data to Memgraph. It never
includes your data, schema, queries, credentials, or connection strings, and
it is not tied to a user or an account.

`SHOW CONFIG;` reports the setting as `telemetry.enabled`.

## What is sent

This is the complete list.

- **With every record:** product name (`memgql`), event type (`start`,
  `periodic` or `shutdown`), timestamp, MemGQL version, a random install id, a
  random run id, and the record's sequence number within the run. The ids are
  random, so they only tell servers apart.
- **At start:** license mode (community or enterprise), connector mode, and
  host facts: hostname, operating system type and description (e.g. `linux`,
  `Ubuntu 24.04`), CPU architecture, CPU core count, total memory, and whether
  it runs in a container.
- **Every hour:** uptime, the peak number of connectors, connections, and
  graphs since start, and the number of node and edge mappings registered.
- **At shutdown:** the same facts as at start, plus uptime.

## Disable it

If required, it's possible to disable sending statistical data by starting the
server with the flag:
```bash
docker run --rm -p 7688:7688 memgraph/memgql:latest --telemetry-enabled=false
```

If Memgraph's telemetry server is unreachable, records are kept in a local
`memgql_telemetry.redb` file next to the server and sent later.