The Talon Manual

Versions Compared

Old Version 19

changes.mady.by.user Unknown User (colin)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (colin)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Excerpt

In addition to the standard direct (tcp TCP based) monitoring capabilities, a Talon XVM can be configured to allow administrative applications to monitor and manage of it over messaging.

 When  When Admin over SMA is enabled, XVMs emit heartbeat, trace and lifecycle events over defined messaging channels for consumption by listening clients. Tools such as Robin and Lumino user use discovery to listen for available XVMs. Once an Admin Client discovers an XVM it connects to the configured message bus and subscribes to its monitoring channels. At a high level, all that is required to enable Admin over SMA is to set the following properties

...

As long as both the admin client and the XVM are using the same discovery descriptor and message bus, they will be able to communicate with one another. 

Note
titleWarning

When enabling Admin over SMA it is important to note that by default admin clients using SMA will attempt to connect to discovered XVMs. If older version XVMs or XVMs not configured for Admin over SMA are advertising themselves over the admin client's discovery address the XVM will never respond and the admin client will see connection timeouts. To avoid this you may:

 

Admin Channels

The table below lists the bus channels used for administration over SMA:
 

NameKeyQOSIDDescription
Command and Control
xvm-requestxvm-admin/${xvmName}/requestBestEffort30000Command and control requests.
xvm-responsexvm-admin/${adminClientId}/responseBestEffort30001Command and control responses (to issuing admin client)
Monitoring
xvm-heartbeatxvm-admin/${xvmName}/heartbeatBestEffort3000330002XVM heartbeats.
xvm-tracexvm-admin/${xvmName}/traceBestEffort3000430003Log trace records.
xvm-eventxvm-admin/${xvmName}/eventBestEffort3000530004Lifecycle and alert events.

...

Admin clients should not attempt to issue commands until an XVM has been discovered via the discovery provider (see Understanding Discovery). When an admin client detects that a an XVM is no longer discoverable it should stop issuing commands over SMA. 

...

The following bus definition can than then be configured for use with the by the XVM. 

Code Block
xml
xml
<buses>
  <bus name="xvm-admin">
	<provider>solace</provider>
    <address>solhost</address>
    <port>55555</port>
  </bus>
</buses>

...

Tip

Enabling xvm heartbeats isn't strictly necessary, but in most monitoring scenarios it is desirable.

Passive Monitoring

Anchor
PASSIVE_MONITORING
PASSIVE_MONITORING

It is possible to use Admin over SMA in a purely passive monitoring capacity by setting the property:

Code Block
nv.server.admin.passivemonitoringonly=falsetrue

With the above configuration setting clients will throw an exception if an attempt is made to send commands to an XVM, and XVMs will not issue subscriptions on the xvm-request channel.

...