6.3 Monitoring Connection Information

Interstage Shunsaku Data Manager Operator's Guide - Microsoft(R) Windows(R) 2000/ Microsoft(R) Windows Server(TM) 2003 - - UNIX -

Contents Index

Chapter 6 Monitoring and Logging

6.3 Monitoring Connection Information

This section explains how to monitor connection information.

Connection information can be used for the following purposes:

Checking the status of connections between applications and Shunsaku
Collecting information about connections where the time taken to respond to an application exceeds a certain interval
Analyzing which applications requests are taking a long time to process

Connection status information can be obtained by executing the shuncstate command with the -c option or the -t option on the server where the conductor is located.

Example 1

The following example shows how connection information is displayed.

shuncstate -s shunc -c
Shunsaku shuncstate 2006/01/01 19:01:00

(1)             (2)
Client          Application
                (3)                  (4)
                RequestType          ShunsakuFile
                (5)                  (6)                  (7)
                QueryStarted         QueryElapse(sec)     Results
                (8)                  (9)
                Stage                StageElapse(sec)
                (10)                 (11)                 (12)
                DirectorStarted      DirectorEnded        BusiestDirector
                (13)                 (14)                 (15)
                SorterStarted        SorterEnded          Sorter
                (16)
                Expression

192.168.0.1     Application2
                SEARCH               file1
                19:02:53.340         6.660
                DIRECTOR             4.060
                19:02:53.950

                SEARCH: /root/company/employee/name == 'smith'
                RETURN: /root/company/name/text()

192.168.0.2     Application1
                DELETE               file1
                19:02:54.140         3.870
                DIRECTOR             3.020
                19:02:58.740
                
                

192.168.0.1     Application.PKG01
                SORT                 file1
                19:02:49.780         9.120                25
                SORTER               1.130                
                19:02:50.330         19:02:56.740         shund1
                19:02:57.080                              shuno1
                SEARCH: /root/company/id = 2000
                SORT: rlen(/root/company/name/text(),16)
                RETURN: /root/company/name/text()

The following table shows the explanation of the item displayed.

Displayed Item

Explanation

(1) Client

The IP address of the host where the application is running

(2) Application

The name of an application
The package name will be displayed as the name of an application for Java API. The program name will be displayed as the name of application for .NET API and C API.

(3) RequestType

Type of request from the connected application
One of the following is displayed for the type of request from the connected application:

CONNECT: Connection request
SEARCH: Search request
SORT: Sort request
INSERT: Insertion request
UPDATE: Update request
DELETE: Deletion request
COMMIT: Commit request
ROLLBACK: Rollback request
SEARCHKEY: Direct search request
UPDATEKEY: Direct update request
DELETEKEY: Direct delete request

(4) ShunsakuFile

Shunsaku File name of the connection destination (displayed only when Shunsaku Files are used.)

(5) QueryStarted

The time when the query was issued (HH:MM:SS.mmm)

(6) QueryElapse(sec)

The time elapsed since the query was issued (seconds)

(7) Results

Number of search results (displayed only if the RequestType is SEARCH or SORT.)

(8) Stage

Processing stage for the request (if the t option is specified, 'IDLE' or 'ERROR' will always be output.)

CONDUCTOR: Conductor processing in progress
DIRECTOR: Request being passed to director
SORTER: Request being passed to sorter
IDLE: Waiting for a request
ERROR: Error

(9) StageElapse(sec)

The time (in seconds) that has elapsed since moving to the current processing stage (not displayed if the stage is "ERROR".)

(10) DirectorStarted

Time when the director started processing (HH:MM:SS.mmm)

(11) DirectorEnded

Time when the director finished processing (HH:MM:SS.mmm)

(12) BusiestDirector

Identifier for the director with the longest processing time

(13) SorterStarted

Time when the sorter started processing (HH:MM:SS.mmm)

(14) SorterEnded

Time when the sorter finished processing (HH:MM:SS.mmm)

(15) Sorter

Sorter identifier used by a search request with a sort specification

(16) Expression

Search request expression (direct access key, search expression, return expression, sort expression)
If the type of request is "SEARCH", the search expression and return expression will be displayed.
If the type of request is "SORT", the search expression, return expression and sort expression will be displayed.
If the type of request is "SEARCHKEY", the direct access key and the return expression will be displayed.
If the request expression is "UPDATEKEY" or "DELETEKEY", the direct access key will be displayed.
If the type of request is not the types above, nothing will be displayed.
If NULL is specified for the return expression (obtain record ID), "RECORD ID" is displayed.
The display format is as follows:

Direct access key SEARCHKEY: Direct access key name = "the value of direct access key"
Search expression SEARCH: Search expression
Sort expression SORT: Sort expression
Return expression RETURN: Return expression

