Foglight for Sybase 5.7.5.40 - User and Reference Guide

Replication Server Metrics

Replication Server Metrics

There are multiple sections in the Replication Server pane:

•	Each of the Primary Server sections shows Primary Server - Replicated Server Status information for a primary server.

•	The bottom section shows Partitions information.

The pane title line indicates the overall status of the replication server, which is either:

•	HEALTHY—all threads are executing as expected.

•

SUSPECT—a thread is down and the Replication Server expected it to be running. Or, a thread is in a Connecting state. The Connecting state means that either the server to which Replicated Server is connecting is unavailable and a problem exists, or the Replicated Server connects successfully in a moment and the suspect status is transitory.

Primary Server - Replicated Server Status

The top sections show sets of related primary and replicated server information:

•	Primary Server Information

•	Replicated Servers Table

Click the Pop Up Screen button to see the full list of replicated server databases.

Primary Server Information

 

Table 62. Primary Server Information

Name	Description
Primary Server	The primary server is shown as combination of the server name and the database name. Accordingly, the Data and Log sizes are indicated for the appropriate database inside the appropriate Sybase server. You can drill down by clicking on this field. A popup appears showing the Data Size and the Log Size. The amount of data memory and log memory (in megabytes) is shown for the primary server: • Available memory • Total memory You can drill down further by clicking on the Data Size or Log Size device image: • The Data Space Used is shown plotted over time. • The Log Space Used is shown plotted over time. The Data Size and Log Size fields displays color-coded real-time behavior for severity.
Sybase_MDA agent status	The status of the Sybase_MDA agent: • Available—the Sybase_MDA Agent and the Replication Server are running on the same Foglight Management Server. This also indicates that the Sybase_MDA Agent is in the Collecting Data state. • No Agent—no Sybase_MDA Agent is running. You can drill down by clicking on this status field. The MDA Home Page Dashboard appears for the appropriate server.
Threads Status	The number of threads that are either: • Down—the thread has not started or has terminated. • Suspended—the thread has been suspended by the user. These fields display color-coded real-time behavior for severity. You can drill down by clicking on any Thread Status. A table appears showing the thread status details.
Inbound Q Size	The amount of memory being used for the inbound queue, in megabytes. These fields display color-coded real-time behavior for severity. You can drill down by clicking on the text or number. A popup appears showing the Inbound queue history, plotted over time.

Replicated Servers Table

 

Table 63. Replicated Servers Table Description

Name	Description
Replicated Server DB	The replicated server database name. You can drill down to view the Data Size and Log Size. You can drill down further to view a chart of the Data Space Used or Log Space Used plotted over time.
Agent Status	The status of the Sybase_MDA agent: • Available—the Sybase_MDA Agent and the Replication Server are running on the same Foglight Management Server. This also indicates that the Sybase_MDA Agent is in the Collecting Data state. • No Agent—no Sybase_MDA Agent is running. You can drill down by clicking on this status field. The MDA Home Page Dashboard appears for the appropriate server.
Latency (sec)	The difference between the time the transaction was committed at the destination (Replicate) database, and the Time at the origin (Primary Site) when the transaction was committed, in seconds. You can drill down to view the Latency plotted over time.
SQM	The SQM (Stable Queue Manager) status. You can drill down by clicking on this field. A popup appears showing the Blocks Written Into the Queue per second, plotted over time.
Q. Size (MB)	The amount of data remaining in the queue for processing, in megabytes. You can drill down to view the Queue Size plotted over time.
DSI	The DSI (Data Server Interface) thread status. You can drill down by clicking on this field. A popup appears showing the Blocks Read from the Queue per second, plotted over time.

Partitions

 

Table 64. Partitions

Name	Description
Partitions	The total number of partitions. This field displays color-coded real-time behavior for severity. You can drill down by clicking on the device symbol. A popup appears showing the used space summary, plotted over time.
Three top partition names	The amount of data memory (in megabytes) in the partition: • Available • Total This field displays color-coded real-time behavior for severity.

Replication Server Activity Dashboard

Replication Server Activity Dashboard

The Replication Server dashboard contains several views that show the performance metrics of the CPU of the machine hosting the Replication Server.

To display this dashboard, on the Sybase MDA Global View Dashboard, drill down on a Sybase_RS agent, and on the RS Home Page Dashboard that appears, click Rep Server Activity.

The dashboard contains the following sections:

•	Primary Servers Metrics

•	Replication Server Metrics

•	Replicated Servers Metrics

Drilldown dashboards may be accessed through some of the dashboard element metrics.

Figure 38. Replication Server Activity Dashboard

Primary Servers Metrics

Primary Servers Metrics

 

Table 65. Primary Servers Metrics

Name	Description
Primary Server box	Lists all primary servers related to the replicated server. The primary server is shown as combination of the server name and the database name. Click the box to select a Primary Server and show its metrics in the Replication Server dashboard.
Primary Server view	Shows the database name and the status of the Sybase_MDA Agent. The status of the Sybase_MDA agent: • Available—the Sybase_MDA Agent and the Replication Server are running on the same Foglight Management Server. This also indicates that the Sybase_MDA Agent is in the Collecting Data state. • No Agent—no Sybase_MDA Agent is running. You can drill down by clicking on this status field. The MDA Home Page Dashboard appears for the appropriate server.
Rep. Agent	The RepAgent status. The Sybase RepAgent is used to send the changes from the primary database to the Replication Server.

Replication Server Metrics

Replication Server Metrics

This pane shows the data flow between a primary server and replicated servers through a replication server. The primary component of a replication server is the Distributor, which processes changes from the primary server and sends it on to replicated servers. The Distributor uses inbound and outbound queues to receive and send data and the related components, including the Stable Queue Transaction (SQT), SQM (Stable Queue Manager), and Data Server Interface (DSI). The following table lists the components that appear on the Replication Server Metrics section in the order of the data flow, appearing on the Replication Server pane.

The pane title line indicates the overall status of the replication server, which is either:

•	HEALTHY—all threads are executing as expected.

•

SUSPECT—a thread is down and the Replication Server expected it to be running. Or, a thread is in a Connecting state. The Connecting state means that either the server to which Replicated Server is connecting is unavailable and a problem exists, or the Replicated Server connects successfully in a moment and the suspect status is transitory.

 

Table 66. Replication Table Metrics

Name	Description
SQM	The status of the SQM used to receive information from the Primary Server, color-coded. You can drill down by clicking on this field, to show the SQM status.
Block writes (c/s)	The rate at which blocks are written to the inbound queue, given as count per second. You can drill down by clicking this component. A popup appears, showing the inbound queue history, plotted over time.
In. Queue Size (MB)	The current size of the inbound queue.
Block reads (c/s)	The rate at which data blocks are read from the inbound queue to the SQM associated with the Distributor, given as count per second.
SQT	The status of the SQM associated with the Distributor that receives information from the inbound queue, color-coded. You can drill down by clicking on this field, to show the SQM status.
Distributor	The status of the Distributor component.
SQM	The status of the SQM associated with the Distributor that writes information to the outbound queue, color-coded. You can drill down by clicking on this field, to show the SQM status.
Block writes (c/s)	The rate at which blocks are written to the outbound queue. You can drill down by clicking this component. A popup appears, showing the inbound queue history, plotted over time.
Out. Queue Size	The current size of the outbound queue.
Block reads (c/s)	The rate at which data blocks are read from the outbound queue to the DSI thread that sends the information to the related replicated server.
DSI	The status of the DSI thread that is associated with a replicated server.