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

Changing same channel on multiple sensors not working (Multi-Edit)

Votes:

0

If I edit several "SNMP Traffic" type sensors on the same channel at the same time, only the first sensor adopts these settings. So I have to adjust the channel individually for each sensor.

For me it's explicitly about the "Data" setting in the "Traffic Total" channel. I have to set this manually to "Display in percent of maximum" - that takes a long time if I have to do this for every sensor.

channel multi-edit prtg snmp traffic

Created on Mar 31, 2022 7:51:40 AM



1 Reply

Votes:

0

Hello,

Thank you for your message.

We indeed noticed this issue and forwarded it to our development team for investigation. Unfortunately, there is no further information about it yet.

In the meantime, you could use the PowerShell module PRTGAPI (from third party) to automate that task by using the code below (might need to be adapted to your needs): ​

param(
    [string] $hostname = "", # PRTG DNS or IP
    [string] $username = "", # User account
    [string] $passhash = ""  # User passhash
)

try {
    if(!(Get-PrtgClient)){
        Connect-PrtgServer $hostname (New-Credential $username $passhash) -PassHash -IgnoreSSL 
    }

$sensors = Get-Sensor -Tag "SensorTAG" # You might need to change/improve this line to only get the sensors you want to modify.
foreach($sens in $sensors){
    $sens | Get-Channel -Id "-1" | Set-ChannelProperty -PercentMode 1 -PercentValue ​MAXIMUMVALUE
}

Please, note that the requests executed by the module can consume memory on the Core server which won't be released as the session established is not closed properly (due to the endpoint used by this module). Therefore, its usage should stay limited until the developer behind it implements the solution we provided to him.

Regards.

Created on Apr 1, 2022 9:01:41 AM by  Florian Lesage [Paessler Support]

Last change on Apr 1, 2022 9:03:07 AM by  Florian Lesage [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.