ITRS Product Roadmap

At ITRS, we share our Product Roadmap with our clients so that we highlight not just new physical deliverables, but also how they fit in with our company initiatives. These initiatives relate the tangible benefits that our clients see when using ITRS software in their daily lives.


Discovery and Automation

In dynamic or large enterprises, handing the changing infrastructure and applications requires a configuration management system that can adapt.

Central Configuration

Providing Geneos administrators and users with central storage, user interface, and API access to their enterprise monitoring configuration and user profiles.

Data and Event Correlation

Reducing the amount of noise in a system that is consistently having more data added to it is not simple. Enhancing the ability to collect a wide range of data and correlate it through visualisations and algorithms. 

Real-time Data Management

Effective decisions can only be made on the most up-to-date data. A reliable system that is both delivering data to screen and to highly accessible storage is the heart of what makes up real-time monitoring and incident management.

Integrations and Partnerships

Being able to send and receive data from other systems so that ITRS can interface with other best-in-class tools and provide customers with a seamless experience.

User Resources

We deliver not just software products but user resources as well. Delivering information architected to help users understand the software and expand their deployments.

Roadmap by product

  4.10 January 2019 4.11 April 2019 Roadmap 6–12 months

Geneos Real-time Monitoring, Incident and Event Management

  • Active Dashboard object inspector
  • Publishing standardised audit data
  • Data publishing API
  • Hub Kafka publishing
  • Gateway Hub monitoring
  • ServiceNow outbound integration
  • Adaptive rules
  • Reporting templates
  • Property browser
  • Investigative historical charting
  • Log collection and search
  • Complex transaction monitoring
  • New Netprobe data connector
  • Centralised configuration
  • Refreshed Active Console UI

Capacity Planner

  • SSO support
  • Gateway Hub integration
  • Self-solving Forward Thinking scenarios
  • Application demand modelling automation
  • Forward Thinking API

Data Collection

  • Integrations: Gateway Hub, Google Stackdriver, Azure Monitor
  • Control-M plug-in
  • Integrations: Ansible
  • MDM Adapters: Solace
  • Integrations: RabbitMQ, Chef, Puppet, Couchbase, MySQL, KDB
  • VMware bundle
  • In-app bundle for Java
  • Next-generation Netprobe package

ITRS Administration

  • Improved self-announcing Netprobe balancing
  • Netprobe configuration files from remote source
  • Licensing and audit
  • Amazon Gateway AMI
  • Single sign-on user interface
  • Netprobe deployment templates
  • RPM for Linux Netprobe
  • MSI for Windows Netprobe

Resources Websites

  • Context-sensitive help
  • Advanced resource search
  • Expanded useful scripts
  • Persona-driven pathways

Delivery Details

Discovery and Automation

Amazon Gateway AMI — 4.11

The Geneos Gateway, License Daemon & Netprobe will be available as an Amazon Web Services AMI to be loaded into a client’s AWS infrastructure.

Next Generation Netprobe Package

All Windows and Linux Netprobes will include the new Netprobe binary. By default, this will not start or run but can be initialized manually. The first uses of this will be smaller vendor integrations that we have today that will migrate over to the new technology. Over the next few releases after this we will introduce more integrations, replace current plug-ins and provide a simple dynamic configuration system to manage them.

In App Bundle for Java

The in-app monitoring solution includes an in-app bundle and a Java agent. The Java App Agent will be a JAR file that clients can add to the command line of their applications, so no code changes will be required. It will collect metrics available from the JVM about heap and other resource usage, thread, object and method performance. Users will also be able to publish custom metrics to the Netprobe via the In-App API. The In-App bundle will be centrally managed via the Bundle Manager.

RPM for Linux Netprobe

ITRS has administrative responsibilities around download, deployment, installation, initialization and upgrade. By creating a Linux Netprobe RPM package we can help clients standardize the installation and upgrade methods that they use while still working with their in house deployment tools.

MSI for Windows Netprobe

Similar to the RPM Packaging for Netprobes, the Windows MSI will make it easier for clients to Install and upgrade their Windows probes using standard deployment techniques.

Central Administration

Netprobe configuration from remote source — 4.10

Self-announcing and floating probes can now retrieve their configuration file from a remote source, as opposed to a local flat file.

Central configuration — 4.11

