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

Remove the other filter on the Netflow9 Sensor

Votes:

1

I would like to know if it would be possible to list the top 10 connections, but excluding others from the graph and table. When the other data is too high, the graph is not legal for visualization.

exemple. https://hlassets.paessler.com/common/files/screenshots/monitoring-cisco-devices/03_02_netflow_v9_custom_top_connections_kl.jpg

netflow netflow-v9 prtg sensor

Created on Oct 6, 2020 1:44:56 PM



5 Replies

Votes:

0

Hello,

There is not a way to accomplish this. However, you can modify some files in PRTG to get the sensor to classify traffic that is otherwise classified as Other.

PRTG Custom Flow Rules

Modifying the custom flow rules will allow you to give PRTG the extra ports and protocols that are specific to your network for classification. This should help reduce the overall percentage of the Other channel.

Let me know if I can answer any other questions.

Benjamin Day
[Paessler Support]

Created on Oct 7, 2020 3:18:45 AM by  Benjamin Day [Paessler Support] (1,441) 2 1

Last change on Dec 2, 2021 9:07:37 AM by  Maike Guba [Paessler Support] (2,404) 2 1



Votes:

0

Hello Bejamin,

We needed to filter the top 10 connections with the highest bytes of IPV4 traffic; when filtering by protocols, we did not find the expected result. inside the "main communication or main connections" exist a chart with line called "others". We would like to appear just the lines to 10 connections with highest bytes. Could you help us?

regards,

Created on Oct 7, 2020 3:39:22 PM



Votes:

1

Hello fabriciorfp,

We do not have the ability to do any filtering on those toplists at this time.

You can submit a feature request for this.

PRTG Feature Requests

Benjamin Day
[Paessler Support]

Created on Oct 7, 2020 9:41:28 PM by  Benjamin Day [Paessler Support] (1,441) 2 1



Votes:

0

I'm trying to map some Office 365 addresses, could you confirm that the formatting is correct?

<group id="3020" name="Microsoft office365"> <caption>Microsoft office365</caption> <help>Mapeamento Microsoft office365</help> <defaultvalue>0</defaultvalue> <channels> <channel id="2049" name="Skype_19"> <rule> Protocol[TCP] and IP[52.244.160.207/32]) and ( DestinationPort[443] or SourcePort[443] or DestinationPort[80] or SourcePort[80] ) </rule> </channel> <channel id="2050" name="Skype_20"> <rule> (Protocol[TCP] or Protocol[udp] and IP[13.107.64.0/18]) and ( DestinationPort[443] or SourcePort[443] or DestinationPort[80] or SourcePort[80] or DestinationPort[3478] or SourcePort[3478] or DestinationPort[3479] or SourcePort[3479] or DestinationPort[3480] or SourcePort[3480] or DestinationPort[3481] or SourcePort[3481] ) </rule> </channel> </group>

Created on Oct 9, 2020 1:29:32 PM



Votes:

1

Hello Brunindf,

It looks good, you just forgot the closing channels.

<group id="3020" name="Microsoft office365"> <caption>Microsoft office365</caption> <help>Mapeamento Microsoft office365</help> <defaultvalue>0</defaultvalue> <channels> <channel id="2049" name="Skype_19"> <rule> Protocol[TCP] and IP[52.244.160.207/32]) and ( DestinationPort[443] or SourcePort[443] or DestinationPort[80] or SourcePort[80] ) </rule> </channel> <channel id="2050" name="Skype_20"> <rule> (Protocol[TCP] or Protocol[udp] and IP[13.107.64.0/18]) and ( DestinationPort[443] or SourcePort[443] or DestinationPort[80] or SourcePort[80] or DestinationPort[3478] or SourcePort[3478] or DestinationPort[3479] or SourcePort[3479] or DestinationPort[3480] or SourcePort[3480] or DestinationPort[3481] or SourcePort[3481] ) </rule> </channel> </channels> </group>

Benjamin Day
[Paessler Support]

Created on Oct 9, 2020 7:01:54 PM by  Benjamin Day [Paessler Support] (1,441) 2 1




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.