How teslamotors/fleet-telemetry works
Fleet Telemetry is a Tesla vehicle telemetry server. Vehicles connect over mTLS WebSockets and push configured records; the service decodes and transforms records, dispatches them to configured outputs, and returns acknowledgements or errors. It also emits connection-state events and exposes operational monitoring. The README documents multiple datastore options and Prometheus/StatsD monitoring; source excerpts confirm key startup, streaming, record, and dispatcher behavior. Unsampled implementation details are represented only where documented, with unverified links dashed.
Main entry points: config.go Configuration · main.go Service startup · server.go WebSocket server · record.go Record parsing
Components 25
Service runtime
- Service startup
cmd/main.go - Configuration
config/config.go - WebSocket server
server/streaming/server.go - Socket processing
server/streaming/socket.go - Socket registry
server/streaming/socket_registry.go
Telemetry processing
- Record parsing
telemetry/record.go - Protocol serializer
telemetry/serializer.go - Stream messages
messages/stream_message.go - Vehicle schemas
protos/vehicle_data.proto - Connection events
protos/vehicle_connectivity.proto
Record dispatch
- Dispatch rules
config/config.go - Kafka output
datastore/kafka/kafka.go - Kinesis output
datastore/kinesis/kinesis.go - MQTT output
datastore/mqtt/mqtt.go - MQTT encoding
datastore/mqtt/mqtt_payload.go - Redis pub/sub
datastore/redis/redis.go - Google Pub/Sub
datastore/googlepubsub/publisher.go - ZeroMQ output
datastore/zmq/zmq.go - Simple outputs
datastore/simple/transformers/payload.go
Operations
- Monitoring endpoints
server/monitoring/metrics_server.go - Metrics collection
metrics/metrics.go - Status endpoint
server/monitoring/status_server.go
Other components
- Vehicle
- Event consumers
- Configured backends
Connections 28
- Service startup → Configuration: loads
cmd/main.go - Service startup → Dispatch rules: configures outputs
cmd/main.go - Service startup → WebSocket server: starts
cmd/main.go - Service startup → Monitoring endpoints: starts
cmd/main.go - Service startup → Status endpoint: starts
cmd/main.go - Vehicle → WebSocket server: streams telemetry
README.md - WebSocket server → Socket processing: routes connection
server/streaming/server.go - WebSocket server → Socket registry: registers sockets
server/streaming/server.go - Socket processing → Record parsing: parses records
- Record parsing → Protocol serializer: deserializes through
telemetry/record.go - Protocol serializer → Stream messages: encodes protocol
telemetry/serializer.go - Record parsing → Vehicle schemas: transforms protobuf
telemetry/record.go - WebSocket server → Connection events: emits connection state
server/streaming/server.go - Record parsing → Dispatch rules: dispatches via
- Configuration → Kafka output: creates producer
config/config.go - Configuration → Kinesis output: creates producer
config/config.go - Configuration → MQTT output: creates producer
- Configuration → Redis pub/sub: creates producer
- Configuration → Google Pub/Sub: creates producer
- Configuration → ZeroMQ output: creates producer
- Configuration → Simple outputs: configures output
- MQTT output → MQTT encoding: encodes payload
- Kafka output → Configured backends: publishes records
datastore/kafka/kafka.go - Redis pub/sub → Configured backends: publishes records
datastore/redis/redis.go - ZeroMQ output → Configured backends: publishes records
datastore/zmq/zmq.go - Google Pub/Sub → Configured backends: publishes records
datastore/googlepubsub/publisher.go - Event consumers → Connection events: consumes events
README.md - Monitoring endpoints → Metrics collection: reports metrics
server/monitoring/metrics_server.go