metricsport query returns duplicated / redundant ntor and ntor_v3 values

Summary

Steps to reproduce:

1. Query relay node metrics

What is the current bug behavior?

tor_relay_load_onionskins_total{type="tap",action="processed"} 124
tor_relay_load_onionskins_total{type="tap",action="dropped"} 0
tor_relay_load_onionskins_total{type="fast",action="processed"} 0
tor_relay_load_onionskins_total{type="fast",action="dropped"} 0
tor_relay_load_onionskins_total{type="ntor",action="processed"} 193734
tor_relay_load_onionskins_total{type="ntor",action="dropped"} 0
tor_relay_load_onionskins_total{type="ntor_v3",action="processed"} 193734
tor_relay_load_onionskins_total{type="ntor_v3",action="dropped"} 0

values for ntor and ntor_v3 appear to be duplicates of each other. summed aggregate value of tor_relay_load_onionskins_total will be incorrect unless either ntor or ntor_v3 are manually filtered out.

Environment

• Tor 0.4.7.8
• Debian 11
• Package install from torproject.org debian repos