Re: Traffic sent and traffic received in historical view in ntopng

Emanuele Faranda <[email protected]>
Newsgroups gmane.linux.ntop.general
Organization ntop
Message-ID <[email protected]>
No, it is also available in the community version.
It should be enabled by default, please verify that the "Traffic" 
preference under "Data Retention" settings is enabled.

Note: local networks data is dumped to disk each 5 minutes.

Emanuele

On 05/15/2017 04:38 PM, Andrew Hilborne wrote:
> It's the ingress/egress bytes _per local network_ which I am 
> interested in. Thank you - I have found this now.
>
> However, it is showing no data. I think this is a licensed feature?
>
> Andrew
>
> On 15 May 2017 at 15:21, Emanuele Faranda faranda-at-ntop.org 
> <http://faranda-at-ntop.org> |ntop-flugle| <[email protected] 
> <mailto:[email protected]>> wrote:
>
>     The graph at the link shows *host* traffic, which indeed is split
>     between sent and received. The *interface* graph instead does not
>     make such a distinction.
>
>     In ntopng we have graphs for:
>     - interfaces: total bytes
>     - local hosts: sent, received bytes
>     - local networks: ingress, egress, inner bytes
>     - .. and others
>
>     If you really want *interface* traffic to be split, please open a
>     feature request on our github page https://github.com/ntop/ntopng.
>
>     Regards,
>     Emanuele
>
>
>     On 05/15/2017 04:11 PM, Andrew Hilborne wrote:
>>     I believe I know what you mean:
>>     http://www.ntop.org/ntopng/exploring-historical-data-using-ntopng/
>>     <http://www.ntop.org/ntopng/exploring-historical-data-using-ntopng/>
>>     shows exactly this information. However my own installation shows
>>     a similar graphic, but without the 'traffic (Sent)' and 'traffic
>>     (Recvd)' designations.
>>
>>     Andrew
>>
>>     On 15 May 2017 at 10:18, Emanuele Faranda faranda-at-ntop.org
>>     <http://faranda-at-ntop.org> |ntop-flugle|
>>     <[email protected] <mailto:[email protected]>> wrote:
>>
>>         Hi Andrew,
>>         Currently ntopng saves the interface RRD data as the total
>>         number of bytes, so it not possible to get a differentiated
>>         sent/received view.
>>         However, you can get such differentiated metrics from the
>>         Local Networks page.
>>
>>         Emanuele
>>
>>
>>         On 05/12/2017 08:02 PM, Andrew Hilborne wrote:
>>>         Hi,
>>>
>>>         Can someone please tell me what I need to do to get
>>>         differentiated traffic sent and received in the 'historical
>>>         view' on an interface?
>>>
>>>         Thanks in advance.
>>>
>>>         Andrew
>>>
>>>
>>>         _______________________________________________
>>>         Ntop mailing list
>>>         [email protected] <mailto:[email protected]>
>>>         http://listgateway.unipi.it/mailman/listinfo/ntop
>>>         <http://listgateway.unipi.it/mailman/listinfo/ntop>
>>
>>
>>         _______________________________________________
>>         Ntop mailing list
>>         [email protected] <mailto:[email protected]>
>>         http://listgateway.unipi.it/mailman/listinfo/ntop
>>         <http://listgateway.unipi.it/mailman/listinfo/ntop>
>>
>>
>>
>>
>>     _______________________________________________
>>     Ntop mailing list
>>     [email protected] <mailto:[email protected]>
>>     http://listgateway.unipi.it/mailman/listinfo/ntop
>>     <http://listgateway.unipi.it/mailman/listinfo/ntop>
>
>
>     _______________________________________________
>     Ntop mailing list
>     [email protected] <mailto:[email protected]>
>     http://listgateway.unipi.it/mailman/listinfo/ntop
>     <http://listgateway.unipi.it/mailman/listinfo/ntop>
>
>
>
>
> _______________________________________________
> Ntop mailing list
> [email protected]
> http://listgateway.unipi.it/mailman/listinfo/ntop

_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.