PRTG Manual: DICOM Query/Retrieve Sensor
The DICOM Query/Retrieve sensor monitors the C-FIND capability of Digital Imaging and Communications in Medicine (DICOM) capable systems and devices. It sends a C-FIND request or Modality Worklist (MWL) query to the target device and counts all found items.
You can specify search levels to only count specific items.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: DICOM Query/Retrieve
- French: Recherche / récupération (DICOM)
- German: DICOM-Abfrage
- Japanese: DICOM クエリ/取得
- Portuguese: Consulta/recuperação DICOM
- Russian: Запрос/получение DICOM
- Simplified Chinese: DICOM 查询/检索
- Spanish: Consulta/Recuperación DICOM
- This sensor has a high performance impact. We recommend that you use no more than 200 of this sensor on each probe.
- This sensor requires .NET 4.7.2 or later from Microsoft on the probe system.
- This sensor supports IPv6.
Requirement |
Description |
---|---|
This sensor requires .NET 4.7.2 or later to be installed on the probe system (on every cluster node, if on a cluster probe).
|
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.
|
Parent Tags |
The tags that the sensor inherits from its parent device, parent group, and parent probe.
|
Tags |
Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
Priority |
Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority ( |
Setting |
Description |
---|---|
Calling Application Entity Title |
Enter the Application Entity Title (AET) of PRTG to initialize a DICOM connection.
|
Called Application Entity Title |
Enter the AET of the target system to initialize a DICOM connection.
|
Port |
Enter the port of the DICOM interface to use for the connection. |
Timeout (Sec.) |
Enter a timeout in seconds for the request. Enter an integer. The maximum timeout value is 900 seconds (15 minutes).
|
Setting |
Description |
---|---|
C-FIND Level |
Define the search level of the C-FIND request:
|
Search Key |
This setting is only visible if you select Patient, Study, or Series above. Enter a key that you want to search for, for example, an instance Unique Identifier (UID), series UID, patient UID, or enter an asterisk (*) to search for all items. Enter a string. |
Modality |
This setting is only visible if select Study or Series above. Enter a modality in short form that you want to search for, for example, CT, MRI, US, or enter an asterisk (*) to search for all modalities. Enter a string. |
Filter Field |
This setting is only visible if you select Worklist above. Define a field of the worklist that you want to filter for:
|
Filter String |
This setting is only visible if you select Worklist above. Enter a string that you want to filter for, for example, a station name, station AET, modality, or an asterisk (*) to filter for all items. Enter a string. |
Channel Field |
This setting is only visible if you select Worklist above. Define which field you want to use to name the channels:
|
Setting |
Description |
---|---|
Result Handling |
Define what PRTG does with the sensor result:
|
Setting |
Description |
---|---|
Primary Channel |
Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.
|
Graph Type |
Define how different channels are shown for this sensor:
|
Stack Unit |
This setting is only visible if you enable Stack channels on top of each other as Graph Type. Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so. |
By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
For more information, see section Root Group Settings, section Access Rights.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Avg. Query Entry Time |
The average query entry time |
Downtime |
In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status |
Max Query Entry Time |
The maximum query entry time |
Min Query Entry Time |
The minimum query entry time |
Total |
The total number of items found
|
Total Time |
The total time of the C-FIND request or MWL query |
The sensor also adds channels for the number of items in each field it finds.
KNOWLEDGE BASE
Which .NET version does PRTG require?
What security features does PRTG include?