When Infrastructure agent log level is set to DEBUG, the logging from hostmonitoring extension is hard to control and soon swamps the IntroscopeAgent.log.
Some log messages are written to logger IntroscopeAgent.SnmpCollector so can be disabled by setting log level on that logger to INFO. However many are written to IntroscopeAgent.InfrastructureAgent and so can't be disabled without also disabling DEBUG logging from most of the rest of the Infrastructure agent which may be needed to diagnose configuration issues.
Specifically there are many repeated log sections such as:
[DEBUG] [IntroscopeAgent.InfrastructureAgent] Received an empty OID vector for 1.3.6.1.2.1.4.32.1.2
[DEBUG] [IntroscopeAgent.InfrastructureAgent] Received an empty OID vector for 1.3.6.1.2.1.4.32.1.4
[DEBUG] [IntroscopeAgent.InfrastructureAgent] Received an empty OID vector for 1.3.6.1.4.1.546.12.1.1.2
Do these indicate a configuration error or possibly some config which does not apply to the current operating system or version? Can configuration be adjusted to stop these being logged? If not, can the number of repeats of these be reduced? They seem to appear approximately every 15 seconds.
Look up the oid2metrics json file for the corresponding metric mappings of these OIDs, e.g. 1.3.6.1.2.1.4.32.1.2 - "SystemEdge|{$HostName}|Network|IP|IPAddressPrefix|{TABLE:INetAdderss}:Type" and 1.3.6.1.4.1.546.12.1.1.2 - "SystemEdge|{$HostName}|DiskIO|{TABLE:DiskName}:Average Operations Wait Queue" for instances, and the host name usually shown in another DEBUG message summing up this query run to help figure out why these OID queries would have empty results and whether any correction would be required to prevent having their occurrences again
There are various free snmp get like utilities . Many of these are included by default or can be found in vendor os repos.