Previously, I gave a brief explanation of the concept of “Packages” as it relates to Extended Events (XEvents). In that article, I taught you some basic concepts about packages. However, I did not go deep into some of the granular details such as Extended Events categories.
Packages come with a pair of descriptors (or Extended Events categories). Importantly, you use descriptors to find related events in the package. Therefore, you will find using these descriptors helpful in creating an XEvent session to troubleshoot your specific issue.
XEvents packages have two basic types of categories. In other words, these classifiers are called keywords and channels.
XEvent Channels
An XEvents channel is defined just the same as a radio station or TV channel. Similarly, the XEvents channel indicates a stream of interest. In addition, it identifies the target audience for the event.
| Term | Definition |
|---|---|
| Admin | These events are targeted to administrators and support. Firstly, these events indicate a problem with a solution that an administrator can act on. In addition, these events include a message indicating how to resolve the problem. |
| Operational | Events that are used for analyzing and diagnosing a problem. For instance, one may use these to trigger tasks based on the occurrence. As a result, these events are for Administrators. |
| Analytic | Use these in performance investigations. However, take note that these are a high volume type of events. Consequently, these events are ideal for anybody working on performance issues. |
| Debug | Debug events are used solely by developers to diagnose a problem for debugging. As a result, you will use these primarily when working with CSS. |
Different issues require different channels. As a result, your interest in a Channel will change day by day.
Continue reading on jasonbrimhall.info.