Centralise your Gateway configuration files so that you can easily share configurations between them as well as start more instances easier. This is the first step in our journey into a more scalable middleware and more automated Netprobe deployment.

Licensing and audit — 4.11

A next generation of the license daemon. This process will provide better insight into which components of the stack a client is using.

Netprobe Deployment Templates

Creating best practice deployment templates for Ansible, Puppet and Chef for the Netprobe package.

Single Sign On User Interface

The Single Sign On process will now be configured using the new ITRS UI Framework.

Data and Event Correlation

Active Dashboard Object Inspector — 4.10

Dashboard objects change without hitting the apply button. For example, if the user is changing the width of a shape by entering a new value in the textbox for width, once he moves to the textbox for height, the width of the shape object on the canvas should adjust automatically to the new width.

Publishing Standardised Audit Data — 4.10

A new publishing topic with audit data will be available alongside the existing Severity, Snooze and User Assign topics. This information, when combined, can tell a powerful time ordered story for state changes to metrics.

Adaptive Rules — 4.11

Using the Gateway Hub Storage engine users will now be able to reference time series data sets to use as a model for threshold in Geneos Gateway Rules.

Reporting Templates — 4.11

Using the API released with 4.10, we can now interface with standard reporting tools.

Self Solving Forward Thinking Scenarios

With this feature, Capacity Planner will automatically solve optimisation and overcommit scenarios, recommending hardware, storage and new instances automatically within a Forward Thinking Scenario Model.

Application Demand Modelling Automation

More streamlined handling for applications at scale. Automating the identification of constraints and integrating the UI more closely to the Sunburst view.

Forward Thinking API

Describe and run a scenario with no need to use the Capacity Planner API, with results that indicate the changes required to be made. Capture demand in a service management platform and instantly determine the impact of that demand.

Property Browser

A new way to dynamically visualize the state tree allowing the user to select any property available in the path. User can rearrange the path and use this tool to create services that can be used in other tools that ITRS is developing.

Investigative Historical Charting

Using historical data available in the IAF users will be able to overlay events and metrics on the same charts as well as display historical banding overlaid with current data.

Complex Transaction Monitoring

High speed, high volume and complex transactions monitoring . Focusing on market data and trade flow analysis as well as high accuracy latency calculations.

Real-time Data Management

Data Publishing API — 4.10

Outbound query API for data stored in Gateway Hub. This includes the raw data as well as statistical and down-sampled data.

Hub Kafka Publishing — 4.10

The Gateway Hub can publish not just data but schemas to a clients Kafka deployment.

Netprobe Data Connector

As new Netprobe technology is deployed with the current Netprobes there will be a few starting bundles that users can initialize that will not require a configuration system. The Vmware bundle for example. This Netprobe will use a new pipeline to bring data back to users consoles.

Log Collection and Search

Using Netprobe technology Log files are now not just checked for errors but are also streamed to the Gateway Hub cluster. A new UI module allows for searching, pattern matching, statistics and to use in investigation of incidents.

Refreshed Active Console UI

New skin and interactive menus for Active Console users.

MDM Adapters


Integrations and Partnerships

Gateway Hub Monitoring — 4.10

A new dataview showing the publishing rates and health of a Gateway process.

New Plugins — 4.10

Control-M monitoring through BMC’s new REST API.

Cloud Integrations — 4.10

Google Stackdriver, Azure Monitor

Monitoring Integrations — 4.11


VMware Bundle

ITRS first bundle created on the New Netprobe Technology. The VMware bundle collects metrics from the VCenter VSphere service. This data is include both host and guest statistics. These stats are also powerful when sent to ITRS Insights Capacity Planner.

Future Monitoring Integrations

RabbitMQ, Chef, Puppet, Couchbase, KDB

User Resources

Advanced Resource Search — 4.10

Improve the common search facilities across all ITRS Websites.

Context Sensitive Help — 4.10

Syncs the help version with the current schema version so that each section in the GSE directs you to a help page.

Expanded Useful Scripts — 4.10

From the first interactions with clients through to their production deployments our internal teams are always making useful scripts and integrations, so many so that we can’t productise all of them. The useful scripts area of the website is key to providing them to our public for free so that everyone can use them.  

Persona Driven Pathways — 4.11

Ready-made information architecture and flows through the documentation, depending on the user.