[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opennms-discuss
Subject:    Re: [opennms-discuss] Datacollection mibObj alias length limit
From:       "Roskens, Ronald" <Ronald.Roskens () biworldwide ! com>
Date:       2014-08-08 15:09:05
Message-ID: B6663E208B2DA14DBB3C6FABB9207F7859274210 () BIUSMB1 ! bius ! bi ! corp
[Download RAW message or body]

I think it makes sense to get rid of the 19 character limit. I've heard the newts \
doesn't have this limitation, but I've not seen a RrdStrategy out for it yet.

But that wouldn't help here, since the issue is in the Data Collection classes. They \
need to be modified to pass an un-truncated name through so that the \
truncation/aliasing happens at the RrdStrategy level. (ex: pass the full \
resource/attribute name of "node[X].{resource}[{index}].{alias}" on down) Then if the \
RrdStrategy had limitations, it could be handled there instead of upstream. 

This touches most layers of Data Collection too, so I suspect this would be a pretty \
substantial change.

Ron

-----Original Message-----
From: Smith, Bruce (Mr) [mailto:Bruces@nmmu.ac.za] 
Sent: Thursday, August 07, 2014 6:00 AM
To: 'opennms-discuss@lists.sourceforge.net'
Subject: [opennms-discuss] Datacollection mibObj alias length limit

Good day,

I'd like to start a discussion on whether the 19 character limit of the alias in a \
mibObj is still necessary. RRDTool has this limit, but JRobin does not when run on \
the CLI. OpenNMS truncates the alias name for use as the DS name when creating the \
database file, but uses the original name as the file name. The graph drawing engine \
also appears to use the original name when generating the graphs from the database \
files.

A large number of SNMP MIB object names now exceed the 19 character limit and thus we \
cannot use the proper name in the data collection process, but a hacked-up version \
which may not be clear in meaning to a future administrator.

The question is fairly simple, is there a good reason for keeping the length at 19 \
characters when using the JRobin RRD strategy, or should OpenNMS remove that \
restriction and only enforce it when using the JNI RRD strategy.

Regards,
Bruce Smith

________________________________

NOTICE: Please note that this eMail, and the contents thereof, is subject to the \
standard NMMU eMail disclaimer which may be found at: \
http://www.nmmu.ac.za/disclaimer/email.htm


------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

This e-mail message is being sent solely for use by the intended recipient(s) and may \
contain confidential information.  Any unauthorized review, use, disclosure or \
distribution is prohibited.  If you are not the intended recipient, please contact \
the sender by phone or reply by e-mail, delete the original message and destroy all \
copies. Thank you.

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss


[prev in list] [next in list] [prev in thread] [next in thread]