Restricting LibreNMS to poll firewall filters / ACLs

Hello,

I noticed that our Juniper devices are having a hard time polling its firewall filters / ACLs, see below output of a device’s SNMP response statistics.
Is there a way to restrict LibreNMS from polling certain areas or modules?
It has become just too much for these poort MX5’s :frowning:

[email protected]> show snmp stats-response-statistics

Average response time statistics:
Stats Stats Average
Type Responses Response
Time (ms)
ifd(non ae) 99547 110.00
ifd(ae) 10956 24.00
ifl(non ae) 10770 37.56
ifl(ae) 46226 142.69
firewall 677 38562.82

Bucket statistics:
Bucket Stats
Type(ms) Responses
0 - 10 148282
11 - 50 15085
51 - 100 4074
101 - 200 605
201 - 500 86
501 - 1000 17
1001 - 2000 2
2001 - 5000 2
More than 5001 23

Bad responses:
Response Request Stats Key
Time Type
(ms) (UTC)
10320.26 2020-05-01 14:34:03 firewall 25Mb
10319.96 2020-05-01 14:34:03 firewall 5Mb
10319.71 2020-05-01 14:34:03 firewall ACCEPT-PPPOE-ONLY-IN
10319.45 2020-05-01 14:34:03 firewall ACCEPT-PPPOE-ONLY-OUT
10311.83 2020-05-01 14:34:03 firewall PROTECT-ROUTER-v4
10301.85 2020-05-01 14:34:03 firewall PartnerCNE-Data_Down
10301.59 2020-05-01 14:34:03 firewall PartnerCNE-Data_Up
10301.34 2020-05-01 14:34:03 firewall PartnerCNE-Voice_Down
10301.11 2020-05-01 14:34:03 firewall PartnerCNE-Voice_Up
10296.41 2020-05-01 14:34:03 firewall SilverMobilityKatwijk
10291.72 2020-05-01 14:34:03 firewall l3vpn-horizon
10291.47 2020-05-01 14:34:03 firewall l3vpn-libernet
10291.22 2020-05-01 14:34:03 firewall l3vpn-mica
10290.99 2020-05-01 14:34:03 firewall police-2M-xe-1/3/0.11427-i
10290.75 2020-05-01 14:34:03 firewall police-2M-xe-1/3/0.11427-o
10290.52 2020-05-01 14:34:03 firewall police-48M-xe-1/3/0.10427-i
10290.28 2020-05-01 14:34:03 firewall police-48M-xe-1/3/0.10427-o
10286.56 2020-05-01 14:34:03 firewall urpf-filter4
10286.15 2020-05-01 14:34:03 firewall urpf-filter6
10285.91 2020-05-01 14:34:03 firewall default_bpdu_filter