Syslog
Unified streams
Device, SaaS, and backend logs land in one view.
Find the errors around a device fault.
Search collected device and backend logs by time and device context. Investigate what changed and check fresh logs after a fix. Retention and analysis capabilities depend on your plan.
- Tail and search syslog from devices, gateways, applications, and backend services.
- Keep each log stream tied to device identity, status, and operational history.
- Compare error signatures across tags, device classes, firmware versions, and cohorts.
Linux device and service log ingestion
Send syslog through the device connection or configured collectors, then search it from the shared operations timeline.
Search
Fast filtering
Search by device, cohort, or error signature.
Context
Device metadata
Logs carry device tags and metadata.
Search with device context
Logs become more useful when they inherit the metadata already attached to each device.
Devices
Jump to the source
Move from a log line to the device record, customer, and current health state.
Cohorts
Filter by fleet segment
Search only lab units, a pilot customer, a firmware version, or a region.
Patterns
Find recurring faults
Compare error signatures across devices to separate one-off failures from product issues.
Incident evidence
Keep the facts that explain a support case beside the action that fixed it.
Alerts
Alert correlation
Pair log evidence with heartbeat, threshold, and availability alerts.
Terminal
Diagnose before acting
Read logs before opening a shell, then return to the same timeline after the fix.
Audit
Support record
Preserve the evidence trail for customer updates, warranty analysis, and postmortems.
Create your log collectors.
Set up syslog and HTTPS collectors so you can start sending logs right away.
Syslog collector
Send RFC5424 syslog over TCP/TLS from servers, gateways, or forwarders.
HTTPS collector
Post JSON logs over HTTPS from apps and services.