Geneos - Gateway data handling methodology

The NetProbe sends data from plugins to the Gateway via data structures in normal process memory. The process memory may be swapped to disk by the operating system. No shared memory used and the Gateway does not use in memory databases like Redis or Memcached. 

In general the Gateway holds the sampler data in two forms

• Update messages from the NetProbe are initially stored on in-process queues. 
• The messages are then used to update in-process representations of the dataviews
• New messages are then dispatched to processes such as the Active Console, Obcerv Data Ingestion or a relational database if database logging is configured

In-memory storage of messages and dataviews uses C++ data structures specific to Geneos. Data values are generally held in plain text within these structures but the metadata needed to identify and interpret them is opaque. Database logging updates may be spooled to disk if the database connection is slow or interrupted, but otherwise data from Netprobes will not be written to disk in the course of Gateway processing.

When ActiveConsole displays current data, this is initially supplied from the Gateways's in-memory representation of the dataviews and then maintained by update messages as the data changes. Active Console may also display historical data; this is obtained either by querying Obcerv or from the relational database tables created by database logging.

If you have any further questions:

• Please contact with our Client Services team via the chat service box available in any of our websites or via email to support@itrsgroup.com