Skip to main content
Telemetron ingests device telemetry data from multiple sources to power AI-driven hardware support.

​
Ingestion Methods

​
REST API

Send telemetry data directly via the REST API: 
curl -X POST https://admin.telemetron.ai/api/telemetry \
  -H "x-api-key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{"deviceIdentifier": "SN-12345", "temperature": 25.5, "humidity": 60}'

​
AWS IoT Core

Forward MQTT messages from your IoT devices through AWS IoT Core rules. Telemetron provides a Terraform package to set up the required AWS infrastructure automatically. See AWS IoT Core Integration for setup details.

​
AWS S3 Bucket Backfill

Import historical telemetry data from compressed CSV files stored in S3. Configure prefix mappings to define how your file structure maps to device identifiers and timestamps. See AWS S3 Bucket Integration for setup details.

​
Memfault

Telemetron queries Memfault device attributes to pull crash reports, firmware information, and fleet health data. See Memfault Integration for setup details.

​
Device Connections

Devices in Telemetron can be connected to external data sources. Each device connection maps a Telemetron device to its representation in an external system (AWS IoT, Memfault, etc.), enabling:
  • Real-time monitoring — view latest telemetry data for any device
  • Historical analysis — query past data points and trends
  • Proactive alerts — AI agent can detect anomalies and create cases before customers report issues

​
Device-Customer Mapping

For telemetry data to be useful in support, devices must be mapped to customers. Use the Device Assignment API to create these mappings so that:
  1. Device sends telemetry to Telemetron
  2. Telemetron looks up which customer owns the device
  3. AI agent provides support with full device context