Update README to include documentation about filtering information via `pep_regex_to_match`

[j-hudecek]

With irods 4.3.3 on Ubuntu 24, and amqp plugin 4.3.3 I get tons of these useless (?) messages:

{
    "tcp_socket_handle" => "0",
       "std_string_ptr" => "",
            "rule_name" => "pep_network_write_header_finally",
           "@timestamp" => 2026-04-20T09:57:58.787Z,
                "ERROR" => "[BytesBuf const*] not supported",
             "hostname" => "u24",
                  "pid" => 35510,
           "std_string" => "tcp",
                "event" => {
        "original" => "\u0000SpE\u0000Ss�\u0000\u0000\u0000'\u0000\u0000\u0000\n@@@@@@�\u0010application/json@@�\u0000\u0000\u0001��SK�\u0000Sw��{\"@timestamp\":1776679078787,\"ERROR\":\"[BytesBuf const*] not supported\",\"hostname\":\"u24\",\"pid\":35510,\"rule_name\":\"pep_network_write_header_finally\",\"std_string\":\"tcp\",\"std_string_ptr\":\"\",\"tcp_socket_handle\":\"0\"}"
    },
             "@version" => "1"
}

is there a way to not emit them so I don't have to filter them out later?

[korydraughn]

The output is tied to the pep_network_write_header_finally PEP.

Is that a PEP you want to track? If not, then you can adjust the regular expression in the plugin configuration to ignore it.

"pep_regex_to_match" : "pep_.+"

See https://cppreference.com/cpp/regex/ecmascript for documentation regarding the regex syntax.

[j-hudecek]

Thanks for looking into it, Kory. Makes sense to look at a smaller subset of PEPs. Perhaps the docs could suggest some that work best?

[korydraughn]

No problem.

We'll update the documentation to include words about the regular expression.

Re-purposing this issue for that.

[SwooshyCueb]

This is being handled in #185