rbacon | 3 May 22:40 2016

Export for dummies

I am sorry to say I inherited a network using openNMS and have never used it
before. I wanted to get a peg count for every event on the network and while
openNMS is set up to email each event I do not see where I can get a file of
each event. I am just hoping to see 1 thing really list of each device with
the number of events in the last "x" of time. Is anyone able to help. I
searched the forum for a bit but didn't see anything clearly, and online was
worse still. Thank you to anyone willing and able to help.

Ron

--
View this message in context: http://opennms.530661.n2.nabble.com/Export-for-dummies-tp7593734.html
Sent from the OpenNMS - discuss mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
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

(Continue reading)

Peter Ivanyi | 3 May 16:51 2016
Picon

Possible SNMP table query bug related to topology

Dear Developers!

I have the following problem. I am teaching at a university and I try to
demonstrate the use of NMS for students with OpenNMS. We have
some industrial ethernet switches. They are discovered and managed
properly by OpenNMS, but there is a problem with the topological map.
(Actually I think the bug is with the SNMP query.)

For the enlinkd daemon only LLDP is enabled. OpenNMS gets the
LLDP data from the switches via SNMP. According to your documentation
(https://www.opennms.org/wiki/Linkd) the daemon gets three groups:
lldpLocalGroup, lldpLocTable, lldpRemTable.
My problem is that only one entry of the lldpRemTable table is shown
by OpenNMS. The entry with zero and the incremented by one entries.

I have queried this table myself by snmpwalk (from net-snmp) and by some
other programs as well and, I see that the indexes sometimes do not start
from zero and the indexes are not incremented by one in the table.
For example I get the following OIDs from the table, when
there are two neighbouring switches:
iso.0.8802.1.1.2.1.4.1.1.1.0.11.2
iso.0.8802.1.1.2.1.4.1.1.1.2000.11.2
...
It seems to me that in the table, the indexes are not consequtive.
In the case of another switch the first index is not even zero,
iso.0.8802.1.1.2.1.4.1.1.1.45633.11.2

OpenNMS does not display these entries! I suspect, that the daemon
does not even query these entries by SNMP! I think it could be a bug
in the SNMP query!
(Continue reading)

Benjamin Reed | 2 May 19:43 2016
Gravatar

This Week in OpenNMS: May 2nd, 2016

It's time for This Week in OpenNMS!

In the last week we worked on the BSM, topology maps, Minion, the TSRM ticketing plugin, JMX data collection configuration, Newts, Documentation, Requisitions, Compass, and bug fixes.


Github Project Updates

  • Business Service Monitor and Topology Maps

This week was more of Jesse, Ronny, and Markus wrapping up BSM for Horizon 18. Jesse did a ton of performance work on loading Enlinkd data into the topology UI, bringing his test set load time down from 5 minutes down to 5 seconds.

  • OSGi Updates and Minion
Seth spent some time working on various issues related to Karaf — updating our embedded Karaf container, as well as more work on getting Minion-related code loading.
  • TSRM Ticketing Plugin
Chandra finished wrapping up the IBM TSRM plugin and has merged it into the Horizon 18 branch.
  • JMX Data Collection
Jesse updated the JMX data collection configuration to support split files in the jmx-datacollection-config.d directory.
  • Newts and Cassandra Performance Investigation
Jesse spent some time investigating a performance issue reported by a number of our customers related to Newts and Cassandra. It turns out the issue was related to default logging levels and the Cassandra driver, and the fix was as simple as adding this to your OpenNMS log4j2.xml file:
<logger name=”com.datastax.driver” additivity=”false” level=”INFO”>
   <appender-ref ref=”RoutingAppender”/>
</logger>
  • Documentation
Chandra, Seth, Ronny, Jesse, and Sven Reissmann have updated documentation in multiple places in preparation for Horizon 18. It is also now possible to view the documentation in the “opennms-doc” package from the OpenNMS web UI by default.
  • Requisitions
Alejandro has done a bit more cleanup and fixing of the Requisitions UI for Horizon 18.
  • Compass
I spent more time this last week cleaning up small things and fixing a few bugs in Compass. I also beefed up the (almost nonexistent) analytics inside Compass, and added an opt-out for analytics tracking. If you’d like to help beta test Compass, see the Compass web site: https://compass.opennms.io/#beta
  • Bug Fixes

A lot of other minor bug fixes have been going in in preparation for OpenNMS Horizon 18.


OpenNMS Horizon 18 Due Monday, May 9th

Barring any last-minute bugs we may discover in testing, the Horizon 18 branch is finished and our plan is to release next Monday, May 9th. If you have a test setup, please give the OpenNMS 18 snapshots a try and let us know if you run into any issues; this is shaping up to be a really nice release. Just change your yum or apt configuration to use “snapshot” instead of “stable” and you’ll get the snapshot builds. While we are prepping 18, “snapshot” points to the release branch, rather than develop.

Upcoming Events and Appearances

The OpenNMS Group has scheduled our next training session in Pittsboro, NC for June 13th through 17th. For more details on OpenNMS training and signing up, see The OpenNMS.com training page: http://www.opennms.com/training

Dev-Jam 2016 is sneaking up on is, but there is still plenty of time to join us in Minnesota. For more information, see The Dev-Jam 2016 wiki page: https://www.opennms.org/wiki/Dev-Jam_2016

Mike Huot has written up a proposal letter you can use to help explain to management why attending Dev-Jam is a good idea. Feel free to copy this letter and join us in Minnesota this year: https://docs.google.com/document/d/1VerZYe5LwMT_1j5ISAsNU9-ZGcwY_zdA_4DODNlBpYg/edit?usp=sharing


Until Next Week…

If there’s anything you’d like me to talk about in a future TWiO, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.


– Ben


Resolved Issues Since Last TWiO

  • BSHIFT-11: traffic in/out utilization does not render properly
  • HZN-645: IBM TSRM Ticketing Plugin
  • HZN-652: Refactor ServiceMonitorLocator to use onmsgi to look up ServiceMonitors
  • HZN-657: Write a Minion feature definition for opennms-poller-monitors-core
  • HZN-688: Create user documentation for the BSM components
  • HZN-715: Define a model for “sub graphs”
  • HZN-716: Design Atlas
  • HZN-717: Prototype import of the data
  • HZN-726: Use “vm” ActiveMQ transport by default
  • NMS-5915: The retry handler used with HttpClient is not going to do what we expect
  • NMS-7731: Remote poller dies when trying to use the PageSequenceMonitor
  • NMS-7846: Slow LinkdTopologyProvider/EnhancedLinkdTopologyProvider in bigger enviroments
  • NMS-7976: Merge OSGi Plugin Manager into Admin UI
  • NMS-8080: VLAN name is not displayed
  • NMS-8198: Provisioning UI indication for changed nodes is too bright
  • NMS-8353: Plugin Manager fails to load
  • NMS-8361: Incorrect documentation for org.opennms.newts.query.heartbeat
  • NMS-8362: nodelink.jsp shared segment without ports
  • NMS-8365: Add metric counter for drop counts when the ring buffer is full
  • NMS-8366: OpenNMS Incompatible with Debian Stretch and Ubuntu 16.04
  • NMS-8373: The placeholder {diffTime} is not supported by Backshift.
  • NMS-8374: The logic to find event definitions confuses the Event Translator when translating SNMP Traps
  • NMS-8375: License / copyright situation in release notes introduction needs simplifying
  • NMS-8377: Applying some organizational changes on the Requisitions UI (Grunt, JSHint, Dist)
  • NMS-8379: Sluggish performance with Cassandra driver
  • NMS-8381: dashboard and ops board not working
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
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
Craig Gallen (OpenNMS | 30 Apr 10:07 2016

TM Forum hack Nice France

For anyone interested near by there is a tmforum hackathon in Mice from friday 6 May to sunday 8th May next week.
I am representing OpenNMS. Anyone wanting to join our team please sign up below and contact me at cgallen <at> opennms.org

http://www.google.co.uk/url?q=http://www.tmforumlive.org/open-hack

Hope you can make it.
Thanks
Craig


------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
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
Craig Gallen (OpenNMS | 30 Apr 09:54 2016

(no subject)

For anyone interested near by there is a tmforum hackathon in Nice France from friday 6 May to sunday 8th May next week.
I am representing OpenNMS. Anyone wanting to join our team please sign up below and contact me at cgallen <at> opennms.org

http://www.google.co.uk/url?q=http://www.tmforumlive.org/open-hack

Hope you can make it.
Thanks
Craig


------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
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
Madden, Joe | 28 Apr 16:57 2016

Random Alert for Cisco Devices

Hi All,

 

We use SNMP V3 to monitor cisco devices in our network which is now working well. However randomly we will get the following message showing up on a few of the devices:

 

Warning               Incorrect Community Name (authenticationFailure Trap) enterprise:.1.3.6.1.6.3.1.1.5.5 (.1.3.6.1.6.3.1.1.5.5) args(3):.1.3.6.1.4.1.9.2.1.5.0="10.59.31.66" .1.3.6.1.4.1.9.9.412.1.1.1.0="1" .1.3.6.1.4.1.9.9.412.1.1.2.0="ipaddressofsystem"

 

Presumably, OpenNMS is trying to connect using “public” and SNMPv3 on the specific host to see what it gets – Is there any way to stop OpenNMS doing this?

 

I guess removing it out of the discovery would do it?

 

Joe

 

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
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
Gibson, Daniel P | 27 Apr 21:37 2016

Please Help with LDAP activeDirectory.xml

G’ day OpenNMS Gurus,

 

I am still struggling with my ldap authentication.  I know the login authentication is working and my Admins are gaining full access…but my standard users are getting logged in but I get the “Permission Denied” page as it seems the USER_ROLE mapping isn’t being recognized.

 

Can someone who understands the xml file see if anything looks abnormal or may be missing…this is a major road block in getting this tool implemented here at my company.  Items in Red are my definitions, but changed for security reason…just cannot get standard users to work…

 

Please, any and all help greatly appreciated,

Danny

 

 

<?xml version="1.0" encoding="UTF-8"?>

<beans:beans xmlns="http://www.springframework.org/schema/security"

  xmlns:beans="http://www.springframework.org/schema/beans"

  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

  xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd

              http://www.springframework.org/schema/security http://www.springframework.org/schema/security/spring-security-3.1.xsd">

 

  <beans:bean id="ldapTemplate" class="org.springframework.ldap.core.LdapTemplate">

    <beans:constructor-arg ref="contextSource"/>

    <beans:property name="ignorePartialResultException" value="true"/>

  </beans:bean>

  <beans:bean id="contextSource" class="org.springframework.ldap.core.support.LdapContextSource">

    <beans:property name="urls">

      <beans:list>

        <!-- List one or more of your Active Directory domain controllers here -->

        <beans:value>ldap://abc.mycompany.org:389/</beans:value>

      </beans:list>

    </beans:property>

    <!-- An optional base DN. Every user and group below is relative to this. -->

    <beans:property name="base" value="dc=abc,dc=mycompany,dc=org" />

    <beans:property name="authenticationSource" ref="authenticationSource" />

  </beans:bean>

  <beans:bean id="authenticationSource" class="org.springframework.ldap.authentication.DefaultValuesAuthenticationSourceDecorator">

    <beans:property name="target" ref="springSecurityAuthenticationSource"/>

    <!-- Identify an unprivileged user for initial binding to the directory -->

    <!-- In some cases, expressing the user as an LDAP DN is the right way -->

    <!-- In other cases, it's necessary to express it in user <at> domain format -->

    <!-- <beans:property name="defaultUser" value="opennms_bind <at> example.org"/> -->

    <!-- Specify the unprivileged bind user's password here -->

    <beans:property name="defaultUser" value="myuser <at> myCompany.org"/>

    <beans:property name="defaultPassword" value="catfur4U"/>

  </beans:bean>

 

  <beans:bean id="springSecurityAuthenticationSource" class="org.springframework.security.ldap.authentication.SpringSecurityAuthenticationSource">

  </beans:bean>

 

  <beans:bean id="externalAuthenticationProvider" class="org.springframework.security.ldap.authentication.LdapAuthenticationProvider">

    <beans:constructor-arg ref="ldapAuthenticator"/>

    <beans:constructor-arg ref="userGroupLdapAuthoritiesPopulator"/>

  </beans:bean>

 

  <beans:bean id="ldapAuthenticator" class="org.springframework.security.ldap.authentication.BindAuthenticator">

    <beans:constructor-arg ref="contextSource"/>

    <beans:property name="userSearch" ref="userSearch"></beans:property>

  </beans:bean>

  <!-- userSearch (alt.: userDnPatterns) -->

 

  <beans:bean id="userSearch" class="org.springframework.security.ldap.search.FilterBasedLdapUserSearch">

    <beans:constructor-arg index="0" value="ou=UserAccounts" />

    <!-- More complex filters are possible depending on the layout of your directory -->

    <beans:constructor-arg index="1" value="(sAMAccountName={0})" />

    <beans:constructor-arg index="2" ref="contextSource" />

    <beans:property name="searchSubtree" value="true" />

  </beans:bean>

 

  <beans:bean id="userGroupLdapAuthoritiesPopulator" class="org.opennms.web.springframework.security.UserGroupLdapAuthoritiesPopulator">

    <beans:constructor-arg ref="contextSource"/>

    <!-- Common LDAP container for the user and admin groups listed below -->

    <beans:constructor-arg value="ou=UserGroups,ou=UserAccounts" />

    <!-- <beans:constructor-arg value="ou=UserGroups,ou=UserAccounts" /> -->

    <beans:property name="searchSubtree" value="true" />

    <beans:property name="convertToUpperCase" value="true" />

    <beans:property name="groupRoleAttribute" value="cn" />

    <!-- <beans:property name="groupSearchFilter" value="member={0}" /> -->

    <!-- If using nested AD groups, try the following groupSearchFilter instead  -->

    <!-- <beans:property name="groupSearchFilter" value="member:1.2.840.113556.1.4.1941:={0}" /> -->

    <beans:property name="groupSearchFilter" value="member={0}" />

    <beans:property name="groupToRoleMap">

      <beans:map>

        <beans:entry>

          <!-- Name of the AD group for OpenNMS administrators -->

          <beans:key><beans:value>My_Admins</beans:value></beans:key>

          <beans:list>

            <beans:value>ROLE_USER</beans:value>

            <beans:value>ROLE_ADMIN</beans:value>

          </beans:list>

        </beans:entry>

        <beans:entry>

          <!-- Name of the AD group for normal (non-admin) OpenNMS users -->

          <!-- <beans:key><beans:value>Domain Users All_ITS_Staff</beans:value></beans:key> -->

          <beans:key><beans:value>My_Staff</beans:value></beans:key>

          <beans:list>

            <beans:value>ROLE_USER</beans:value>

            <!-- <beans:value>ROLE_DASHBOARD</beans:value> -->

          </beans:list>

        </beans:entry>

      </beans:map>

    </beans:property>

  </beans:bean>

</beans:beans>

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
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
kalle.carlbark | 27 Apr 20:17 2016
Picon

A more optimized way to retrieve measurement data (disk information)?

Hi,

I hope I post this to the correct mailing list and sorry for my inadequate english skills.

I hope some of you understands some of it at least :)

So, since http://issues.opennms.org/browse/NMS-8242 came in to play for us after upgrading to 17.1.1 we needed to change the way how we retrieve disk information (disk size, used storage, etc) for all nodes (Windows and Linux) from OpenNMS (We have about 5000 of these nodes) and put this disk information in an external system/database.
We looked at measurement API via ReST to get this information instead. Although this is working fine (thank you very much for this feature) we do see some potential to perhaps improve our workflow/process a bit. Right now we need to:

1. Ask OpenNMS via ReST for all resources, ie GET /opennms/rest/resources/
2. By using the response from step 1 and parsing out the correct data we can build a XML and POST this to /opennms/rest/measurement[*]
3. By using the response from step 2 we can now parse out the necessary disk information and put it in our external database for the right node.

This takes time and complex code to get what we need. Some questions:

First of all I would like to ask, are we doing it right<tm>?
I understand that the measurement API was perhaps not built for these kinds of queries?
Are there any better ways to get the disk information we need?
Could we optimize our current way somehow?
If we store the measurement data in newts/cassandra would that somehow help us to retrieve the information faster directly from there?
Do you see any improvements on the horizon for ReST that would ease our current workflow?


[*]A side note, if asking for _all_ disk measurements in step 2 the process takes a very long time. So we have shrunk the XML to only include queries for 500 resources per POST which resulted in a faster response.


Thank you!

Best regards,
Kalle Carlbark
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
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
Ronny Trommer | 26 Apr 21:32 2016
Gravatar

DevJam 2016 - Travel Bursary

Hello, 

Just to inform you the OpenNMS Foundation Europe e.V. provides a travel bursary for DevJam 2016. If you are interested and it is mostly used for people who have no strong financial or commercial background around OpenNMS and want to attend. You find all the details here


If you still have questions don’t hesitate and drop me a mail

Greetings Ronny


------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
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
sricharan.rekanar | 24 Apr 15:02 2016
Picon

RTTMON Graph

Hi,

       I have configured IP SLA 1 on Cisco switch for monitoring the RTD and
Packet loss with icmp-echo to a destination IP. Installed OpenNMS 17.1.1 in
windows server 2008 OS.

Switch# ip sla 1
icmp-echo 172.168.10.3
timeout 300
threshold 50
tag OpenNMS Test
frequency 10
ip sla schedule 1 life forever start-time now

       OpenNMS is learning the RTTMON Index 1 IP SLA strings, under the
CISCO switch 3750. But not able to populate any of the graphs apart from the
ICPIF. 

          Please can you help in plotting the RTT, Jitter and packet loss
graphs.

Regards,
Sri

--
View this message in context: http://opennms.530661.n2.nabble.com/RTTMON-Graph-tp7593708.html
Sent from the OpenNMS - discuss mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
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

Benjamin Reed | 25 Apr 22:22 2016
Gravatar

This Week in OpenNMS: April 25th, 2016

It's time for This Week in OpenNMS!

In the last week we worked on BSM, topology maps, the TSRM ticketing plugin, Slack and Mattermost notifications, Grafana, Compass, and Horizon 18 bug fixes.


Github Project Updates

  • Business Service Monitor and Topology Maps

This week was Jesse, Ronny, and Markus continued their work on wrapping up BSM for Horizon 18, with topology UI cleanups, documentation, and more bug squashing. Antonio’s fixes to the Enlinkd topology provider have also been merged into Foundation 2016 as of this morning.

  • TSRM Ticketing Plugin

Chandra’s IBM TSRM plugin works an this week he has been working on adding support for more field mappings between OpenNMS ticketing and TSRM.

  • Slack and Mattermost Notification Plugins

Jeff added support for Slack and Mattermost as notification targets. Additionally, the Mattermost plugin uses Mattermost’s enhanced markdown support for formatting.

  • Grafana 3.0 Plugin

Jesse re-engineered the OpenNMS Grafana plugin for Grafana 3.0. It is now available directly from the Grafana plugin marketplace so it no longer requires installing extra packages: https://grafana.net/plugins/opennms-datasource

  • Compass

Compass 2.1.0 betas are progressing with a number of fixes and small improvements. The memory-usage crash has been squashed, and there are just a few more small things to tweak before I release it. If you’d like to help beta test, see the Compass web site: https://compass.opennms.io/#beta

  • Bug Fixes

A lot of other minor bug fixes have been going in in preparation for OpenNMS Horizon 18.


Upcoming Events and Appearances

The OpenNMS Foundation Europe is having its General Assembly meeting on April 22nd, 2016. For details on the agenda and contact information, see this post on the OpenNMS discuss mailing list: http://permalink.gmane.org/gmane.network.opennms.general/52706

The OpenNMS Group has scheduled our next training session in Pittsboro, NC for June 13th through 17th. For more details on OpenNMS training and signing up, see The OpenNMS.com training page: http://www.opennms.com/training

Dev-Jam 2016 is sneaking up on is, but there is still plenty of time to join us in Minnesota. For more information, see The Dev-Jam 2016 wiki page: https://www.opennms.org/wiki/Dev-Jam_2016

Mike Huot has written up a proposal letter you can use to help explain to management why attending Dev-Jam is a good idea. Feel free to copy this letter and join us in Minnesota this year: https://docs.google.com/document/d/1VerZYe5LwMT_1j5ISAsNU9-ZGcwY_zdA_4DODNlBpYg/edit?usp=sharing


Until Next Week…

If there’s anything you’d like me to talk about in a future TWiO, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.


– Ben


Resolved Issues Since Last TWiO

  • HZN-645: IBM TSRM Ticketing Plugin
  • HZN-649: Load features/poller/monitors/core as an OSGi bundle
  • HZN-651: Prototype Atlas Topology Provider
  • HZN-652: Refactor ServiceMonitorLocator to use onmsgi to look up ServiceMonitors
  • HZN-662: Create an OSGI-INF blueprint to expose ServiceMonitors as OSGi services
  • HZN-666: Generate alarms for business services
  • HZN-703: Change blueprint-trapd-handler-minion.xml to use Minion ActiveMQ Component
  • HZN-710: The Threshold Function should be explained
  • HZN-711: Highest severity above is inclusive
  • HZN-713: Root cause and impact analysis should also show the entire map
  • NMS-6521: PageSequenceMonitor fails to unmarshal configuration
  • NMS-7792: NPE in JmxRrdMigratorOffline
  • NMS-7854: Translated events with a new UEI do not receive the description, severity and alarm-data of the new event if new UEI’s eventconf is present after original UEI’s eventconf
  • NMS-7872: 303 See Other on requisitions response breaks the usage of the Requisitions ReST API
  • NMS-7922: Null pointer exceptions with whitespace in requisition name
  • NMS-7976: Merge OSGi Plugin Manager into Admin UI
  • NMS-8041: Refactor Enhanced Linkd Topology
  • NMS-8080: VLAN name is not displayed
  • NMS-8096: JMX detector connection errors use wrong log level
  • NMS-8098: PageSequenceMonitor sometimes gives poor failure reasons
  • NMS-8129: Disallow restricted characters from foreign source and foreign ID
  • NMS-8330: Switching Topology Providers causes Exception
  • NMS-8334: Implement org.opennms.timeseries.strategy=evaluate to facilitate the sizing process
  • NMS-8336: Set the required fields when not specified while adding events through ReST
  • NMS-8337: Non-existing resources or attributes break JasperReports when using the Measurements API
  • NMS-8346: Add Mattermost and Slack notification strategies
  • NMS-8349: Update screenshots with 18 theme in user documentation
  • NMS-8366: OpenNMS Incompatible with Debian Stretch and Ubuntu 16.04
  • NMS-8371: The contents of the info panel should refresh when the vertices and edges are refreshed
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
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

Gmane