<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors

When adding Custom xFlow sensors, Custom IPFIX, or Custom Packet Sniffing sensors, you will notice a field entitled Channel Definition. In this field you need to provide the channel definitions in the following syntax (one entry per channel):




  • <id> needs to be 1 or greater and must be unique for the sensor (i.e., 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 using channel IDs 1, 2, 3, etc.
  • 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 doesn't matter) and the data is accounted to the first match.
  • One Other channel is added automatically.
  • Behind the name a optional [<unit>] can be used to override the automatic unit 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. Since data is accounted to the first match, please make sure to start with the most specific rule at the top getting less specific to the bottom.

Note: We recommend writing the rule list in an external editor and paste it into the respective PRTG field. Otherwise, if the rules contain an error, the entries will be removed when adding the rules in case!


General example:

Protocol[TCP] and 
(SourcePort[80] or DestinationPort[80] or SourcePort[8080] or 


Channel definition example for differentiating by protocol:



Related Topics


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



Advanced Topics

Keywords: Flow,Flow Channel Definitions,Packet Sniffer,Packet Sniffer Channel Definitions