SlideShare a Scribd company logo

RapidInsight for OpenNMS

•Download as PPT, PDF•
•
M
mberkay

The document summarizes the RapidInsight integration with OpenNMS. RapidInsight is an IT operations management solution that can integrate with OpenNMS to provide additional functionality. The integration populates RapidInsight with alarms and inventory data from OpenNMS. It allows users to access OpenNMS performance graphs and alarms through the RapidInsight UI. RapidInsight provides additional capabilities like dynamic scripting, custom interfaces, notifications, multi-tenancy, topology maps, and visualization when integrated with OpenNMS.

1 of 14
RapidInsight OpenNMS Integration An Overview
RapidInsight is .. RapidInsight is an integration, automation and presentation solution for IT operations management. RapidInsight is designed from the ground up as an open solution using leading web technologies to minimize implementation time and the total cost of ownership.
RapidInsight ...  has an easy to use modelling engine (dynamic, inheritance, operations, relations, etc.)  scales up to support hundreds of users and millions of objects  has a modern, easily extendible, web based user interface  is built on standard technologies  utilizes a standard, full featured, dynamic scripting language  supports multi-tenancy (data segmentation)  has an integrated full text search engine  consolidates data from different sources
RapidInsight OpenNMS Plugin v0.1  Extends OpenNMS seamlessly  Populates RapidInsight repository with alarms and inventory data from OpenNMS  Users can access OpenNMS performance graphs and alarms through RapidInsight UI seamlessly  Current integration uses JDBC to retrieve data from the database. In the future, upcoming REST interface may be used instead.  HTTP is used to retrieve the performance graphs on- demand  Default model in RapidInsight mimics OpenNMS inventory model, but this can be easily modified and/or extended.  Alarm (not events) are retrieved periodically
What does RapidInsight provide today for OpenNMS Users?  Dynamic scripting language to extend/modify solution in the field without having to disturb OpenNMS implementation  Custom web based user interfaces  Self service notifications using OpenNMS alarms  Advanced event management  Multi-tenancy (data segmentation)  Topology maps & Google maps mashup  Ad-hoc monitoring and graphs  Business service management
Self Service Notifications  Users can create filters themselves to specify which alarms they'd like to be notified using simple Google search like queries and point & click.  Users can enable/disable/create/modify filters via the web interface any time (no system restart required)  Notifications are based on OpenNMS alarms instead of events (by default)  Users can specify delay for notifications (send if down more then 5 minutes etc.)  Execute custom scripts to add business logic prior to sending the notification (verification, etc.)
Multi-tenancy (Data segmentation)  Users can only access the objects they are allowed to  Data is segmented by adding an AND clause to all queries executed for the users in the background  Queries can use any object property. Data can come from OpenNMS or other data sources  Process is seamless to the users
Custom Web Interfaces  RapidInsight uses Grails as the web development framework  Highly scalable Ajax web components (grid, tree, etc.) specifically designed to handle large data sets  New web pages can be created using tags with no disruption to the rest of the system  Authorization mechanism to control which users can use which web pages (no restart, etc.)
Advanced Event Management  Add new properties (fields) to events (alarms)  Add in-context actions (acknowledge, change severity, suppress, escalate, etc.) to events  Integrate events with inventory data  Add business data to events from other sources (enrichment)
Topology Maps  Flash based network topology maps  Automatic layouts (hierarchical, circular, etc.)  In-context launch of maps to show just the relevant section of the maps  Support for multiple map types (layer2, layer3, services, etc.)  Can consume map data from other data sources (file, database, etc.)
Google maps integration  Store geographic coordinates or address as device properties  Aggregate devices in same location, and click to see the device list in the location
Visualization  Tree view and Maps can be used to visualize the customers, services and their dependencies  Select an node in the tree to see related info on other components
Ad-hoc monitoring and graphs  Create and populate time series (rrd) data stores from groovy scripts easily (uses jrobin)  Create events when over threshold, etc.
Next Steps  What's missing?  Tell us what you'd like to see  Join the project Project Website: http://www.ifountain.org Screencasts http://www.ifountain.com/rapidinsight/screencasts Demo: http://www.ifountain.com/rapidinsight/demo

