Data
Explore logs, export streams, and build real‑time metrics visualizations
Data
The Data section consolidates tools for inspecting device and account activity, streaming events to external systems, and visualizing key business performance indicators. This centralized data hub supports operations monitoring, troubleshooting, and system performance insights through multiple data perspectives.
Data Architecture
TelemetryOS data infrastructure separates into four primary categories:
| Category | Scope | Primary Use Case |
|---|---|---|
| Device Logs | Device-level operational events | Troubleshooting, error diagnosis |
| Account Logs | Account-level configuration changes | Audit trails, compliance |
| Export Streams | Real-time event delivery to external systems | Integration, analytics |
| Metrics | Custom business intelligence visualizations | Performance monitoring, KPIs |
Data Flow Patterns
Device logs → Filterable interface for real-time troubleshooting
Account logs → Audit trail for compliance and change tracking
Export streams → Webhook delivery to external systems
Metrics → Custom visualizations from data sources
Common Integration Workflows
Log aggregation: Device logs → Export streams → SIEM/logging platform (Splunk, ELK)
Proof of play: Playback logs → Export streams → Analytics platform → Campaign reporting
Compliance auditing: Account logs → Manual review or export → Compliance documentation
Business intelligence: Custom metrics → Visualization apps → Dashboard displays
Alerting: Device logs → Export streams → Monitoring platform → Alert notifications
Configuration Specifications
Data features configure through Data menu and device-level settings.
Access Points
Access points are organized as Device Logs and Account Logs in the Data menu, with exports available from device settings at Devices > [Device] > Settings > Webhooks (device-level) or from account-level Settings > Webhooks. Metrics are available through Data > Metrics.
Capabilities
Capabilities include filtering logs by severity, device, and time range; reviewing audit trails with change attribution; configuring webhooks for real-time event delivery; creating custom metrics from multiple data sources; and configuring the visualization app for metrics display.
Limitations
Device and account logs are retained for 90 days, with longer retention requiring export. Export streams require webhook endpoint setup because no built-in archival storage is provided. Metrics depend on configured data sources (APIs, databases, or static values), and real-time delivery requires stable device connectivity. Filtering performance can degrade over very large date ranges (best to stay under about seven days for large fleets), while webhook reliability depends on endpoint availability and retries use exponential backoff. Metric refresh rates are also limited by source query performance.
Updated about 1 month ago