Event Catalog¶
Every event the PQ system publishes, generated from the sources on each docs build. There are two kinds:
| Kind | Count | Raised by | Defined in |
|---|---|---|---|
| Device events | 437 | adapters, on behalf of a Thing in the device tree | the framework event taxonomy (pq-events.yaml) |
| Application events | 72 | the server and built-in modules (people, credentials, spaces, incidents, …) | event classes in the server domain |
Device events¶
An adapter never builds these by hand: the Thing declares them in its YAML and the generator emits the
publication methods. The event id is hierarchical, general to specific, so subscribing to a parent
receives all of its children (pq.event.access.denied receives every denial reason). The default case
has no suffix; .schedule, .remote and .rex mark how it was triggered.
Application events¶
Each is a C# class; its type name, lower-cased, is the event type on the message bus and in the audit
log. Properties marked Identity link the event to an entity (person, credential, space, …) so the
event shows up in that entity's history; properties marked Audited are kept in the audit record.
Every event also carries SourceTime and Severity.