An event is a time-specific change to a resource or class. Fault Manager and SMF services dynamically record event data. A device faulting is a system event. An administrative change to a service is a system event.
The following SSID identifies any system fault event:
The following SSID identifies a fault of CPU 0:
The following SSID identifies any administrative action event:
The following SSID identifies an administrative action on the svc:/network/smtp:sendmail service:
The statistics store can capture system fault, defect, and alert data as described in Fault Management Overview in Managing Faults, Defects, and Alerts in Oracle Solaris 11.4 and some administrative action data. The following example lists all events for CPUs:
$ sstore list //:class.cpu//:res.id/0//:event.* IDENTIFIER //:class.cpu//:res.id/0//:event.adm-action //:class.cpu//:res.id/0//:event.alert //:class.cpu//:res.id/0//:event.fault
Event information is stored only if you requested the information. The statistics store is not populated with events that existed before event recording started. See the sstore capture command in Using Command Line Interfaces.
The statistics store includes a predefined set of formatting operations for events. Use the fmt keyword in the event SSID to format event information as shown in Formatting Event Information.
In some system object classes, events can be used as aliases to the resources with which they are associated.