How to catch blocked_process_report_filtered event?

lifeisdao 65 Reputation points

Good day,
I am trying to understand how I can catch blocked_process_report_filtered. I did test with blocked_process_report (without filtered) and it works as planned but at the same time no blocked_process_report_filtered events were caught.
Does somebody know how to catch this specific blocked_process_report_filtered event?

I use standalone instance of Enterprise Editition of SQL Server 2019.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,293 questions
0 comments No comments
{count} votes

Accepted answer
  1. Erland Sommarskog 106.2K Reputation points MVP

    I tested this now on SQL 2019 as well. And indeed, on SQL 2019, this event does not fire. But as I said, it fired on SQL 2022 when I tested.

    I guess then that this is a new event, introduced in SQL 2022. Somehow the metadata about the event has leaked into SQL 2019, but the event itself has not been backported.

1 additional answer

Sort by: Most helpful
  1. Erland Sommarskog 106.2K Reputation points MVP

    That's a little strange. I had never heard of this filtered event before, so I naïvely set up an X-event session with both events. In my case - on SQL 2022, I should hasten to add - both events were fired when there had been blocking longer than the threshold I had set.

    The difference is that the filtered event has less information where potentially sensitive information has been replaced by filtered. For instance:

      <inputbuf>  filtered   </inputbuf>

    Login names and application names were also filtered.