PRTG Manual: DICOM Bandwidth Sensor
The DICOM Bandwidth sensor monitors the bandwidth usage of a C-STORE request to a Digital Imaging and Communications in Medicine (DICOM) capable device. It sends one or more DICOM images and files that you have stored in a folder on a local disk or share and checks if the DICOM device can handle the C-STORE request.
You can use this sensor to test your picture archiving and communication system (PACS), for example.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: DICOM Bandbreedte
- French: Bande passante (DICOM)
- German: DICOM-Bandbreite
- Japanese: DICOM 帯域幅
- Portuguese: Largura de banda DICOM
- Russian: Пропускная способность DICOM
- Simplified Chinese: DICOM 带宽
- Spanish: Anchura de banda 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 |
---|---|
File Path |
Enter the full path to the folder where you have stored your DICOM files and images (ending with .dcm). This sensor sends all files in the folder to the target DICOM device with each request. You can use any folder on a disk or share that the probe system has access to.
|
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 select Stack channels on top of each other above. 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 |
---|---|
C-STORE Bandwidth |
The bandwidth usage of the sent files
|
C-STORE Response Time |
The response time of the C-STORE request |
C-STORE Size |
The total size of the sent files |
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 |
KNOWLEDGE BASE
Which .NET version does PRTG require?
What security features does PRTG include?