This Week in OpenNMS: September 6th, 2017

It's time for This Week in OpenNMS!

Last week was a short week because of the Labor Day holiday, but we continued wrapping up Helm changes and working on bug fixes in preparation for Meridian 2017.

Github Project Updates

  • Internals, APIs, and Documentation

    • I continued my work on getting OpenNMS integration tests to run cleanly in Docker containers. I have the foundation and foundation-2016 branches building cleanly, and have managed to run them on Elastic Bamboo instances, so we're in the home stretch.
    • Christian and Dustin wrapped up their work moving event parms to a separate database table.
    • Jesse worked on a Pagerduty client and notification strategy.
    • Antonio did some refactoring of the bridge topology DAO.
  • Web and UI

    • Markus fixed a bug in how the ReST API throws errors.
    • Jesse did more work on being able to "extend" model objects with extra information in ReST.
    • Markus exposed the ticketing URL in alarm ReSTv2 so it can be used in the UI.
    • Alejandro changed the graph results page to pop-up forecasts like NRTG.
    • I did a bunch of work investigating CXF date-parsing. It turns out it works as designed, FIQL is just weird.
    • Seth worked on improved outage and node list pages with search and typeahead.
    • I fixed UTF-8 handling in ReST integration tests.
    • Jesse worked on making a role that allows acknowledging alarms on behalf of other users.
    • Markus finished up our error handling work in OpenNMS.js.
    • Jesse and Markus added event label, location, and ticket link to the OpenNMS.js model.
    • I fixed ReSTv2 URL-encoding for FIQL in OpenNMS.js.
    • Markus fixed IP address display in Helm.
    • Jesse and Markus added event label, location, and ticket information to Helm.
    • Jesse did other UI cleanup in helm.

Upcoming Events and Appearances

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

  • HELM-4: Move event parameters into their own table
  • HELM-13: Display the event label in the alarms table
  • HELM-31: Provide a link to the ticket in the alarm details modal
  • HELM-39: Show a non crypting error message to the user
  • HELM-46: Provide autocompletion functionality for the "frequently used attributes"
  • HELM-50: Persisted nested Queries are not restored properly
  • HELM-51: Redefine the defaults of the Alarm Table Panel
  • HELM-52: Show event parameter key/values in the alarm table panel
  • HZN-1098: Enhance the v2 REST API to return endpoint meta-data
  • HZN-1143: Use DTOs in REST v2 endpoints for events and alarms
  • HZN-1147: Move event parameters into their own table
  • JS-13: Improper error code handling
  • JS-22: Add capability to fetch values from ReST endpoint
  • JS-23: Map troubleTicketLink
  • JS-24: troubleTicketState is not mapped properly
  • NMS-3915: Adaptive size of interface list on node page
  • NMS-5356: Sort a Nodes IP and Physical Interface List
  • NMS-6207: Rebooting a linux node results in SNMP spikes
  • NMS-8856: Resource graph forecast page lacks header
  • NMS-9456: ClassNotFoundException when running vmwarecimquery/vmwareconfigbuilder
  • NMS-9555: reloadDaemonConfig doesn't work for Eventd, only eventsConfigChange works
  • NMS-9578: Apache CXF is not decoding url parameters correctly.
  • NMS-9602: EventParameterMigratorOffline task fails when eventparms contains empty strings
  • NMS-9605: Error loading node list page (column "event_id" does not exist)

Previous Post Next Post