HOW IT WORKS: dm_os_ring_buffer vs XEvent *_ring_buffer_reported events

Posted by

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.

Many of the sys.dm_os_ring_buffer entries support matching XEvent (security_error, resource_monitor)_ring_buffer_reported events.

For example:  How It Works: What are the RING_BUFFER_RESOURCE_MONITOR telling me? - Microsoft Tech Community outlines the resource monitor report.

    The logic: When a ring buffer record is recorded the matching XEvent is fired when enabled.

A bit of confusion comes from the naming.  When querying sys.dm_os_ring_buffers the ring buffer name is not the same as the event name.  For example: RING_BUFFER_RESOURCE_MONITOR is the name of the ring buffer, and the event is resource_monitor_ring_buffer_recorded when exposed as the XEvent.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.