More Related Content

RapidInsight for OpenNMS

  • 2. RapidInsight is .. RapidInsight is an integration, automation and presentation solution for IT operations management. RapidInsight is designed from the ground up as an open solution using leading web technologies to minimize implementation time and the total cost of ownership.
  • 3. RapidInsight ...  has an easy to use modelling engine (dynamic, inheritance, operations, relations, etc.)  scales up to support hundreds of users and millions of objects  has a modern, easily extendible, web based user interface  is built on standard technologies  utilizes a standard, full featured, dynamic scripting language  supports multi-tenancy (data segmentation)  has an integrated full text search engine  consolidates data from different sources
  • 4. RapidInsight OpenNMS Plugin v0.1  Extends OpenNMS seamlessly  Populates RapidInsight repository with alarms and inventory data from OpenNMS  Users can access OpenNMS performance graphs and alarms through RapidInsight UI seamlessly  Current integration uses JDBC to retrieve data from the database. In the future, upcoming REST interface may be used instead.  HTTP is used to retrieve the performance graphs on- demand  Default model in RapidInsight mimics OpenNMS inventory model, but this can be easily modified and/or extended.  Alarm (not events) are retrieved periodically
  • 5. What does RapidInsight provide today for OpenNMS Users?  Dynamic scripting language to extend/modify solution in the field without having to disturb OpenNMS implementation  Custom web based user interfaces  Self service notifications using OpenNMS alarms  Advanced event management  Multi-tenancy (data segmentation)  Topology maps & Google maps mashup  Ad-hoc monitoring and graphs  Business service management
  • 6. Self Service Notifications  Users can create filters themselves to specify which alarms they'd like to be notified using simple Google search like queries and point & click.  Users can enable/disable/create/modify filters via the web interface any time (no system restart required)  Notifications are based on OpenNMS alarms instead of events (by default)  Users can specify delay for notifications (send if down more then 5 minutes etc.)  Execute custom scripts to add business logic prior to sending the notification (verification, etc.)
  • 7. Multi-tenancy (Data segmentation)  Users can only access the objects they are allowed to  Data is segmented by adding an AND clause to all queries executed for the users in the background  Queries can use any object property. Data can come from OpenNMS or other data sources  Process is seamless to the users
  • 8. Custom Web Interfaces  RapidInsight uses Grails as the web development framework  Highly scalable Ajax web components (grid, tree, etc.) specifically designed to handle large data sets  New web pages can be created using tags with no disruption to the rest of the system  Authorization mechanism to control which users can use which web pages (no restart, etc.)
  • 9. Advanced Event Management  Add new properties (fields) to events (alarms)  Add in-context actions (acknowledge, change severity, suppress, escalate, etc.) to events  Integrate events with inventory data  Add business data to events from other sources (enrichment)
  • 10. Topology Maps  Flash based network topology maps  Automatic layouts (hierarchical, circular, etc.)  In-context launch of maps to show just the relevant section of the maps  Support for multiple map types (layer2, layer3, services, etc.)  Can consume map data from other data sources (file, database, etc.)
  • 11. Google maps integration  Store geographic coordinates or address as device properties  Aggregate devices in same location, and click to see the device list in the location
  • 12. Visualization  Tree view and Maps can be used to visualize the customers, services and their dependencies  Select an node in the tree to see related info on other components
  • 13. Ad-hoc monitoring and graphs  Create and populate time series (rrd) data stores from groovy scripts easily (uses jrobin)  Create events when over threshold, etc.
  • 14. Next Steps  What's missing?  Tell us what you'd like to see  Join the project Project Website: http://www.ifountain.org Screencasts http://www.ifountain.com/rapidinsight/screencasts Demo: http://www.ifountain.com/rapidinsight/demo