Introduction to RTA#
ATLAS Remote Telemetry Architecture (RTA) defines web services to let you load telemetry directly from your existing storage:
This can work with a wide range of technologies, such as:
- InfluxDB, TimescaleDB and other time-series stores
- MongoDB, Couchbase and other document databases
- Parquet, HDF5 and other file formats
- SQL Server, PostgreSQL, MySQL...
The RTA specification includes WebSocket streaming for live telemetry monitoring.
Our reference architecture recommends implementing this by taking a feed from your acquisition pipeline, and buffering it through Redis — which decouples the client activity and allows users to join the session at any point.
This enables ATLAS to display data in real-time even if your acquisition pipeline cannot write to storage in real-time, or if the storage is not available until acquisition is complete — common with file formats.
When users open live sessions, ATLAS selectively subscribes to the parameters on display using a WebSocket connection, and the Redis buffer covers the gap until data is flushed to storage. Users can get a complete and real-time view of the data even when joining hours into a session.
The RTA API Specification provides all the nececessary information to create a slick integration between ATLAS and your data infrastructure, with detail including:
- OpenAPI schema describing the REST API
- JSON schemas for the data model and query dialect
- Protobuf schemas for low-level data transport
However, you can save a lot of development effort by deploying services from our implementation toolkit.
By using these services to cover all the data management functionality, you won't need to implement any of the browsing, search or configuration management features. All you'll need to write is a simple hook into your ingest pipeline, and a Data Adapter Service:
These Toolkit Services provide gRPC services for integration with the rest of your data infrastructure.
gRPC is a modern, high performance framework for making service calls. It supports all popular programming languages, and the services are fully-described with schemas — so you get a high-quality client library that will work with your existing software stack, and high-quality developer tools to guide use of the API.
If you do not have any central telemetry database or file archive, RTA may not be the right architecture for you — but ATLAS is also very capable operating standalone:
ATLAS can browse and mount files directly.
This is a great option if your use case involves a lot of travel and in-field laptops.
ATLAS can display and record live telemetry directly from equipment — e.g. CAN bus — or the local network.
This option is popular in motorsport and eSports.
Some plugin development will be required for both these capabilities.
Contact us for a more in-depth technical discussion.