Nice tool.
Easy to add, clone the glustertool repo, and run
# ./newtool mnt_log_analyze --type=exec --bin=log_analyzer.sh --prog=bash
I used tool name "mnt_log_analyze" just for this example, feel free to
name your tool.
This will create following dir and files
I have a script written to analyze the log message of gluster process.
It actually scans the log file and identifies the log messages with ERROR
and WARNING levels.
It lists the functions (with either ERROR or WARNING logs) and their
percentage of occcurance.
It also lists the MSGIDs for ERROR
Also, don't forget to send a pull request to Aravinda, so that others can
use it too.
Maybe add some basic usage note. If it is not already there.
On Thu, Jan 28, 2016 at 7:04 AM, Aravinda wrote:
> Nice tool.
>
> Easy to add, clone the glustertool repo, and run
>
> #
On 10/27/2015 11:12 PM, Sankarshan Mukhopadhyay wrote:
On Mon, Oct 26, 2015 at 7:04 PM, Shyam wrote:
Older idea on this was, to consume the logs and filter based on the message
IDs for those situations that can be remedied. The logs are hence the point
where the event for
On Mon, Oct 26, 2015 at 7:04 PM, Shyam wrote:
> Older idea on this was, to consume the logs and filter based on the message
> IDs for those situations that can be remedied. The logs are hence the point
> where the event for consumption is generated.
>
> Also, the higher level
regards
Aravinda
On 10/23/2015 11:50 PM, Shyam wrote:
On 10/23/2015 06:46 AM, Aravinda wrote:
Hi Gluster developers,
In this mail I am proposing troubleshooting documentation and
Gluster Tools infrastructure.
Tool to search in documentation
===
We recently
regards
Aravinda
On 10/23/2015 11:42 PM, Vijay Bellur wrote:
On Friday 23 October 2015 04:16 PM, Aravinda wrote:
Hi Gluster developers,
In this mail I am proposing troubleshooting documentation and
Gluster Tools infrastructure.
Tool to search in documentation
===
regards
Aravinda
On 10/24/2015 07:01 AM, Sankarshan Mukhopadhyay wrote:
On Fri, Oct 23, 2015 at 4:16 PM, Aravinda wrote:
Initial idea for Tools Framework:
-
A Shell/Python script which looks for the tool in plugins sub directory, if
exists
Nice tool suggestions, added to the etherpad. Thanks.
regards
Aravinda
On 10/23/2015 04:25 PM, Amit Chaurasia wrote:
A few more:
1.A tool to determine the back end brick location given a file name.
2. A rebalance meter which allows me to determine if it's high time to
perform rebalance.
On
On 10/23/2015 09:31 PM, Sankarshan Mukhopadhyay wrote:
On Fri, Oct 23, 2015 at 4:16 PM, Aravinda wrote:
Initial idea for Tools Framework:
-
A Shell/Python script which looks for the tool in plugins sub directory, if
exists pass all the
On 10/23/2015 06:46 AM, Aravinda wrote:
Hi Gluster developers,
In this mail I am proposing troubleshooting documentation and
Gluster Tools infrastructure.
Tool to search in documentation
===
We recently added message Ids to each error messages in Gluster. Some
of
Hi Gluster developers,
In this mail I am proposing troubleshooting documentation and
Gluster Tools infrastructure.
Tool to search in documentation
===
We recently added message Ids to each error messages in Gluster. Some
of the error messages are self explanatory.
A few more:
1.A tool to determine the back end brick location given a file name.
2. A rebalance meter which allows me to determine if it's high time to
perform rebalance.
On Oct 23, 2015 4:16 PM, "Aravinda" wrote:
> Hi Gluster developers,
>
> In this mail I am proposing
On Fri, Oct 23, 2015 at 4:16 PM, Aravinda wrote:
> Initial idea for Tools Framework:
> -
> A Shell/Python script which looks for the tool in plugins sub directory, if
> exists pass all the arguments and call that script.
>
> `glustertool help`
14 matches
Mail list logo