Ported BandwidthMonitor utility to.Net Core 3.1#1
Open
paragpkulkarni wants to merge 5 commits into
Open
Conversation
… contained single file executable.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I have migrated this utility to .Net Core 3.1. Now you can run it on linux. I found this utility quite useful for checking bandwidth usage on Redis server. Deployment of this utility is super easy since it is self contained single exe. There is no need of .Net Core installation on the target machine. Simply xcopy the file and give the appropriate permission to run it on linux server. Bandwidth usage on Redis server can be easily monitored.