<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: DICOM Bandwidth Sensor

Performance impact

• This sensor has a high performance impact. We recommend that you use no more than 200 of this sensor on each probe.

.NET 4.7.2 or later

• This sensor requires .NET 4.7.2 or later from Microsoft on the probe system. In a cluster, install it on every cluster node.

If the framework is missing, you cannot create this sensor.

For more information, see the Knowledge Base: Which .NET version does PRTG require?

IPv6

• This sensor supports IPv6.

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. The default port is 104.

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.

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 to the DICOM enabled device via a C-STORE request to measure bandwidth. 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.

Result Handling

Define what PRTG does with the sensor result:

• Discard result (default): 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.

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, PRTG displays the last value of the primary channel 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 this sensor shows different channels:

• 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 select Stack channels on top of each other above.

Select a unit from the list. PRTG stacks all channels with this unit 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.

C-STORE Bandwidth

The bandwidth usage of the sent files

This channel is the primary channel by default.

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