Displayed Item	Explanation
(1) Client	The IP address of the host where the application is running
(2) Application	The name of an application The package name will be displayed as the name of an application for Java API. The program name will be displayed as the name of application for .NET API and C API.
(3) RequestType	Type of request from the connected application One of the following is displayed for the type of request from the connected application: CONNECT: Connection request SEARCH: Search request SORT: Sort request INSERT: Insertion request UPDATE: Update request DELETE: Deletion request COMMIT: Commit request ROLLBACK: Rollback request SEARCHKEY: Direct search request UPDATEKEY: Direct update request DELETEKEY: Direct delete request
(4) ShunsakuFile	Shunsaku File name of the connection destination (displayed only when Shunsaku Files are used.)
(5) QueryStarted	The time when the query was issued (HH:MM:SS.mmm)
(6) QueryElapse(sec)	The time elapsed since the query was issued (seconds)
(7) Results	Number of search results (displayed only if the RequestType is SEARCH or SORT.)
(8) Stage	Processing stage for the request (if the t option is specified, 'IDLE' or 'ERROR' will always be output.) CONDUCTOR: Conductor processing in progress DIRECTOR: Request being passed to director SORTER: Request being passed to sorter IDLE: Waiting for a request ERROR: Error
(9) StageElapse(sec)	The time (in seconds) that has elapsed since moving to the current processing stage (not displayed if the stage is "ERROR".)
(10) DirectorStarted	Time when the director started processing (HH:MM:SS.mmm)
(11) DirectorEnded	Time when the director finished processing (HH:MM:SS.mmm)
(12) BusiestDirector	Identifier for the director with the longest processing time
(13) SorterStarted	Time when the sorter started processing (HH:MM:SS.mmm)
(14) SorterEnded	Time when the sorter finished processing (HH:MM:SS.mmm)
(15) Sorter	Sorter identifier used by a search request with a sort specification
(16) Expression	Search request expression (direct access key, search expression, return expression, sort expression) If the type of request is "SEARCH", the search expression and return expression will be displayed. If the type of request is "SORT", the search expression, return expression and sort expression will be displayed. If the type of request is "SEARCHKEY", the direct access key and the return expression will be displayed. If the request expression is "UPDATEKEY" or "DELETEKEY", the direct access key will be displayed. If the type of request is not the types above, nothing will be displayed. If NULL is specified for the return expression (obtain record ID), "RECORD ID" is displayed. The display format is as follows: Direct access key SEARCHKEY: Direct access key name = "the value of direct access key" Search expression SEARCH: Search expression Sort expression SORT: Sort expression Return expression RETURN: Return expression

If the value of the direct access key is more than 64 KB, all the details may not be displayed by the "SEARCHKEY".

Example 2

In the following example, information for connections relating to queries where requests were received within a certain period and where the response time to the application exceeds three seconds is output to a text file.

shuncstate -s shunc -t start -q 3 -o C:\shunwork\monitor\conection.txt
shuncstate -s shunc -t end

shuncstate -s shunc -t start -q 3 -o /home/shunsaku/monitor/connection.txt
shuncstate -s shunc -t end

Specifying "-t start" starts the collection of connection information, while specifying "-t end" ends information collection.

Content of connection.txt

Client          Application
                RequestType          ShunsakuFile
                QueryStarted         QueryElapse(sec)     Results
                Stage                StageElapse(sec)
                DirectorStarted      DirectorEnded        BusiestDirector
                SorterStarted        SorterEnded          Sorter
                Expression

192.168.0.1     application2
                SORT                 file1
                19:19:46.053         3.160                201
                IDLE                 0.000                
                19:19:46.091         19:19:47.133         shund1
                19:19:47.134         19:19:49.211         shuno1
                SEARCH: /document/base/prefecture == 'Melbourne' 
                SORT: val(/document/base/price/text()), /document/base/in/text()
                RETURN: /document/base/name, /document/base/price, /document/base/in 

192.168.0.2     application1
                SORT                 file1
                19:19:46.250         3.162                283
                IDLE                 0.000          
                19:19:46.252         19:19:47.333         shund1
                19:19:47.334         19:19:49.411         shuno1
                SEARCH: /document/base/prefecture == 'Sydney' 
                SORT: val(/document/base/price/text()), 
/document/base/in/text()
                RETURN: /document/base/name, /document/base/price, /document/base/in

Example 3

In the following example, information for connections relating to queries where requests were received within a certain time period is output in CSV format.

shuncstate -s shunc -t start -C -o C:\shunwork\monitor\conection.csv
shuncstate -s shunc -t end

shuncstate -s shunc -t start -C -o /home/shunsaku/monitor/connection.csv
shuncstate -s shunc -t end

Specifying "-t start" starts the collection of connection information, while specifying "-t end" ends information collection.

Content of connection.csv

"Client","Application","RequestType","ShunsakuFile","QueryStarted","QueryElapse(sec)","Results","Stage","StageElapse(sec)","DirectorStarted","DirectorEnded","BusiestDirector","SorterStarted","SorterEnded","Sorter","Expression"
"192.168.0.1","application2","SORT","file1","19:19:46.053",3.160,201,"IDLE",0.000,"19:19:46.091","19:19:47.133","shund1","19:19:47.134","19:19:49.211","shuno1","SEARCH: /document/base/prefecture == 'Melbourne' SORT: val(/document/base/price/text()), /document/base/in/text() RETURN: /document/base/name, /document/base/price, /document/base/in"
"192.168.0.2","application1","SORT","file1","19:19:46.250",3.162,283,"IDLE",0.000,"19:19:46.252","19:19:47.333","shund1","19:19:47.334","19:19:49.411","shuno1","SEARCH: /document/base/prefecture == 'Sydney' SORT: val(/document/base/price/text()), /document/base/in/text() RETURN: /document/base/name, /document/base/price, /document/base/in"

Column headings are output in the first line, and connection information is output from the second line.
Each record ends with a linefeed code.

CSV files are output using the following format:

Enclose character string items in double quotes ("). If there any double quotes in the character string, the character string will be enclosed with another double quotes.
Do not enclose numerical values in double quotes (").

Contents Index