What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

Add/Remove Channels Linux Disk Free Sensor



I have a sensor which have channels which no longer exist on the Linux system ( cciss/c0d0p2, loop0 ) How can I remove these channels ?

I added a new sensor for this system but it only channels for sda2 and sb1, but NO entries for sda3 and sdc1. How can I add these channels ?


  • PRTG V14.2.10.2114
  • Ubuntu 12.04.4 LTS
  root@server5:/data# df -k
  Dateisystem     1K-Blöcke   Benutzt  Verfügbar Verw% Eingehängt auf
  /dev/sda2        82567856   7773092   70600564   10% /
  udev             16456872         4   16456868    1% /dev
  tmpfs             3293788      6020    3287768    1% /run
  none                 5120         0       5120    0% /run/lock
  none             16468920       328   16468592    1% /run/shm
  /dev/sda3       203700064  35932260  157420440   19% /home
  /dev/sdb1       288338280 227831612   45859936   84% /data
  /dev/sdc1      1953512000 149149128 1804362872    8% /media/Expansion Drive

disk-free linux snmp

Created on Jul 9, 2014 9:12:53 AM

5 Replies



In order to remove a single channel from a sensor (which is basically making it invisible), simply click the small cogwheel on the right corner of the channel. Now select "Hide from Charts" and "Hide from Tables".

The sensor usually walks your fstab file for entries. Are they mounted there? Or manually?

Created on Jul 10, 2014 12:43:09 PM by  Stephan Linke [Paessler Support]



/dev/sda3 is mounted on /home during boot from fstab, but is NOT shown in PRTG /dev/sdc3 is an external USB disk and was automounted through the system but NOT shown in PRTG.

root@server5:/etc# more fstab
# /etc/fstab: static file system information.
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/cciss/c0d0p2 during installation
UUID=957c23e2-4c1b-4c9a-ad57-afc75a4cfab4 /               ext4    errors=remount-ro 0       1
# /data was on /dev/cciss/c0d1p1 during installation
UUID=84f5c6e1-1c40-4841-9ac1-43c0657a6e6a /data           ext4    defaults        0       2
# /home was on /dev/cciss/c0d0p3 during installation
UUID=759f09a4-fae7-4429-9331-f269ec7fe077 /home           ext4    defaults        0       2
# swap was on /dev/cciss/c0d0p1 during installation
UUID=4bf45604-b1c0-4ac0-8c26-342c485475f7 none            swap    sw              0       0

>>> The sensor usually walks your fstab file for entries.

I thought an SNMP sensor will walk the SNMP MIB ? Because a SNMP-Walk will show up these informations:

Oid : (enterprises.2021. )
Value: sda
Oid : (enterprises.2021. )
Value: sda1
Oid : (enterprises.2021. )
Value: sda2
Oid : (enterprises.2021. )
Value: sda3
Oid : (enterprises.2021. )
Value: sdb
Oid : (enterprises.2021. )
Value: sdb1
Oid : (enterprises.2021. )
Value: sdc
Oid : (enterprises.2021. )
Value: sdc1

Created on Jul 10, 2014 6:23:34 PM



Sorry for the late reply. I didn't see the SNMP tag in the first post; In order to monitor those properly, add the following lines to your /etc/snmp/snmpd.conf file:

sda3 / 10%
sdc1 / 10%

and then restart snmpd: sudo /etc/init.d/snmpd restart PRTG should then list them when you add a new disk sensor :)

Created on Jul 28, 2014 2:25:23 PM by  Stephan Linke [Paessler Support]



I would like to be able to remove channels from the linux disk-free-sensor. We are monitoring a number of Docker hosts, and I need to monitor disk space only on the host. When PRTG runs auto-discovery, it catches a volume for every single Docker container, and then when containers are shut down, it sends errors for those. How can I work around this? I have a sensor with hundreds of channels which I don't want to monitor and which also really slows down the UI.

Created on Feb 5, 2019 9:08:48 PM



Channels are usually not to be removed, but you might want to check this alternative sensor. It allows you to monitor the given hosts volumes, but you can also configure an include list of volumes you'd like to see within the sensor. Others are not considered.

PRTG Scheduler | PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Created on Feb 6, 2019 7:32:20 AM by  Stephan Linke [Paessler Support]

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.