...
| Excerpt |
|---|
In addition to the standard direct (TCP based) monitoring capabilities, a Talon XVM can be configured to allow administrative applications to monitor and manage it over messaging. |
...
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 | ||
|---|---|---|
| ||
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:
| Name | Key | QOS | ID | Description |
|---|---|---|---|---|
| Command and Control | ||||
| xvm-request | xvm-admin/${xvmName}/request | BestEffort | 30000 | Command and control requests. |
| xvm-response | xvm-admin/${adminClientId}/response | BestEffort | 30001 | Command and control responses (to issuing admin client) |
| Monitoring | ||||
| xvm-heartbeat | xvm-admin/${xvmName}/heartbeat | BestEffort | 30003 | XVM heartbeats. |
| xvm-trace | xvm-admin/${xvmName}/trace | BestEffort | 30004 | Log trace records. |
| xvm-event | xvm-admin/${xvmName}/event | BestEffort | 30005 | Lifecycle and alert events. |
...
| Tip |
|---|
Enabling xvm heartbeats isn't strictly necessary, but in most monitoring scenarios it is desirable. |
Passive Monitoring
| Anchor | ||||
|---|---|---|---|---|
|
It is possible to use Admin over SMA in a purely passive monitoring capacity by setting the property:
...