You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am most interested in tracking traffic to and from the internet with my router and not so much traffic that is internal to my network. It would be nice if when the source and destination both match the network range parameter, that a tag called "traffic_type" is set to local, otherwise it would be set to external (Using a tag instead of a boolean field to allow for faster searching).
I'll be forking this project and creating a pull request of this feature, but would like some feedback if this would be accepted back into this codebase.
The text was updated successfully, but these errors were encountered:
Hey, thanks for the suggestion and the pull request. It might take the week before I check but i will give feedback and merge if everything is ok. I should be able to put some time on it before the end of next week.
I took a look at your suggestion and it is a great idea. However, I think that if we go down that route, we need to add both local and external traffic separately. I would add $local_down_byte and $external_down_byte. That way, people who just need external can also plot their graph.
I am most interested in tracking traffic to and from the internet with my router and not so much traffic that is internal to my network. It would be nice if when the source and destination both match the network range parameter, that a tag called "traffic_type" is set to local, otherwise it would be set to external (Using a tag instead of a boolean field to allow for faster searching).
I'll be forking this project and creating a pull request of this feature, but would like some feedback if this would be accepted back into this codebase.
The text was updated successfully, but these errors were encountered: