CHALLENGE
If you use multiple templates, it is very challenging to verify which template attached to your metrics.
ACTION
All the information is saved into h2 database (snmpcollector.mv.db) and sql technique help you.
(*1) h2 database is accessible via h2 console. (http://<snmpcollector hostname or ip>:9715/database)
(*2) h2 console feature was disabled at some release of snmpcollector and is enabled again in the latest hotfix of 3.43.
----------------------------------------------------------------------------
THIS WILL DISPLAY ALL THE ACTIVE METRICS THAT IS CONTROLLED BY TEMPLATE
----------------------------------------------------------------------------
SELECT d.HOSTNAME, d.IPADDRESS, ca.VALUE, mf.DISPLAYNAME, m.METRICNAME, a.TEMPLATENAME from METRICSTATE m
INNER JOIN ATTRIBUTION a on m.ATTRIBUTION_ID_OID = a.ID
INNER JOIN SNMPDEVICE d on d.DEVICEID = m.PARENTDEVICEID
INNER JOIN COMPONENTGROUP mf on m.METRICFAMILYID = mf.METRICFAMILYID and mf.DEVICEID = m.PARENTDEVICEID
INNER JOIN COMPONENT c on m.METRICFAMILYID = c.METRICFAMILYID and m.COMPONENTSEQUENCEID = c.SEQUENCEID and c.DEVICEID = m.PARENTDEVICEID
INNER JOIN COMPONENT_ATTRIBUTES ca on ca.ID_OID = c.ID and ca.KEY = 'Names'
----------------------------------------------------------------------------
THIS WILL DISPLAY ALL THE ACTIE METRICS THAT IS NOT CONTROLLED BY TEMPLATE
----------------------------------------------------------------------------
SELECT d.HOSTNAME, d.IPADDRESS, ca.VALUE, mf.DISPLAYNAME, m.METRICNAME from METRICSTATE m
INNER JOIN SNMPDEVICE d on d.DEVICEID = m.PARENTDEVICEID
INNER JOIN COMPONENTGROUP mf on m.METRICFAMILYID = mf.METRICFAMILYID and mf.DEVICEID = m.PARENTDEVICEID
INNER JOIN COMPONENT c on m.METRICFAMILYID = c.METRICFAMILYID and m.COMPONENTSEQUENCEID = c.SEQUENCEID and c.DEVICEID = m.PARENTDEVICEID
INNER JOIN COMPONENT_ATTRIBUTES ca on ca.ID_OID = c.ID and ca.KEY = 'Names'
WHERE m.ATTRIBUTION_ID_OID IS NULL