# ANN: es-diag - elastic search sanity checks/diagnostics **URL:** \ **Category:** Elasticsearch\ **Created:** [June 14, 2012, 2:18pm UTC](https://discuss.elastic.co/t/ann-es-diag-elastic-search-sanity-checks-diagnostics/8104 "2012-06-14T14:18:41Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Dotan\_Nahum](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@Dotan\_Nahum](https://discuss.elastic.co/u/Dotan_Nahum)\ **Post date:** [June 14, 2012, 2:18pm UTC](https://discuss.elastic.co/t/ann-es-diag-elastic-search-sanity-checks-diagnostics/8104/1 "2012-06-14T14:18:41Z")
Hello group, I'd like to announce es-diag > **[jondot/es-diag](https://github.com/jondot/es-diag)** > > es-diag - Elastic Search health checks and problem discovery toolkit I've decided to build a tool for our ops, to assist discovering improper Elastic Search machine configuration. The goal is to provide 0-friction and fast problem discovery for ops before they start implementing Elastic Search, and while they are running an instance. Right now the bare minimum is implemented in terms of checks - that is, the common 'too many open files' ulimit problem. However the needed framework is in place such that you can write a 'check' script using the simple DSL-like structure, and send a pull request pretty easily. In the immediate future, I'm planning integration with a running instance's cluster info to warn about health problems. In addition, a quiet-mode where the tool can be easily integrated with monitoring tools such as nagios/zabbix and the sorts. Please feel free to ask me questions directly, here, or open issues/pull requests Hope this helps, Dotan ---
**Author:** ![nelalx](https://avatars.discourse-cdn.com/v4/letter/n/7c8e57/32.png) [@nelalx](https://discuss.elastic.co/u/nelalx)\ **Post date:** [June 16, 2012, 9:50am UTC](https://discuss.elastic.co/t/ann-es-diag-elastic-search-sanity-checks-diagnostics/8104/2 "2012-06-16T09:50:35Z")
Hi ``` Great work on es-diag...I jus tried to install es-diag and got warnings ``` like Unrecognized directive 'short' in README.rdoc Unrecognized directive 'long' in README.rdoc Unrecognized directive 'description' in README.rdoc Unrecognized directive 'default' in README.rdoc Unrecognized directive 'required' in README.rdoc Unrecognized directive 'on' in README.rdoc Unrecognized directive 'boolean' in README.rdoc Unrecognized directive 'show\_options' in README.rdoc Unrecognized directive 'exit' in README.rdoc Unrecognized directive 'proc' in README.rdoc But it got installed..When i tried to check the status it shows the following error... Invalid gemspec in [/var/lib/gems/1.8/specifications/es-diag-0.0.1.gemspec]: invalid date format in specification: "2012-06-14 00:00:00.000000000Z" /usr/lib/ruby/vendor\_ruby/1.8/rubygems.rb:926:in `report_activate_error': Could not find RubyGem es-diag (>= 0) (Gem::LoadError) from /usr/lib/ruby/vendor_ruby/1.8/rubygems.rb:244:in`activate\_dep' from /usr/lib/ruby/vendor\_ruby/1.8/rubygems.rb:236:in `activate' from /usr/lib/ruby/vendor_ruby/1.8/rubygems.rb:1307:in`gem' from /usr/local/bin/es-diag:18 Being a newbie in ruby and this, please help me overcome this issue... Thanks and regards Nel ---
**Author:** ![Dotan\_Nahum](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@Dotan\_Nahum](https://discuss.elastic.co/u/Dotan_Nahum)\ **Post date:** [June 17, 2012, 3:46pm UTC](https://discuss.elastic.co/t/ann-es-diag-elastic-search-sanity-checks-diagnostics/8104/3 "2012-06-17T15:46:25Z")
issue fixed in 0.0.2 On Saturday, June 16, 2012 12:50:35 PM UTC+3, nel wrote: > Hi > > ``` > Great work on es-diag...I jus tried to install es-diag and got > > ``` > > warnings > > like > > Unrecognized directive 'short' in README.rdoc > Unrecognized directive 'long' in README.rdoc > Unrecognized directive 'description' in README.rdoc > Unrecognized directive 'default' in README.rdoc > Unrecognized directive 'required' in README.rdoc > Unrecognized directive 'on' in README.rdoc > Unrecognized directive 'boolean' in README.rdoc > Unrecognized directive 'show\_options' in README.rdoc > Unrecognized directive 'exit' in README.rdoc > Unrecognized directive 'proc' in README.rdoc > > But it got installed..When i tried to check the status it shows the > following error... > > Invalid gemspec in > [/var/lib/gems/1.8/specifications/es-diag-0.0.1.gemspec]: > invalid date format in specification: "2012-06-14 00:00:00.000000000Z" > /usr/lib/ruby/vendor\_ruby/1.8/rubygems.rb:926:in `report_activate_error': Could not find RubyGem es-diag (>= 0) (Gem::LoadError) from /usr/lib/ruby/vendor_ruby/1.8/rubygems.rb:244:in `activate\_dep' > from /usr/lib/ruby/vendor\_ruby/1.8/rubygems.rb:236:in `activate' from /usr/lib/ruby/vendor_ruby/1.8/rubygems.rb:1307:in `gem' > from /usr/local/bin/es-diag:18 > > Being a newbie in ruby and this, please help me overcome this issue... > Thanks and regards > > Nel > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/ANN-es-diag-elastic-search-sanity-checks-diagnostics-tp4019301p4019413.html](http://elasticsearch-users.115913.n3.nabble.com/ANN-es-diag-elastic-search-sanity-checks-diagnostics-tp4019301p4019413.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:23am UTC](https://discuss.elastic.co/t/ann-es-diag-elastic-search-sanity-checks-diagnostics/8104/4 "2017-07-06T03:23:42Z")