What would be nice to see is the model classes used under the webapi
extended to the be used inside the event/alarm/notification system. The
fact that you can only use specific %{string}% entries inside
notifications/events that get expanded should be enhanced so that you
could use entries like ${event.message}, ${node.nodelabel},
${notification.rule}, etc. that expand out to their respective values.
On 11/16/2012 10:23 AM, Seibold, Michael wrote:
> Hi Jeff,
>
> just to illustrate one of our problems:
>
> we get traps from brocade devices indicating that Port x/y of Switch abc has
> a problem. Our SAN-Guys configured "PortName" on the switches to contain the
> name of the attached device. We need this name to generate an alarm for the
> "owner" of this device.
>
> We can get it from the
> /opt/opennms/share/rrd/snmp/8/swFCPortIndex/3/strings.properties
>
> Which contains the name of the Port and attached Device
> swFCPortSpecifier=1/2
> swFCPortName=linux0300
>
> but we would like to have this information in the postgres db to use the
> tools like event translator to work on the information.
>
> Also WWN's like MAC-Adresses are very helpful to put somewhere in the db.
>
> Almost everything else we needed up to now is already there in opennms so it
> makes sense to add the rest instead of using something else. But if there is
> a way to do this without changing code I might switch to the other discussion
> list.
>
>
> -Michael
>
>
> -----Ursprüngliche Nachricht-----
> Von: Jeff Gehlbach [mailto:je...@opennms.org]
> Gesendet: Freitag, 16. November 2012 16:56
> An: OpenNMS Code Development and Bugs
> Betreff: Re: [opennms-devel] enhancing FibreChannel Monitoring in OpenNMS
>
> Hi Michael!
>
> On 11/16/2012 08:21 AM, Seibold, Michael wrote:
>
>> 1. Is there already work in progress in this direction where we can
>> join in?
> I've got some work in a feature branch that enables our SNMP collector to
> deal with the funky proto-Counter64 objects that appear in the FCMGMT-MIB.
>
>> 2. Which approach would you suggest for collecting the data?
>> - Add code to the part where nodescan is checking the device and
>> branch there if snmpiftype=56 for fc interfaces
>> - Add code in some part of linkd/provisiond for the devices to be
>> checked if the sysoid points to a known fibre channel equipement
> I admittedly don't have a comprehensive understanding of the FCMGMT-MIB, but
> I don't really understand why code changes would be necessary to enable
> special behavior. If any piece should need code changes, I would think it
> would be the SNMP collector (see above).
>
>> 3. Where do you suggest to store the data?
>> - extend snmpinterface table
>> - add a new table like fcinterface
> Generally, this kind of tabular data can be easily modeled using generic
> resource-types. Have you already tried this and found the approach lacking?
>
>> 4. Any hint where to start in the source code?
> Don't start until you're sure you need to go there :)
>
> -jeff
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single web
> console. Get in-depth insight into apps, servers, databases, vmware, SAP,
> cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> 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
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> 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
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
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
