How can we monitor the heartbeat between OneClick and the SpectroSERVERs

Products

• Spectrum
• Network Observability

Issue/Introduction

We have been encountering more frequent issues with the heartbeat being lost between a SpectroServer in one location, and the MLS Parent Landsdcape in another location.

We need a means of monitoring, via script, utility, whatever will work, to Monitor this heartbeat connection.

This loss of heartbeat is seen under the Administration tab, Landscapes, Monitored Landscapes.

The Heartbeat Received will be several hundred thousand seconds.

Environment

Component : Spectrum Core / OneClick Server

Resolution

The heartbeat can be obtained by running the following REST query.  You could then create a script to monitor the output and create an alarm via REST or CLI:

http://OneClickServer:port/spectrum/restful/heartbeat

 

This is the output:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<heartbeat-response xmlns="http://www.ca.com/spectrum/restful/schema/response" total-landscapes="2">
    <heartbeat>Success</heartbeat>
    <landscape>
        <id>16777216</id>
        <name>HOSTNAME</name>
        <isPrimary>true</isPrimary>
        <mls>true</mls>
        <spectroserver>Success</spectroserver>
        <archmgr>Success</archmgr>
    </landscape>
    <landscape>
        <id>33554432</id>
        <name>HOSTNAME</name>
        <isPrimary>true</isPrimary>
        <mls>false</mls>
        <spectroserver>Success</spectroserver>
        <archmgr>Success</archmgr>
    </landscape>
</heartbeat-response>

 

 

Note: 
   isPrimary = false   -and- spectroserver = Success  means that the FT Secondary landscape is active
   isPrimary = false   -and- spectroserver = Failed  means no landscape is available (FT is down also, or if not configured for FT no landscape is available)