ITRS: Geneos, digital monitoring, licensing and support

A Geneos installation separates collection, processing and presentation. Netprobes and Collection Agents acquire measurements; Gateways apply monitoring rules and severity logic; ITRS Analytics stores metrics and logs for analysis. Operators use Active Console, Web Console or Entity Viewer according to the deployment. The distinction matters for capacity and access design: collection agents need visibility into monitored systems, while consoles and analytics need the appropriate paths to the processing layer.[2]

FIX Analyser 2 reads FIX messages from application log files. The documented arrangement places a File Agent on the application server and performs parsing on a separate monitoring server. Local SQLite data supports order-state and latency analysis; an optional external message database supports searches and drilldowns. The specialist FIX Netprobe does not include the standard infrastructure plug-ins, so monitoring the monitoring server itself requires a separate arrangement.[3]

Market Data Monitor normalizes feed inputs through adapters and uses Lua scripts to inspect them. It can compare feeds, detect price spikes and report update rates or latency as Geneos measurements. Adapter support depends on the operating system and feed connection. These capabilities observe incoming data; they do not remove the institution’s need for the relevant market-data subscriptions, and ITRS expressly leaves third-party data charges with the customer.[4]

Opsview publishes plan structures but asks customers to obtain a price. Its host-count recommendations of 150-plus for Essentials and 500-plus for Observability describe intended deployment scale, rather than a stated minimum licence commitment. A host can be a physical device or virtual machine identified by its own IP address. Standard subscriptions are invoiced annually in advance; the MSP model combines an annual base with quarterly overage billing.[5]

Uptrends has public Core and Pro pricing and a custom Enterprise offer. Monitoring capacity is allocated through credits: an uptime monitor uses six, a full-browser monitor 50, a transaction step 50 and an API step 15. Core excludes API and transaction monitoring. Its ten-user limit rises to 25 on Pro and unlimited users on Enterprise. The FAQ says credits reset at annual renewal, although customers can reallocate capacity during the term. Real-user monitoring is an add-on to Core. The practical cost comparison therefore depends on journey length, check type, user count and the purchased credit allocation, rather than the headline plan alone.[7]

Geneos licensing is enforced through a Licence Daemon and a feature-count model covering binaries, plug-ins and selected Gateway functions. Netprobes obtain their entitlements through a Gateway. Licence-file expiry can disable functions, so renewal and replacement files are an operational dependency. The daemon’s monitoring mode records use without the same enforcement behavior; it should not be interpreted as an unrestricted commercial licence.[10]

The Geneos quickstart establishes the Licence Daemon, Gateway, Active Console and Netprobe, then connects managed entities and samplers. A production rollout consequently needs installation permissions, network routes, licence files and monitoring definitions before meaningful alerts appear. Selecting the measurements and severity rules is a substantive part of implementation: the basic component installation does not itself define which business events deserve an incident.[9]

Version selection also affects maintainability. The current compatibility matrix says regular security updates are concentrated on the latest major Geneos release. Support for Licence Daemon versions below 7.8 ended on 31 July 2026, and Intel-based macOS Active Console support ended on 3 August 2026 in favor of Apple Silicon. Supported cloud and container deployment does not extend ITRS support to the underlying customer container platform.[11]

The support centre requires an active agreement and registration using an approved corporate email domain. Its remit includes installation questions, configuration and product defects; large new implementations, custom code and third-party infrastructure fall outside ordinary product support. Although the centre describes 24-hour coverage, telephone handling on weekends and public holidays is restricted to Premium Support customers. Incident severity and a continuously available customer contact affect escalation.[13]

ITRS lists a common maintenance policy alongside its global product terms, with additional SaaS terms where applicable. The legal page directs Uptrends customers to a separate support route. The applicable product, support tier and contract therefore need to travel together when a group-wide monitoring estate is procured.[14]

Geneos encryption is a configuration choice. The secure-communications guide says a normal Netprobe started without secure options accepts unencrypted TCP connections. Secure modes require the appropriate certificates, trust settings and connection configuration. One reversed-role mode encrypts traffic without authenticating the Netprobe, so enabling encryption alone does not settle peer identity. Access design should distinguish transport protection, authenticated components and the privileges granted to operators.[12]

The privacy notice identifies ITRS Group Limited as controller for the personal information covered by that notice, including contact and account interactions. This website and relationship notice should not be substituted for the separate data-processing arrangements governing a customer’s monitoring data. The legal index provides a data-processing addendum for relevant EEA and UK personal data.[15][14]

ITRS Group Limited is an active UK private company, number 02873731, incorporated on 19 November 1993. Its registered office is 15 Bonhill Street, London. The company previously used International Trading Room Software names and, later, ITRS Group PLC. This corporate record establishes the operating entity and history; it does not describe a financial-services permission.[16]

ITRS identifies Montagu and TA Associates as its investors. Its group combines specialist monitoring businesses, so an institution may encounter different product brands and contracting or support arrangements within the same portfolio.[17]

The completed acquisition of IP-Label was announced on 21 January 2026, adding the Ekara digital-experience platform. It follows the July 2021 acquisition of Opsview; that earlier announcement also identifies Sumerian, OP5 and Uptrends among ITRS acquisitions. These names remain relevant when tracing installed products, renewal paperwork and support responsibility.[18][19]

Operator

ITRS Group Limited

Service scope

Infrastructure, application and digital-experience monitoring, including trading-system observability.

Customer types

Investment banks; Exchanges; Hedge funds; Retail banks; Enterprise technology teams

Delivery

SaaS; Hosted; On premises; Hybrid

Pricing publication

Public and quoted pricing

Headquarters

London, United Kingdom

Platforms

Geneos; Opsview; Uptrends; Ekara

Integrations

FIX log analysis; Market-data feed adapters; OpenTelemetry

Pricing scope

Geneos and Opsview use commercial quotations; Uptrends publishes plan pricing and credit allocations.

Implementation

Licensed Geneos components, monitoring definitions and deployment-specific integrations.

Support

Agreement-based product support; Premium conditions apply to weekend and public-holiday telephone coverage.

Permissions and regulatory scope

Operational monitoring software used by financial institutions and other enterprises.

Provider metadata checked 21 Oct 2026Source 16Source 20Source 8Source 1Source 5Source 9Source 13Source 7Source 6

Synthetic monitoring follows a defined journey on a schedule, while real-user monitoring measures what visitors actually experience. The two views answer different operational questions: a scripted check can detect an unavailable path without waiting for a visitor, whereas real-user data reflects the mix of devices, locations and behavior reaching the service. Uptrends offers both, allowing an application team to relate controlled checks to the experience of its users.[6]