Suggest that datacollection be enhanced to allow for collection of "indirect" OIDS/Indexes

Specifically for cisco CPU monitoring, The CISCO-PROCESS-MIB has no description of the cpus being instumented, only a reference into the ENTITY-MIB..

This is explained at the following URL
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094a94.shtml

This obviously would have other uses, adding the ability to tie together various MIB Tables.

Ultimately what I'd love to see was something similar to...

<resourceType name="cpmPhysIndex" label="cpm CPUIndex"
resourceLabel="entPhysicalName">
<persistenceSelectorStrategy
class="org.opennms.netmgt.collectd.PersistAllSelectorStrategy"/>
<storageStrategy class="org.opennms.netmgt.dao.support.IndexStorageStrategy"/>
</resourceType>

<group name="cpmCPU" ifType="all">
<mibObj oid="1.3.6.1.4.1.9.9.109.1.1.1.1.2"
instance="cpmPhysIndex" alias="cpmCPUTotalPhysicalIndex "
type="Integer" />
<mibObj oid="1.3.6.1.4.1.9.9.109.1.1.1.1.5"
instance="cpmPhysIndex" alias="cpmCPUTotal5min" type="Gauge" />
<mibObj oid="1.3.6.1.2.1.47.1.1.1.1.7"
instance="cpmPhysIndex.cpmCPUTotalPhysicalIndex"
alias="entPhysicalName " type="String" />
</group>
</group>

where the . indicates a property of the previous query..