Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-5062

Enabling DEBUG for Collectd, breaks SiblingColumnStorageStrategy

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.9.93
    • 1.10.0
    • Data Collection - SNMP
    • Security Level: Default (Default Security Scheme)
    • None

    Description

      If DEBUG is not enabled for Collectd, the SiblingColumnStorageStrategy will work as expected, but when DEBUG is enabled, the strategy will fail and it'll use the instance ID instead of the sibling column to identify the resource.

      For example, take a look at dskIndex resources. I expect to see something like:

      macalejo:dskIndex agalue$ pwd
      /Users/agalue/Development/opennms/git/1.10/target/opennms-1.9.94-SNAPSHOT/share/rrd/snmp/6/dskIndex
      imacalejo:dskIndex agalue$ ls -l
      total 0
      drwxrwxr-x 7 root staff 238 Nov 21 20:44 _root_fs/
      drwxrwxr-x 7 root staff 238 Nov 21 20:44 boot/

      But, I'm seeing this:

      macalejo:dskIndex agalue$ pwd
      /Users/agalue/Development/opennms/git/1.10/target/opennms-1.9.94-SNAPSHOT/share/rrd/snmp/6/dskIndex
      imacalejo:dskIndex agalue$ ls -l
      total 0
      drwxrwxr-x 7 root staff 238 Nov 21 13:46 1/
      drwxrwxr-x 7 root staff 238 Nov 21 13:46 2/

      Because this is related with verbosity, I've tracked down the problem and it points to avoid using the method getLabel() from the method toString() on GenericIndexResource.

      I replaced getLabel() with getInstance() on GenericIndexResource and the problem is gone. I need to investigate why.

      Attachments

        Activity

          People

            agalue Alejandro Galue
            agalue Alejandro Galue
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: