Vector map

.gitignore

@@ -36,3 +36,4 @@ selenium
 *.swo
 *.out
 ui_framework/doc_site/build/*.js*
+yarn.lock

CONTRIBUTING.md

@@ -146,16 +146,15 @@ Now you can point your web browser to https://localhost:5601 and start using Kib
 
 #### Customizing `config/kibana.dev.yml`
 
-The `config/kibana.yml` file stores user configuration directives. Since this file is checked into source control, however, developer preferences can't be saved without the risk of accidentally committing the modified version. To make customizing configuration easier during development, the Kibana CLI will look for a `config/kibana.dev.yml` file if run with the `--dev` flag. This file behaves just like the non-dev version and accepts any of the [standard settings](https://www.elastic.co/guide/en/kibana/master/kibana-server-properties.html).
+The `config/kibana.yml` file stores user configuration directives. Since this file is checked into source control, however, developer preferences can't be saved without the risk of accidentally committing the modified version. To make customizing configuration easier during development, the Kibana CLI will look for a `config/kibana.dev.yml` file if run with the `--dev` flag. This file behaves just like the non-dev version and accepts any of the [standard settings](https://www.elastic.co/guide/en/kibana/current/settings.html).
 
-The `config/kibana.dev.yml` file is very commonly used to store some opt-in/**unsafe** optimizer tweaks which can significantly increase build performance. Below is a commonly used `config/kibana.dev.yml` file, but additional options can be found [in #4611](https://github.com/elastic/kibana/pull/4611#issue-99706918).
+#### Potential Optimization Pitfalls
 
-```yaml
-optimize:
-  sourceMaps: '#cheap-source-map' # options -> http://webpack.github.io/docs/configuration.html#devtool
-  unsafeCache: true
-  lazyPrebuild: false
-```
+In development mode, Kibana runs a customized version of [Webpack](http://webpack.github.io/) with some optimizations enabled to make building the browser bundles as fast as possible. These optimizations make the build process about 2x as fast for initial builds, and about 7x faster for rebuilds, but are labeled "unsafe" by Webpack because they can sometimes cause changes to go unnoticed by the compiler. If you experience any of the scenarios below either restart the dev server, or add `optimize.unsafeCache: false` to your `config/kibana.dev.yml` file to disable these optimizations completely.
+
+ - Webpack is trying to include a file in the bundle that I deleted and is now complaining about it is missing
+ - A module id that used to resolve to a single file now resolves to a directory, but webpack isn't adapting
+ - (if you discover other scenarios, please send a PR!)
 
 #### Setting Up SSL
 
@@ -375,4 +374,4 @@ Remember, someone is blocked by a pull awaiting review, make it count. Be thorou
 1. **Hand it off** If you're the first reviewer and everything looks good but the changes are more than a few lines, hand the pull to someone else to take a second look. Again, try to find the right person to assign it to.
 1. **Merge the code** When everything looks good, put in a `LGTM` (looks good to me) comment. Merge into the target branch. Check the labels on the pull to see if backporting is required, and perform the backport if so.
 
-Thank you so much for reading our guidelines! :tada:
+Thank you so much for reading our guidelines! :tada:

FAQ.md

@@ -1,24 +1,23 @@
 # Frequently asked questions
 
-**Q:** I'm getting `bin/node/bin/node: not found` but I can see the node binary in the package?      
-**A:** Kibana 4 packages are architecture specific. Ensure you are using the correct package for your architecture. 
+**Q:** I'm getting `bin/node/bin/node: not found` but I can see the node binary in the package?
+**A:** Kibana 4 packages are architecture specific. Ensure you are using the correct package for your architecture.
 
-**Q:** Where do I go for support?  
-**A:** Please join us at [discuss.elastic.co](https://discuss.elastic.co) with questions. Your problem might be a bug, but it might just be a misunderstanding, or feature we could improve. We're also available on Freenode in #kibana
+**Q:** Where do I go for support?
+**A:** Please join us at [discuss.elastic.co](https://discuss.elastic.co) with questions. Your problem might be a bug, but it might just be a misunderstanding, or a feature we could improve. We're also available on Freenode in #kibana
 
-**Q:** Ok, we talked about it and its definitely a bug  
+**Q:** Ok, we talked about it and its definitely a bug
 **A:** Doh, ok, let's get that fixed. File an issue on [github.com/elastic/kibana](https://github.com/elastic/kibana). I'd recommend reading the beginning of the CONTRIBUTING.md, just so you know how we'll handle the issue.
 
 ### Kibana 3 Migration
-**Q:** Where is feature X that I loved from Kibana 3?  
+**Q:** Where is feature X that I loved from Kibana 3?
 **A:** It might be coming! We’ve published our immediate roadmap as tickets. Check out the beta milestones on GitHub to see if the feature you’re missing is coming soon.
 
-**Q:** Is the dashboard schema compatible?  
-**A:** Unfortunately, they are not compatible. In order to create the new features we wanted, it simply was not possible to keep the same schema. Aggregations work fundamentally different from facets, the new dashboard isn’t tied to rows and columns and the relationships between searches, visualizations and the dashboard are complex enough that we simply had to design something more flexible.
+**Q:** Is the dashboard schema compatible?
+**A:** Unfortunately, it is not compatible. In order to create the new features we wanted, it simply was not possible to keep the same schema. Aggregations work fundamentally different from facets, the new dashboard isn’t tied to rows and columns, and the relationships between searches, visualizations and the dashboard are complex enough that we simply had to design something more flexible.
 
-**Q:** How do I do multi-query?  
+**Q:** How do I execute a multi-query?
 **A:** The ‘filters’ aggregations will allow you to input multiple queries and compare them visually. You can even use Elasticsearch JSON in there!
 
-**Q:** What happened to templated/scripted dashboards?  
+**Q:** What happened to templated/scripted dashboards?
 **A:** Check out the URL. The state of each app is stored there, including any filters, queries or columns. This should be a lot easier than constructing scripted dashboards. The encoding of the URL is RISON.
-

LICENSE.md

@@ -1,4 +1,4 @@
-Copyright 2012–2016 Elasticsearch BV
+Copyright 2012–2017 Elasticsearch BV
 
 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
 

docs/console.asciidoc

@@ -59,12 +59,6 @@ When the response come back, you should see it in the left hand panel:
 .The Output Pane
 image::images/introduction_output.png[Screenshot]
 
-Console allows you to easily switch between Elasticsearch instances. By default it will connect to `localhost:9200`
-but you can easily change this by entering a different url in the Server input:
-
-.The Server Input
-image::images/introduction_server.png["Server",width=400,align="center"]
-
 [float]
 [[console-ui]]
 == The Console UI

docs/development/plugin/development-internationalization.asciidoc

@@ -0,0 +1,187 @@
+[[translating-kibana]]
+Translating Kibana
+------------------
+
+[[background]]
+Background
+~~~~~~~~~
+
+Please see https://github.com/elastic/kibana/issues/6515[kibana#6515]
+for background discussion on the Kibana translation work.
+
+[[prerequisites]]
+Prerequisites
+~~~~~~~~~~~~
+
+Kibana must be installed and operational, see README.md
+
+[[audience]]
+Audience
+~~~~~~~
+
+There are three audiences for this document:
+
+* those that want to contribute language packs to Kibana
+* those that want to enable translations in existing Kibana plugins
+* those that want to create a new Kibana Plugin
+
+[[contributing-language-packs]]
+Contributing Language Packs
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+For this example, we will demonstrate translation into Maltese (Language
+code `mt`). Add-on functionality for Kibana is implemented with plug-in modules.
+Refer to
+https://www.elastic.co/guide/en/kibana/current/kibana-plugins.html[Kibana
+Plugins] for more details.
+
+* Fork the `kibana` source, and ensure you have an up to date copy of
+the source.
+* Ensure you have signed the agreement as in CONTRIBUTING.md
+* Choose the right link:[bcp47] language code for your work. In this
+example, we will use the `kibana` plugin for translating and `mt` for
+Maltese. Other examples might be `zh-Hans` for Chinese using Simplified
+characters, or `az-Cyrl` for Azerbaijani using Cyrillic characters. The
+following links can help:
+* https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes[List of ISO
+639-1 codes]
+*
+http://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code[“Picking
+the right language code”]
+* Create a new branch for your work:
++
+git checkout -b translate-mt
+* For each translation scope (see link:#Enabling%20Translations%20on%20Existing%20Plugins[Enabling Translations on Existing Plugins], below), generate a Kibana plugin with name _plugin_-_languagecode_ using the https://github.com/elastic/generator-kibana-plugin[Kibana Plugin Yeoman Generator]:
++
+* Replace the the `es.json` translation file with _languagecode_`.json`:
+`mv src/plugins/kibana-mt/translations/es.json src/plugins/kibana-mt/translations/mt.json`
+* Translate the `mt.json` file in a JSON editor
+* Edit index file (`kibana-mt/index.js`), updating the
+'translations' item in 'uiExports' as per your plugin translation file(s)
+* Copy translations plugin (`kibana-mt/`) to the Kibana plugins (`<kibana_root>/plugins`) directory
+* Start up Kibana and verify the translation works as expected
+* Ensure Kibana tests pass
+* Commit the `kibana-mt` directory and files, and push them to your own
+fork of `kibana`
+* Open a pull request titled `Translation: Maltese (mt)`
+
+[[enabling-ranslations-on-existing-plugins]]
+Enabling Translations on Existing Plugins
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Kibana translates according to plugin scope, so there is a `.json` file
+in `translations` subdirectory for each plugin.
+
+[[enabling-translation-of-an-angular-view]]
+Enabling Translation of an Angular view
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+* Determine which views share a plugin scope. In this example, `create`
+and `edit` will share scope.
+* If it does not already exist, Create the appropriate `translation`
+directory and the new translation file `en.json` inside it. In the above
+example, it would be: `src/core_plugins/kibana/translations/en.json`
+* If it does not exist add 'translations' item to the 'uiExports' in the plugin creation (`src/core_plugins/kibana/translations/en.json`) as follows:
+-------------------------------------------------------------------------
+uiExports {
+  translations: [ 
+    resolve(__dirname, './translations/en.json')
+  ], ….
+}
+-------------------------------------------------------------------------
+
+* In the view (HTML) file, such as
+`src/core_plugins/kibana/public/management/sections/indices/_create.html`
+Replace English text with translation keys, and copy the English text
+into the `en.json` file appropriately. Note that loose text was put into
+a `<p></p>` tag for translation purposes. Also note the prefix `KIBANA-`
+matching the plugin being translated.
+
+[[before]]
+Before
+++++++
+
+`_create.html`
+
+-----------------------------------------------------------------------------------------------------
+    <h1>Configure an index pattern</h1>
+    In order to use Kibana you must configure at least one index pattern…
+
+    <kbn-info info="This field will be used to filter events with the global time filter"></kbn-info> 
+-----------------------------------------------------------------------------------------------------
+
+[[after]]
+After
++++++
+
+`_create.html`
+
+-------------------------------------------------------------------------------------------
+    <h1 translate="KIBANA-CONFIGURE_INDEX_PATTERN"</h1>
+    <p translate="KIBANA-MUST_CONFIGURE_INDEX_PATTERN"</p>
+
+    <kbn-info info="{{ 'KIBANA-FIELD_FILTER_EVENTS_GLOBAL_TIME' | translate }}"></kbn-info>
+-------------------------------------------------------------------------------------------
+
+* In the view (JS) file, such as
+`src/core_plugins/kibana/public/management/sections/indices/_create.js`
+As above, replace English text with translation keys, and copy the English text
+into the `en.json` file appropriately. Note that some strings may not be user facing
+and do not need to be replaced then. Also note the prefix `KIBANA-` matching the plugin
+being translated.
+
+[[before]]
+Before
+++++++
+
+`_create.js`
+
+--------------------------------------------------------------------------------------------------------------
+    notify.error('Could not locate any indices matching that pattern. Please add the index to Elasticsearch');
+--------------------------------------------------------------------------------------------------------------
+
+[[after]]
+After
++++++
+
+`_create.js`
+
+-------------------------------------------------------------------------------------------
+    notify.error($translate.instant('KIBANA-NO_INDICES_MATCHING_PATTERN'));
+-------------------------------------------------------------------------------------------
+
+`en.json`
+
+-----------------------------------------------------------------------------------------------------------------------------------------
+    {
+       "KIBANA-CONFIGURE_INDEX_PATTERN": "Configure an index pattern",
+       "KIBANA-MUST_CONFIGURE_INDEX_PATTERN": "In order to use Kibana you must…",
+       "KIBANA-FIELD_FILTER_EVENTS_GLOBAL_TIME" : "This field will be used to filter events with the global time filter",
+       "KIBANA-NO_INDICES_MATCHING_PATTERN": "Could not locate any indices matching that pattern. Please add the index to Elasticsearch",
+    }
+-----------------------------------------------------------------------------------------------------------------------------------------
+
+* Refresh the Kibana page and verify the UI looks the same.
+* Refer to Kibana core plugin (`src/core_plugins/kibana/`) for examples.
+
+[[new-plugin-authors]]
+New Plugin Authors
+~~~~~~~~~~~~~~~~~
+
+Add-on functionality for Kibana is implemented with plug-in modules.
+Refer to
+https://www.elastic.co/guide/en/kibana/current/kibana-plugins.html[Kibana
+Plugins] for more details. It is recommended that when creating a plugin
+you enable translations (see link:#Enabling%20Translations%20on%20Existing%20Plugins[Enabling Translations on Existing Plugins], above).
+
+[[enabling-translation-in-a-plugin]]
+Enabling Translation in a New Plugin
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+* Generate a Kibana plugin using the https://github.com/elastic/generator-kibana-plugin[Kibana Plugin Yeoman Generator]. In this
+example, `plugin1`
+* Add the translation IDs to the views
+* Add the corresponding translation IDs and text to the default translation file (`translations/en.json`)
+* Refer to link:#Enabling%20Translations%20on%20Existing%20Plugins[Enabling Translations on Existing Plugins] for more
+details on enabling translation in your plugin views and refer to Kibana
+core plugin (`src/core_plugins/kibana/`) for an example.

docs/management/advanced-options.asciidoc

@@ -78,7 +78,6 @@ Markdown.
 `notifications:lifetime:error`:: Specifies the duration in milliseconds for error notification displays. The default value is 300000. Set this field to `Infinity` to disable error notifications.
 `notifications:lifetime:warning`:: Specifies the duration in milliseconds for warning notification displays. The default value is 10000. Set this field to `Infinity` to disable warning notifications.
 `notifications:lifetime:info`:: Specifies the duration in milliseconds for information notification displays. The default value is 5000. Set this field to `Infinity` to disable information notifications.
-
 `timelion:showTutorial`:: Set this property to `true` to show the Timelion tutorial to users when they first open Timelion.
 `timelion:es.timefield`:: Default field containing a timestamp when using the `.es()` query.
 `timelion:es.default_index`:: Default index when using the `.es()` query.
@@ -89,3 +88,5 @@ Markdown.
 `timelion:graphite.url`:: [experimental] Used with graphite queries, this it the URL of your host
 `timelion:quandl.key`:: [experimental] Used with quandl queries, this is your API key from www.quandl.com
 `state:storeInSessionStorage`:: [experimental] Kibana tracks UI state in the URL, which can lead to problems when there is a lot of information there and the URL gets very long. Enabling this will store parts of the state in your browser session instead, to keep the URL shorter.
+`context:defaultSize`:: Specifies the initial number of surrounding entries to display in the context view. The default value is 5.
+`context:step`:: Specifies the number to increment or decrement the context size by when using the buttons in the context view. The default value is 5.

docs/migration/migrate_6_0.asciidoc

@@ -10,4 +10,14 @@ your application to Kibana 6.0.
 Kibana 6.0 will only support Painless and Lucene expression based scripts.
 
 
-*Impact:* You will need to migrate your groovy, python, javascript, etc. scripted fields to Painless or Lucene expressions.
+*Impact:* You will need to migrate your groovy, python, javascript, etc. scripted fields to Painless or Lucene expressions.
+
+[float]
+=== Changed response format of status API
+*Details:* In an effort to align with our style guidelines and provide a digestible response,
+the status API has changed:
+
+* Properties are now snake cased and several have been renamed
+* Metrics now provide the latest available data instead of samples over time
+
+*Impact:* You will need to update anything using the status API and expecting the previous response format.

docs/plugins/known-plugins.asciidoc

@@ -17,6 +17,7 @@ This list of plugins is not guaranteed to work on your version of Kibana. Instea
 === Apps
 * https://github.com/sivasamyk/logtrail[LogTrail] - View, analyze, search and tail log events in realtime with a developer/sysadmin friendly interface
 * https://github.com/wtakase/kibana-own-home[Own Home] (wtakase) - enables multi-tenancy
+* https://github.com/asileon/kibana_shard_allocation[Shard Allocation] (asileon) - visualize elasticsearch shard allocation
 
 [float]
 === Timelion Extensions
@@ -35,6 +36,10 @@ This list of plugins is not guaranteed to work on your version of Kibana. Instea
 * https://github.com/clamarque/Kibana_health_metric_vis[Health Metric] (clamarque)
 * https://github.com/ommsolutions/kibana_ext_metrics_vis[Extended Metric] (ommsolutions)
 * https://github.com/virusu/3D_kibana_charts_vis[3D Charts] (virusu)
+* https://github.com/DeanF/health_metric_vis[Colored Metric Visualization] (deanf)
+* https://github.com/elo7/cohort[Cohort analysis] (elo7)
+* https://github.com/amannocci/kibana-plugin-metric-percent[Percent] (amannocci)
+* https://github.com/outbrain/ob-kb-funnel[Funnel Visualization] (roybass)
 
 [float]
 === Other