Data

The Data section consolidates tools for inspecting device and account activity, streaming events to external systems, and reviewing playback history. This centralized data hub supports operations monitoring, troubleshooting, and system performance insights through multiple data perspectives.

Device logs

Filterable logs from devices with severity context and troubleshooting links for diagnosing and resolving device-related issues.

Account logs

Audit trails tracking account-level changes including assignments, settings modifications, and user actions for compliance and security monitoring.

Export

Data streams sending logs, playbacks, and views to designated endpoints via webhooks for integration with external analytics platforms and custom processing workflows.

Data Architecture

TelemetryOS data infrastructure separates into three 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

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

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

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.

Capabilities

Capabilities include filtering logs by severity, device, and time range; reviewing audit trails with change attribution; and configuring webhooks for real-time event delivery.

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. 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.