On 08/09/2012 06:52 AM, jcat wrote: > Do the metric aliases defined in the datacolection.xml file need to be > unique?
Duplicates are legal here, but it's up to the person introducing them to deal with any collisions created as a result. You will lose for sure if you have duplicate aliases within the same <group>. Across groups whose <mibObj> children have disparate values of their "instance" attributes, it's probably fine to have duplicate aliases because of the way the collector persists data. For scalar objects (instance="0" or another numeric constant) it's necessary to evaluate the likelihood that the two objects will ever be collected from the same node (mergers and acquisitions happen). > Can you confirm if this will impact the snmp-graphs at all? See above; every graph definition has a ".type" sub-property that (for the case of data collected via SNMP) maps to the value of the "instance" attribute of the <mibObj> whose alias(es) that graph's ".columns" subproperty names. This provides a degree of collision mitigation, but you still need to be mindful. -jeff ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
