`sp_HumanEvents` - Like Predicate Compare

[mattcargile]

Is your feature request related to a problem? Please describe.
Would be nice to discuss or have some level of wildcard handling on parameters like @client_hostname , @database, @username, etc. I imagine you have already thought about it. I couldn't find any issue on the topic, either.

Describe the solution you'd like
First thought was to sniff the characters in the parameters already created and use like behind the scenes. Maybe have a disable like parameter.

Describe alternatives you've considered
Second could be additional parameters directly with like functionality like @client_hostname_like.

Third could be enabling it by default instead of equals and then have a disable option.

Are you ready to build the code for the feature?
Yes, I am ready to build it. Below is the query I was looking at to return the pred% options.

SELECT o.name AS predicate_source_name,
       o.description AS predicate_source_description,
       p.name AS package_name,
       p.description AS package_description,
       o.object_type
FROM sys.dm_xe_objects AS o
     INNER JOIN sys.dm_xe_packages AS p
         ON o.package_guid = p.guid
WHERE o.object_type IN ( N'pred_compare', N'pred_source' )
ORDER BY o.object_type, predicate_source_name ASC;

[erikdarlingdata]

@mattcargile If you truly want to take this on, go for it.

I don't see a reason to add additional parameters. Just look for a % in the string and go from there.

Please just mind the query formatting in your contributions, e.g.

SELECT
    predicate_source_name = o.name,
    predicate_source_description = o.description,
    package_name = p.name,
    package_description = p.description,
    o.object_type
FROM sys.dm_xe_objects AS o
JOIN sys.dm_xe_packages AS p
  ON o.package_guid = p.guid
WHERE o.object_type IN
      (
          N'pred_compare',
          N'pred_source'
      )
ORDER BY
    o.object_type,
    predicate_source_name ASC;