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 the sensor to test your picture archiving and communication system (PACS), for example.
DICOM Bandwidth Sensor
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
Sensor in Other Languages
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
Remarks
This sensor has a high performance impact. Use it with care. We recommend that you use no more than 200 sensors of this sensor type on each probe.
This sensor requires .NET 4.7.2 or later from Microsoft on the probe system.
This sensor supports the IPv6 protocol.
Detailed Requirements
Requirement
Description
.NET 4.7.2 or later
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).
If the framework is missing, you cannot create this sensor.
The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the settings that are required to create the sensor. You can change nearly all settings on the sensor's Settings tab after creation.
Basic Sensor Settings
Click the Settings tab of a sensor to change its settings.
If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include?
This setting is for your information only. You cannot change it.
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.
It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).
For performance reasons, it can take some minutes until you can filter for new tags that you added.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
dicom
bandwidth
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 () to the highest priority ().
Usually, a sensor connects to the IP Address/DNS Name of the parent device. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings.
DICOM Connection
DICOM Connection
Setting
Description
Calling Application Entity Title
Enter the Application Entity Title (AET) of PRTG to initialize a DICOM connection.
The AET is case sensitive and does not support special characters.
Called Application Entity Title
Enter the AET of the target system to initialize a DICOM connection.
The AET is case sensitive and does not support special characters.
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).
If the reply takes longer than this value, the sensor cancels the request and shows a corresponding error message.
Bandwidth Settings
Bandwidth Settings
Setting
Description
File Path
Enter the full path to the folder where you have stored your DICOM files and images (ending with .dcm). The 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.
For example, enter C:\DICOM to send files that are stored in a folder named DICOM on the probe system.
The path must contain *.dcm files. Enter the path without a backslash (\) at the end.
Debug Options
Debug Options
Setting
Description
Result Handling
Define what PRTG does with the sensor result:
Discard result: Do not store the sensor result.
Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file names are Result of Sensor [ID].txt, Result of Sensor [ID].Data.txt, and Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites these files with each scanning interval.
This option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.
In a cluster, PRTG stores the result in the PRTG data directory of the master node.
Sensor Display
Sensor Display
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.
You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab.
Graph Type
Define how different channels are shown for this sensor:
Show channels independently (default): Show a graph for each channel.
Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic. You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).
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.
Inherited Settings
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 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.
Schedules, Dependencies, and Maintenance Window
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
Access Rights
Access Rights
For more information, see section Root Group Settings, section Access Rights.
Channel List
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 in bytes per second
This channel is the primary channel by default.
C-STORE Response Time
The response time of the C-STORE request in milliseconds (msec)
C-STORE Size
The total size of the sent files in bytes
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