There can be a lot of events in even a small trace, so they're organized into classes to make them easier for you to manage:
(The <sys/trace.h> header file also defines an _NTO_TRACE_EMPTY class, but it's a placeholder and isn't currently used.)
The sections that follow list the events for each class, along with a description of when the events are emitted, as well as the labels that traceprinter and the IDE use to identify the events.
For information about the data for each event, see the Current Trace Events and Data appendix.