Description of problem:
using nftrace tracing one can mark less or more specific traffic to be traced and reported via nft monitor command. the output prints out *all* packet traces without without a way to filter which particular trace rule enabled the tracing.

Each event in a single trace is printed on a separate line, thus making reading of the trace very difficult especially when they overlap and if there are more than one rule enabling/disabling the tracing.

Scenario: there's traffic to two services coming from two hosts, I can set trace for all incoming traffic, for traffic coming from one of the hosts or towards one or both of the services. An instance of nft monitor is used to get the some of the traffic while other instance for other parts of the traffic. This could help a lot with aggregating the data for immediate or later use from the same time window.

The RFE is for ability to filter traffic by a key or some part of the context the trace contain like: ip header, nft objects, tcp payload, packet marks or specific nftrace mark key.
e.g.
nft monitor trace ip saddr ::1
nft monitor trace ip6 filter INPUT
nft monitor trace tcp dport 25
nft monitor trace mark mouse
nft monitor trace trace_key_str # see note bellow
 * this would move specification of the filter to the rule itself rather than to the monitor but probably also require a netfilter update

Version-Release number of selected component (if applicable):
nftables-0.9.3-4.el8.x86_64

How reproducible:
always

Steps to Reproduce:
nft -f - <<EOF
table inet trace_t {
	chain ch {
		type filter hook input priority filter; policy accept;
		tcp dport 25 meta nftrace set 1
	}
}
EOF
nft monitor trace &
nc localhost 25

Actual results:
a verbose output of trace events linked by an id in 3rd column. without a parser or a low traffic this is rather difficult to use
>example output:
trace id bb59767d inet trace_t inch packet: iif "lo" @ll,0,112 34525 ip6 saddr ::1 ip6 daddr ::1 ip6 dscp cs0 ip6 ecn not-ect ip6 hoplimit 64 ip6 flowlabel 43505 ip6 nexthdr tcp ip6 length 40 tcp sport 46356 tcp dport 25 tcp flags == syn tcp window 43690 
trace id bb59767d inet trace_t inch rule tcp dport 25 meta nftrace set 1 (verdict continue)
trace id bb59767d inet trace_t inch verdict continue 
trace id bb59767d inet trace_t inch policy accept 
trace id bb59767d ip6 filter INPUT verdict continue 
trace id bb59767d ip6 filter INPUT policy accept 
trace id bb59767d inet firewalld filter_INPUT packet: iif "lo" @ll,0,112 34525 ip6 saddr ::1 ip6 daddr ::1 ip6 dscp cs0 ip6 ecn not-ect ip6 hoplimit 64 ip6 flowlabel 43505 ip6 nexthdr tcp ip6 length 40 tcp sport 46356 tcp dport 25 tcp flags == syn tcp window 43690 
trace id bb59767d inet firewalld filter_INPUT rule iifname "lo" accept (verdict accept)
trace id bb59767d ip6 security INPUT verdict continue 
trace id bb59767d ip6 security INPUT policy accept 
trace id 820a27e1 inet trace_t inch packet: iif "lo" @ll,0,112 2048 ip saddr 127.0.0.1 ip daddr 127.0.0.1 ip dscp cs0 ip ecn not-ect ip ttl 64 ip id 46216 ip protocol tcp ip length 60 tcp sport 60948 tcp dport 25 tcp flags == syn tcp window 43690 
trace id 820a27e1 inet trace_t inch rule tcp dport 25 meta nftrace set 1 (verdict continue)
trace id 820a27e1 inet trace_t inch verdict continue 
trace id 820a27e1 inet trace_t inch policy accept 
trace id 820a27e1 ip filter INPUT verdict continue 
trace id 820a27e1 ip filter INPUT policy accept 
trace id 820a27e1 inet firewalld filter_INPUT packet: iif "lo" @ll,0,112 2048 ip saddr 127.0.0.1 ip daddr 127.0.0.1 ip dscp cs0 ip ecn not-ect ip ttl 64 ip id 46216 ip protocol tcp ip length 60 tcp sport 60948 tcp dport 25 tcp flags == syn tcp window 43690 
trace id 820a27e1 inet firewalld filter_INPUT rule iifname "lo" accept (verdict accept)
trace id 820a27e1 ip security INPUT verdict continue 
trace id 820a27e1 ip security INPUT policy accept 

Expected results:
ability to filter traffic by a key or some part of the context the trace contain like: ip header, nft objects, tcp payload, packet marks or other

Additional info: