<commit_before># Kibana
Copyright 2012 <NAME> <rashidkpc #logstash irc.freenode.net>

Kibana is a browser based interface for Logstash and ElasticSearch that allows 
you to efficiently search, visualize, analyze and otherwise make sense of your 
logs. 

## Requirements

ruby >= 1.8.7 (probably?)  
bundler  
logstash >= 1.1.0  
elasticsearch >= 0.18.0  

## Installation
Install:  
  git clone --branch=kibana-ruby <EMAIL>:rashidkpc/Kibana.git
	cd Kibana  
	gem install bundler  
	bundle install  

Configure:  
Set your elasticsearch server in KibanaConfig.rb:  
	Elasticsearch = "elasticsearch:9200"  

Run:  
	ruby kibana.rb  

Use:  
  Point your browser at http://localhost:5601

## FAQ
Q: Why is there no last button?  
A: ElasticSearch isn't so hot at going to the last result of a many million 
result query. 

Q: Why is this Ruby instead of PHP now?  
A: Closer integreation with logstash, Ruby is shiny. Its mostly javascript 
anyway. If you want it in something else, it shouldn't be too hard to port.  

Q: Why do I have to set a limit on events to analyze  
A: Big result sets take a long time to retrieve from elasticsearch and parse out  

Q: Well then why don't you use the Elastic Search terms facet?  <commit_msg>Added git command to README.md<commit_after># Kibana
Copyright 2012 <NAME> <rashidkpc #logstash irc.freenode.net>

Kibana is a browser based interface for Logstash and ElasticSearch that allows 
you to efficiently search, visualize, analyze and otherwise make sense of your 
logs. 

## Requirements

ruby >= 1.8.7 (probably?)  
bundler  
logstash >= 1.1.0  
elasticsearch >= 0.18.0  

## Installation
Install:  
  git clone --branch=kibana-ruby <EMAIL>:rashidkpc/Kibana.git  
	cd Kibana  
	gem install bundler  
	bundle install  

Configure:  
Set your elasticsearch server in KibanaConfig.rb:  
	Elasticsearch = "elasticsearch:9200"  

Run:  
	ruby kibana.rb  

Use:  
  Point your browser at http://localhost:5601

## FAQ
Q: Why is there no last button?  
A: ElasticSearch isn't so hot at going to the last result of a many million 
result query. 

Q: Why is this Ruby instead of PHP now?  
A: Closer integreation with logstash, Ruby is shiny. Its mostly javascript 
anyway. If you want it in something else, it shouldn't be too hard to port.  

Q: Why do I have to set a limit on events to analyze  
A: Big result sets take a long time to retrieve from elasticsearch and parse out  

Q: Well then why don't you use the Elastic Search terms facet?  
{'fraction_non_alphanumeric': 0.06322996375352397, 'fraction_numerical': 0.017720499395892066, 'mean_word_length': 3.5830258302583027, 'pattern_counts': {'":': 0, '<': 9, '<?xml version=': 0, '>': 15, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5945170', 'n_tokens_mistral': 843, 'n_tokens_neox': 794, 'n_words': 350}