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

Channel Definitions for Flow not working

Votes:

0

Hello,

we try to configure a custom channel definition and are not sure if the defintion does not work or the syntax is wrong:

#34:VIE34
SourceIP[10.2.*.*] and DestinationIP[10.25.25.2] and (DestinationPort[80] or DestinationPort[443])

Thanks in advance, Thomas

channel definitions flow

Created on Feb 20, 2017 4:08:39 PM

Last change on Dec 2, 2021 9:18:16 AM by  Maike Guba [Paessler Support]



Best Answer

Accepted Answer

Votes:

0

Thanks a lot Sebastian for the clarification.

The syntax was indeed fine, but the channel was "overlaying" with another definition with lower channel number so this channel was never receiving data and created.

Created on Feb 21, 2017 5:15:17 PM



4 Replies

Votes:

0

Seems then multiple ANDs are not working. Unfortunately the samples in the documentation are to simple to get the right syntax.

Created on Feb 21, 2017 9:03:08 AM



Votes:

0

Dear koflert,

Thank you for your knowledge base post.

Please see the two relevant manual articles on Channel definitions for Flow, IPFIX, and Packet Sniffer sensors and Filter rules for Flow, IPFIX, and Packet Sniffer sensors.

You can create more complex expressions using parantheses ( ) and the words and, or, and not. The filters can contain multiple and.

The syntax and also the placement of the parentheses look good to me, therefore please confirm that the channel show incorrect monitoring values.

Thank you in advance,
Sebastian

Created on Feb 21, 2017 1:55:33 PM by  Sebastian Kniege [Paessler Support]

Last change on Dec 2, 2021 9:18:30 AM by  Maike Guba [Paessler Support]



Accepted Answer

Votes:

0

Thanks a lot Sebastian for the clarification.

The syntax was indeed fine, but the channel was "overlaying" with another definition with lower channel number so this channel was never receiving data and created.

Created on Feb 21, 2017 5:15:17 PM



Votes:

0

Dear koflert,

Thank you very much for your feedback, I'm glad you found the issue.

Best,
Sebastian

Created on Feb 22, 2017 8:52:03 AM by  Sebastian Kniege [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.