aa8b3b66f4
English grammar states that an en-dash should be used, not a hyphen between two years. ## Examples of each __em-dash__: — __en-dash__: – __hyphen__: - ## Em-dash An em-dash is typically used as a stand-in for a comma or parenthesis to separate out phrases—or even just a word—in a sentence for various reasons (i.e. an appositive). Examples where an em-dash should be used: * School is based on the three R’s—reading, writing, and ’rithmetic. * Against all odds, Pete—the unluckiest man alive—won the lottery. * I sense something; a presence I've not felt since— ## En-dash An en-dash is used to connect values in a range or that are related. A good rule is to use it when you're expressing a "to" relationship. Examples where an en-dash should be used: * in years 1939–1945 * pages 31–32 may be relevant * New York beat Los Angeles 98–95 * When American English would use an em-dash – following British and Canadian conventions. ## Hyphen A hyphen is used to join words in a compound construction, or separate syllables of a word, like during a line break, or (self-evidently) a hyphenated name. * pro-American * cruelty-free eggs * em-dash * it's pronounced hos-pi-tal-it-tee * Olivia Newton-John |
||
|---|---|---|
| docs | ||
| src | ||
| tasks | ||
| test | ||
| .bowerrc | ||
| .gitignore | ||
| .jshintrc | ||
| .travis.yml | ||
| bower.json | ||
| CONTRIBUTING.md | ||
| FAQ.md | ||
| Gruntfile.js | ||
| LICENSE.md | ||
| package.json | ||
| README.md | ||
| STYLEGUIDE.md | ||
Kibana 4.1.0-snapshot
Kibana is an open source (Apache Licensed), browser based analytics and search dashboard for Elasticsearch. Kibana is a snap to setup and start using. Kibana strives to be easy to get started with, while also being flexible and powerful, just like Elasticsearch.
Requirements
- Elasticsearch version 1.4.4 or later
- Kibana binary package
Installation
- Download: http://www.elasticsearch.org/overview/kibana/installation/
- Run
bin/kibanaon unix, orbin\kibana.baton Windows. - Visit http://localhost:5601
Quick Start
You're up and running! Fantastic! Kibana is now running on port 5601, so point your browser at http://YOURDOMAIN.com:5601.
The first screen you arrive at will ask you to configure an index pattern. An index pattern describes to Kibana how to access your data. We make the guess that you're working with log data, and we hope (because it's awesome) that you're working with Logstash. By default, we fill in logstash-* as your index pattern, thus the only thing you need to do is select which field contains the timestamp you'd like to use. Kibana reads your Elasticsearch mapping to find your time fields - select one from the list and hit Create.
Tip: there's an optimization in the way of the Use event times to create index names option. Since Logstash creates an index every day, Kibana uses that fact to only search indices that could possibly contain data in your selected time range.
Congratulations, you have an index pattern! You should now be looking at a paginated list of the fields in your index or indices, as well as some informative data about them. Kibana has automatically set this new index pattern as your default index pattern. If you'd like to know more about index patterns, pop into to the Settings section of the documentation.
Did you know: Both indices and indexes are acceptable plural forms of the word index. Knowledge is power.
Now that you've configured an index pattern, you're ready to hop over to the Discover screen and try out a few searches. Click on Discover in the navigation bar at the top of the screen.
Documentation
Visit Elasticsearch.org for the full Kibana documentation.