Monitoring Page

A server continuously logs activity. These logs are stored for seven days. During that time, you can retrieve the results and display them graphically in a web browser or export them to a comma-separated file for importing into a spreadsheet, database or other application.

The following list of system activities can be retrieved from the system logs.

System activity Description
DICOM objects acquired

Number of DICOM objects the system acquired. The red entries indicate new objects. Green entries indicate resends.

DICOM objects forwarded

Number of DICOM objects the system forwarded. This includes forwards to other EP servers in the dotcom. The red entries indicate objects forwarded to non-archive devices. Green entries indicates forwards to registered archives.

Objects processed

Number of objects processed by the task manager. Red entries indicate acquired objects. Green entries indicate objects retrieved from a registered archive. Blue entries indicate re-indexed objects.

Processing latency

Time in seconds between an object’s acquisition and it being processed. The longest processing latency for any object for a given second is reported.

Objects in queue

Number of tasks in the queues.

Images served

Average number of MBtyes per minute the server has processed. Red entries indicate raw data. Green entries indicate compressed data.

Images max throughput

Maximum number of image Mbits per second sampled for each minute.

Images streamed total (MBytes/s)

Total throughput in the given minute via streaming (total number of bytes served  / 60 sec)

Images streamed user max (MBytes/s)

Highest throughput packet during the given minute (packet size / transfer time)

Images streaming active clients

Number of clients performing any activity in the given minute

Images streaming requests (ops)

Number of streaming packet operations in the given minute

Processor load

The load on the processor taken at one-minute, five-minute and fifteen-minute intervals.

# sleeping processes

Number of sleeping processes

# running processes

Number of running processes

# zombie processes

Number of zombie (defunct) processes

CPU usage

Percentage of the CPU being used.

IO wait

Percentage of time spent reading and writing data to the file system.

CPU idle

Percentage of time the CPU is reported idle.

Memory usage

Memory usage including RAM used for disk cache.

Memory usage actual

Memory usage minus the disk cache, showing actual memory used by the application(s).

Data partition usage

Percent of the data partition in use.

TMP partition usage

Percent of medsrv’s TMP partition used.

Cache repo activity

Total number of resource (study) operations (delete or move) in the measured minute

Data/processed/other repo moves

Total number of move operations in the given repos (data, processed) in the measured minute.
Other is currently unused in v8, in v9 it is measured for any other, user, meta or localcache combined

Data/processed/other repo deletes

Total number of delete operations in the given repos (data, processed) in the measured minute
Note that data and processed have no deletes.
Other is currently unused in v8, in v9 it is measured for any other: user, meta or localcache (the last one does have deletes)

Time of SQL query

Response time reported by a defined MySQL query performed each minute.

Time of WL page download

Response time reported by a defined worklist query including formatting, apache, etc.

Task queue

Number of tasks in queue. Red entries indicate items in retry.  Green entries indicate items in failed.

Task queue failed

(Obsolete) Number of tasks in failed queue.

Task queue critical lag

Time the oldest task with a mission-critical priority (less than 200) has been in the queue

Task queue total lag

Time the oldest task has been in the queue.

DICOM associations

Percentage of the configured DICOM associations allocated.

Apache threads

Percentage of the configured apache threads allocated.

Tomcat threads

Percentage of the configured tomcat threads allocated.

MySQL threads

Percentage of the configured MySQL threads allocated.

 

To collect the data for a specific activity:

1. Check the box for the system activity you wish to view.

2. Set the date. You can collect data for one day at a time.

3. Click Get Statistics button

The data is displayed as a graph across the 24-hour period. The maximum scale value appears on the graph’s vertical axis.  Clicking on the graph image opens a popup window where the graph image with original size can be examined.

To export the data for any specific activity, click the Export button at the top of the graph. The data is downloaded as a comma-separated file.