Solace Geneos Agent

Solace Geneos Agent is a Solace component which enables Geneos Enterprise Management to access message broker data that might be of interest to network or solution administrators/operators that want to create ITRS data views for the ITRS Geneos Enterprise Management product. This agent represents one component of the Geneos Enterprise Management Solution.

The figure below shows the key components of this solution.

Solace and ITRS Geneos Interaction

  • Active Console—The GUI component for the system presents the console views and the dashboard. It contains a number of objects which allow you to navigate, control, and organize the data collected from the message broker and other third-party vendors.
  • Gateway—A Gateway is responsible for storing historical data, executing customer-defined rules on newly received data, and generating notifications based on network events or status changes. It receives data that is pushed to it by the Geneos NetProbes in the network. A single Geneos Gateway may be responsible for collecting data from multiple NetProbes.
  • NetProbe—A NetProbe is the data collection point for the system. It either performs polling of data from a monitored system, or receives data which is pushed to it by an agent. It is responsible for detecting deltas in data records and pushing new data to the Geneos Gateway. The Active Console GUI allows NetProbes to be created and associated with Gateway objects. This association establishes the communication path between a NetProbe and a Gateway.
    • A NetProbe is typically deployed on each message broker. In this deployment architecture, communication between the NetProbe and Gateway is through the management Ethernet port; therefore, the server on which the Geneos Gateway is installed must have connectivity to the IP management VRF.
    • Alternatively, a NetProbe may be deployed on a server external to the message broker. In this deployment architecture, communication between the NetProbe and Solace Geneos Agent is through the management ethernet port. Therefore, the server that the NetProbe is installed on must have connectivity to the IP management VRF. Each instance of a Geneos NetProbe must have a corresponding NetProbe object created and configured through the Active Console application.
  • Solace Geneos Agent—The Solace Geneos Agent runs on a message broker, and it is responsible for polling data from the message broker, and pushing that data to one or more NetProbes through the open XML-RPC API. The agent retrieves status and statistics information from the message broker by using the Solace Element Management Protocol (SEMP).
  • Managed Entities—Managed entities represent any hardware or software component being monitored. The user is responsible for creating and naming the message broker managed entity on the gateway and associating it with a NetProbe running on that message broker or off the message broker. The monitored message broker is modeled as a Managed Entity in the Active Console application.
  • Sampler—A Sampler Object defines a set of views that a NetProbe gathers from a particular managed entity. By default, Solace provides the SolaceSampler which exposes all of the Solace Views. You can also customize a set of samplers to package the available views as you want.
  • Data Views—A data view object is the holding place for the actual data polled from the managed entity. They are automatically created when the Solace Geneos Agent pushes data up to the NetProbe. Solace Geneos Agent distribution comes with several default data views.