Traffic control feature #8
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A traffic control feature was needed in my case (the majority of cloud providers do not offer unlimited traffic and the usage can get out of hand pretty quickly and even lead to unwanted charges/invoices). These changes solve this problem by adding a Traffic control feature to the script. So far I did test ist in a couple of my environments, and it works, but feel free to only use the useful parts.
Summary of the changes/additions:
Traffic monitoring - Tracks cumulative upload/download by parsing Docker logs
Configurable limit - Set monthly GB cap during install or via conduit traffic limit
Automatic enforcement - Background monitor stops the container when the limit is exceeded
Persistent tracking - Usage survives container/server restarts via traffic.dat
Delta-based counting - Detects container restarts to avoid double-counting
Thank you.