FilterOption_FiltersOutSpecifiedCommands issues commands, and even if all commands are filtered out the driver still tries to connect to an instance, making it more of an integration test. To work as expected it needs the [SkipUnlessEnvVarFoundTheory(RedisEndPointEnvVarName)] attribute added and then the connection setup modified to respect that env var.

A filter specific test can be added to RedisProfilerEntryToActivityConverterTests that does not require a connection:

    [Fact]
    public void ProfilerCommandToActivity_UsesFilter()
    {
        var activity = new Activity("redis-profiler");
        var profiledCommand = new TestProfiledCommand(DateTime.UtcNow);
        var options = new StackExchangeRedisInstrumentationOptions
        {
            Filter = command => false,
        };
        var result = RedisProfilerEntryToActivityConverter.ProfilerCommandToActivity(activity, profiledCommand, options);
        Assert.Null(result);
    }
    ```

Pull Request Overview

Adds a Filter option to StackExchangeRedisInstrumentationOptions enabling early filtering of profiled commands.

• Introduce a Filter property on the options class
• Apply the filter in ProfilerCommandToActivity to skip unwanted commands
• Update tests, changelog, and public API to include the new option

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

/// <summary>

public void FilterOption_FiltersOutSpecifiedCommands(string value)