Http Status Reporting For Publisher And Replicator; Publisher Response - Dell DX6000 Setup And Configuration Manual

the cause is unknown or a configuration or connectivity issue has been resolved, administrators
may wish to consider Republishing the subscription.
• Last Connection: the amount of time elapsed since the subscriber queried the Publisher for
stream events
• Last Transmit: the amount of time elapsed since the subscriber last retrieved at least one
stream event from the Publisher
• Republish buttons:
• Republish All: this button in the top right of the screen reruns all configured rules for all
subscribers, including any new or updated rules. It will then restart all existing subscribers.
• Subscriber Republish: this button next to each subscriber restarts the subscriber. Since the
Publisher has no way of knowing the Subscriber's status for each event, all stream events that
have been previously sent to the subscriber will be retransmitted as well as any new events.
Administrators may wish to republish a subscription if the Subscriber has failed and needs
a completely fresh list of events or, in the case of a Replicator, if there are a high number of
unexplained dropped events.

5.5. HTTP Status Reporting for Publisher and Replicator

Both the Publisher and the Replicator will provide basic status information in response to a GET
request from any HTTP client as follows:
For Publisher: GET http://<PublisherIP>:PublisherConsolePort/status
For Replicator: GET http://<ReplicatorIP>:ReplicatorConsolePort/status
The response to the request is a standard HTTP response but the response body differs slightly for
each service. All active enumerators will be included in the response in the same order with every
request. Enumerators may be deleted, however, so the index may change.
If either DX Content Router service is installed on a Cluster Services Node (CSN), the response
from the request is used to populate the SNMP MIB for the respective service on the CSN.

5.5.1. Publisher Response

The data in the Publisher response corresponds to the same fields available on the Publisher
console.
[settings]
hostip={publisher ip address or host name}
sourceCluster={source cluster multicast group}
[stats]
version={publisher software version}
upTime={seconds since Publisher started}
eventsFound={number of distinct stream events heard by Publisher}
filterBacklog={number of stream events remaining to be info-ed and filtered}
diskMBAvailable={total disk space available on Publisher data store file system}
diskMBCapacity={total disk space capacity on Publisher data store file system}
cycleTime={seconds elapsed for most recent completed data store merge cycle}
cycleStart={start of current data store merge cycle}
cycleNumber={data store merge cycle count during current Publisher run}
Copyright © 2010 Caringo, Inc.
All rights reserved 21
Version 2.2
December 2010