Connections
Every other page in these docs is about pushing telemetry to Plexus. This section is about the other direction: reading data that already exists somewhere, without moving it first.
There are three ways data reaches Plexus, and it is worth knowing which one you are on, because they behave differently.
| What it is | Where the data lives | |
|---|---|---|
| Devices push | The Python SDK, HTTP, or Prometheus remote_write | In Plexus |
| A system describes itself | A ground system or a flight log that already knows its own channels, units and limits | Stays where it is; read on demand |
| A database | A connection string and your own SQL | Stays where it is; read on demand |
A device is something you send data to us from. A connection is something we read from. Both appear in the same lists, share one naming scheme, and can be put on the same dashboard — the difference is only which way the data travels.
What a connection needs
Nothing installed on your side. A connection is a host, a credential, and read access — Plexus never writes to a store you connect.
Available now
Databases — PostgreSQL, TimescaleDB, ClickHouse, MySQL, QuestDB — connect the same way: pick the type, paste a connection string, write SQL. There is nothing to configure beyond the string.