Preview

You're viewing the Next docs — a rolling preview of in-development changes. The current release docs may differ.

Telemetry

Device events are structured messages emitted by a device and stored by Nexigon Hub. Use them for a history of device behavior; use properties for the latest reported state.

For examples, follow Device Telemetry.

Event Fields

Field	Meaning
Body	Any JSON value, including a message string or structured object.
Severity	Importance of the event; defaults to `info`.
Category	Optional string identifying an event type. Keep the set of categories small.
Attributes	Additional named JSON values, such as version or sensor identifiers.

Severity Values

Value	Meaning
`trace`	Low-level execution details.
`debug`	Diagnostic information for debugging.
`info`	Routine informational messages.
`warning`	A potential problem that may need attention.
`error`	A problem that affects functionality.
`critical`	A severe problem requiring immediate attention.

Emission Interface

nexigon-agent events emit [OPTIONS] <BODY>

Options:
  --severity <SEVERITY>     Event severity [default: info]
  --category <CATEGORY>     Event category
  --attribute <ATTRIBUTE>   Event attribute; repeat for multiple attributes

Each attribute uses name=<JSON-value> syntax.

Nexigon Agent sends events immediately. It has no offline buffer; emission fails without a connection to Nexigon Hub.

Querying Events

Use devices_QueryEvents to query a device’s stored events. See Pagination for cursor handling, ordering, and consistency rules.

Edit this page

PreviousDevice Commands NextOperations