"The page below is from the manual of PRTG, our quick-to-install and easy-to-use network monitoring software"

Try PRTG now and see how it can make your job easier.
 

Free Trial Download
You will be up and running in 2 minutes
Learn More
Screenshots, Features, Videos


Aurelio, System Admin at Paessler AG

When adding Custom xFlow sensors, Custom IPFIX, or Custom Packet Sniffing sensors, you have the option to provide a Channel Definition . In this field enter your channel definitions using the following syntax (one entry per channel):

#<id>:<Name>
<Rule>

 

Syntax

  • <id> needs to be 1 or greater and must be unique for the sensor (so each channel definition must have a unique ID).
    Note: The maximum channel ID you can use is 2147483648 (2^31). Higher IDs are not supported. We recommend that you use channel IDs 1, 2, 3, and so on.
  • The <id> is linked to the historic data: As soon as it has been changed, the history for this particular channel is lost.
  • One rule can span multiple lines.
  • The next rule starts with a # as first character in a line.
  • <name> is the channel's display name.
  • The rules are processed top to bottom (the number does not matter) and the data is accounted to the first match.
  • PRTG adds one channel named Other automatically. This channel counts all traffic for which you have not defined a channel.
  • Behind the name you can use an optional [<unit>] to override the automatic unit which is based on the source sensors.

The <Rule> syntax is identical to the one described in the Filter Rules for xFlow and Packet Sniffer Sensors section. Because data is accounted to the first match, make sure you start with the most specific rule at the top and get less specific to the bottom.

Note : We recommend that you write the rule list in an external editor and paste it into the Channel Definition field of the sensor in PRTG. Otherwise, if the rules contain an error, the entries will be removed when adding the rules in case!

Example

General example:

#5:HTTP
Protocol[TCP] and 
(SourcePort[80] or DestinationPort[80] or SourcePort[8080] or 
DestinationPort[8080])

 

Channel definition example for differentiating by protocol:

#1:TCP
Protocol[TCP]
 
#2:UDP
Protocol[UDP]
 
#3:ICMP
Protocol[ICMP]

 

Related Topics

More

Knowledge Base: Can I add custom channels to standard Packet Sniffer and NetFlow sensors?

Knowledge Base: How can I change the default groups and channels for xFlow and Packet Sniffer sensors?

 

 

Copyright © 1998 - 2015 Paessler AG