This is documentation for EA software. It may contain information that is out of date and subject to change. Last updated: 3 October 2018.
This document serves as an introduction to the ITRS Gateway Hub.
It is assumed that you have a good grasp of the way in which Geneos handles architecture and data.
By the end you should understand:
- Why you would want to use Gateway Hub.
- Some of the basic use cases.
- Who in your organisation should be using it.
- Where it fits into the current ITRS Geneos ecosystem.
- The plan for Gateway Hub in the future.
Gateway Hub is part of ITRS Group’s strategy to build better, smarter, more effective monitoring through Geneos. The Gateway Hub provides storage and analytics capabilities, ultimately empowering the Geneos solution, to make real-time monitoring easier and more insightful for customers.
It provides enhanced automation, intelligent predictive solutions, lower operational costs, and help to prevent costly outages.
In 2018, Gateway Hub brings:
- Storage capabilities to support improved access to historical data for all monitored metrics at scale, on a big data platform.
- An open REST API for seamless integration with all ITRS products, including Insights Capacity Planner, and publishing data into third-party tools.
As Gateway Hub evolves it will begin to enable all stored data to be leveraged for smarter rules, simplified incident and anomaly detection, powerful predicative capabilities, and automated decision making preventative actions. Data will be presented through a new UI, offering rich dashboarding and data visualisation.
Historic Geneos data has been identified as a key customer requirement to improve monitoring. Leveraging historical data allows smarter rules, e.g. taking into account daily or hourly variations, rather than simple thresholds. It also gives the ability to investigate why an incident occurred and prevent it from happening again.
In the past, in order to leverage historic data, ITRS experimented with allowing customers to log data to their own SQL database, allowing them to perform their own analysis on historical data. Unfortunately, this did not support the volume of data being processed by Geneos, and customers were forced to choose a subset of their data to log. More recently, Kafka publishing was added to alleviate the performance issue, though again, this is only a one-directional connection; that is, customers cannot directly leverage this data to improve their monitoring.
Gateway Hub's first important development is to store and retrieve all data published from the Gateway, to provide basic metric history which can be retrieved at will. Data is published to Gateway Hub from the Gateway, and in its second release can be retrieved using structured queries via a REST API (as of late 2018). This will initially be available via Active Console, using the history charting feature of Active Dashboard.
The next initiative is to provide the Web Console, a new UI which will be accessed via a browser. The first versions of the Web Console will be concerned with administering Gateway Hub; checking the status of data ingestion from the gateway, and some related administrative functions, e.g. setting the retention policy for dataviews and specifying the time window that retention policies should be applied:
The new intuitive UI which will eventually be rolled out over all ITRS Group solutions will mean that any and all operations staff will likely use Gateway Hub at some point. The historical data will also be available from new UI dashboards for managers and executives that are less likely to use the operational tools.
In order to further accelerate our build, we have decided to partner with MapR, building Gateway Hub on their infrastructure. This will significantly simplify certain aspects of our development such as monitoring and security. It will also significantly simplify the deployment requirements as MapR is an integrated solution.
MapR is based on the open source stack, though some of the components have been replaced by proprietary ones. For example, their implementation of the database layer has been refactored to give better performance when there are lots of files.
The MapR partnership will further accelerate development without affecting ITRS Group's ability to switch back to the open source stack in the future, as MapR is API compatible with the OSS counterparts.
The final advantage of using the MapR stack is that it is likely to reduce the demand on customer hardware requirements, as MapR is faster, and compresses data better resulting in less CPU and disk requirements.
You should now have some understanding of what Gateway Hub is offering to Geneos customers, the advantages it brings, and some of the vision moving forwards. For information on what is coming and when, see the ITRS Product Roadmap.