Merge remote-tracking branch 'upstream/master' into feature/ccr

elastic · Jan 16, 2019 · 17cae34 · 17cae34
2 parents 19f604a + a00d487
commit 17cae34
Show file tree

Hide file tree

Showing 343 changed files with 7,434 additions and 2,883 deletions.
diff --git a/.eslintrc.js b/.eslintrc.js
@@ -203,6 +203,34 @@ module.exports = {
       },
     },
 
+    /**
+     * Files that run in the browser with only node-level transpilation
+     */
+    {
+      files: [
+        'test/functional/services/lib/leadfoot_element_wrapper/scroll_into_view_if_necessary.js',
+      ],
+      rules: {
+        'prefer-object-spread/prefer-object-spread': 'off',
+        'no-var': 'off',
+        'prefer-const': 'off',
+        'prefer-destructuring': 'off',
+        'no-restricted-syntax': [
+          'error',
+          'ArrowFunctionExpression',
+          'AwaitExpression',
+          'ClassDeclaration',
+          'RestElement',
+          'SpreadElement',
+          'YieldExpression',
+          'VariableDeclaration[kind="const"]',
+          'VariableDeclaration[kind="let"]',
+          'VariableDeclarator[id.type="ArrayPattern"]',
+          'VariableDeclarator[id.type="ObjectPattern"]',
+        ],
+      },
+    },
+
     /**
      * Files that run AFTER node version check
      * and are not also transpiled with babel

diff --git a/NOTICE.txt b/NOTICE.txt
@@ -34,6 +34,32 @@ THE SOFTWARE.
 This product uses Noto fonts that are licensed under the SIL Open
 Font License, Version 1.1.
 
+---
+Based on the scroll-into-view-if-necessary module from npm
+https://github.com/stipsan/compute-scroll-into-view/blob/master/src/index.ts#L269-L340
+
+MIT License
+
+Copyright (c) 2018 Cody Olsen
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
 ---
 Pretty handling of logarithmic axes.
 Copyright (c) 2007-2014 IOLA and Ole Laursen.

diff --git a/docs/images/index-lifecycle-policies-create.png b/docs/images/index-lifecycle-policies-create.png
diff --git a/docs/images/index_lifecycle_policies_options.png b/docs/images/index_lifecycle_policies_options.png
diff --git a/docs/images/index_management_add_policy.png b/docs/images/index_management_add_policy.png
diff --git a/docs/management.asciidoc b/docs/management.asciidoc
@@ -19,6 +19,16 @@ include::management/rollups/create_and_manage_rollups.asciidoc[]
 
 include::management/rollups/visualize_rollup_data.asciidoc[]
 
+include::management/index-lifecycle-policies/intro-to-lifecycle-policies.asciidoc[]
+
+include::management/index-lifecycle-policies/create-policy.asciidoc[]
+
+include::management/index-lifecycle-policies/manage-policy.asciidoc[]
+
+include::management/index-lifecycle-policies/add-policy-to-index.asciidoc[]
+
+include::management/index-lifecycle-policies/example-index-lifecycle-policy.asciidoc[]
+
 include::management/managing-fields.asciidoc[]
 
 include::management/managing-indices.asciidoc[]

diff --git a/docs/management/index-lifecycle-policies/add-policy-to-index.asciidoc b/docs/management/index-lifecycle-policies/add-policy-to-index.asciidoc
@@ -0,0 +1,17 @@
+[[adding-policy-to-index]]
+=== Adding a policy to an index
+
+You can add a lifecycle policy to an index and view the status for indices 
+managed by a policy in *Management > {es} > Index Management*.  This page lists your 
+{es} indices, which you can filter by lifecycle status and lifecycle phase.  
+
+To add a policy, select the index name and then select *Manage > Add lifecycle policy*.
+You’ll see the policy name, the phase the index is in, the current 
+action, and if any errors occurred performing that action. 
+
+To remove a policy from an index, select *Manage > Remove lifecycle policy*.
+
+[role="screenshot"]
+image::images/index_management_add_policy.png[][UI for adding a policy to an index]
+
+
diff --git a/docs/management/index-lifecycle-policies/create-policy.asciidoc b/docs/management/index-lifecycle-policies/create-policy.asciidoc
@@ -0,0 +1,57 @@
+[[creating-index-lifecycle-policies]]
+=== Creating an index lifecycle policy
+
+An index lifecycle policy enables you to define rules over when to perform 
+certain actions, such as a rollover or force merge, on an index. Index lifecycle 
+management automates execution of those actions at the right time.
+
+When you create an index lifecycle policy, consider the tradeoffs between 
+performance and availability. As you move your index through the lifecycle, 
+you’re likely moving your data to less performant hardware and reducing the 
+number of shards and replicas.  It’s important to ensure that the index 
+continues to have enough replicas to prevent data loss in the event of failures.
+
+*Index Lifecycle Policies* is automatically enabled in {kib}. Go to 
+*Management > {es} > Index Lifecycle Policies*. 
+
+NOTE: If you don’t want to use this feature, you can disable it by setting 
+`xpack.ilm.enabled` to false in your `kibana.yml` configuration file. If you 
+disable *Index Management*, then *Index Lifecycle Policies* is also disabled.
+
+[role="screenshot"]
+image::images/index-lifecycle-policies-create.png[][UI for creating an index lifecycle policy]
+
+You can define up to four phases in the index lifecycle. For each phase, you 
+can enable actions to optimize performance for that phase. Transitioning 
+between phases is based on the age of the index.
+
+The four phases of an index lifecycle policy are:
+
+* *Hot.* The index is actively being queried and written to. You can optionally 
+roll over to a new index when the 
+original index reaches a specified size or age.  When a rollover occurs, a new 
+index is created, added to the index alias, and designated as the new “hot” 
+index. You can still query the previous indices, but you only ever write to 
+the “hot” index. See {ref}/indices-rollover-index.html[Rollover index] for more information.
+
+* *Warm.* The index is typically searched at a lower rate than when the data is 
+hot. The index is not used for storing for new data, but might occasionally add 
+late-arriving data, for example, from a Beat that had a network problem that's now fixed.  
+You can optionally shrink the number replicas and move the shards to a 
+different set of nodes with smaller or less performant hardware. You can also 
+reduce the number of primary shards and force merge the index into 
+smaller {ref}/indices-segments.html[segments].
+
+* *Cold.* The index is no longer being updated and is seldom queried, but is 
+still searchable. If you have a big deployment, you can move it to even 
+less performant hardware. You might also reduce the number of replicas because 
+you expect the data to be queried less frequently.
+
+* *Delete.* The index is no longer relevant. You can define when it is safe to 
+delete it.
+
+The index lifecycle always includes an active hot phase. The warm, cold, and 
+delete phases are optional. For example, you might define all four phases for 
+one policy and only a hot and delete phase for another.  See {ref}/_actions.html[Actions]
+for more information on the actions available in each phase. 
+
diff --git a/docs/management/index-lifecycle-policies/example-index-lifecycle-policy.asciidoc b/docs/management/index-lifecycle-policies/example-index-lifecycle-policy.asciidoc
@@ -0,0 +1,22 @@
+[[example-using-index-lifecycle-policy]]
+=== Example of using an index lifecycle policy
+
+A common use case for managing index lifecycle policies is when you’re using 
+{beats-ref}/beats-reference.html[Beats] to continually send time-series data, 
+such as metrics and log data, to {es}.  When you create the Beats packages, an 
+index template is installed.  The template includes a default policy to apply 
+when new indices are created.  
+
+You can edit the policy in {kib}'s *Index Lifecycle Policies*.  For example, you might:
+
+* Rollover the index when it reaches 50 GB in size or is 30 days old.  These 
+settings are the default for the Beats lifecycle policy. This avoids 
+having 1000s of tiny indices. When a rollover occurs, a new “hot” index is 
+created and added to the index alias.
+
+* Move the index into the warm phase, shrink the index down to a single shard, 
+and force merge to a single segment.
+
+* After 60 days, move the index into the cold phase and onto less expensive hardware.
+
+* Delete the index after 90 days.
diff --git a/docs/management/index-lifecycle-policies/intro-to-lifecycle-policies.asciidoc b/docs/management/index-lifecycle-policies/intro-to-lifecycle-policies.asciidoc
@@ -0,0 +1,29 @@
+[[index-lifecycle-policies]]
+== Index lifecycle policies
+
+If you're working with time series data, you don't want to continually dump 
+everything into a single index. Instead, you might periodically roll over the 
+data to a new index to keep it from growing so big it's slow and expensive. 
+As the index ages and you query it less frequently, you’ll likely move it to 
+less expensive hardware and reduce the number of shards and replicas.
+
+To automatically move an index through its lifecycle, you can create a policy 
+to define actions to perform on the index as it ages. Index lifecycle policies 
+are especially useful when working with {beats-ref}/beats-reference.html[Beats] 
+data shippers, which continually 
+send operational data, such as metrics and logs, to Elasticsearch. You can 
+automate a rollover to a new index when the existing index reaches a specified 
+size or age.  This ensures that all indices have a similar size instead of having 
+daily indices where size can vary based on the number of Beats and the number 
+of events sent.
+
+{kib}’s *Index Lifecycle Policies* walks you through the process for creating 
+and configuring a policy. Before using this feature, you should be familiar 
+with index lifecycle management:
+
+* For an introduction, see 
+{ref}/getting-started-index-lifecycle-management.html[Getting started with index 
+lifecycle management].  
+* To dig into the concepts and technical details, see 
+{ref}/index-lifecycle-management.html[Managing the index lifecycle].
+* To check out the APIs, see {ref}/index-lifecycle-management-api.html[Index lifecycle management API].
diff --git a/docs/management/index-lifecycle-policies/manage-policy.asciidoc b/docs/management/index-lifecycle-policies/manage-policy.asciidoc
@@ -0,0 +1,27 @@
+[[managing-index-lifecycle-policies]]
+=== Managing index lifecycle policies
+
+Your configured policies appear on the *Index lifecycle policies* page. 
+You can update an existing index lifecycle policy to fix errors or change 
+strategies for newly created indices. To edit a policy, select its name. 
+
+[role="screenshot"]
+image::images/index_lifecycle_policies_options.png[][UI for viewing and editing an index lifecycle policy]
+
+In addition, you can:
+
+* *View indices linked to the policy.* This is important when editing a policy. 
+Any changes you make affect all indices attached to the policy.  The settings 
+for the current phase are cached, so the update doesn’t affect that phase. This 
+prevents conflicts when you’re modifying a phase that is currently executing on 
+an index. The changes takes effect when the next phase in the index lifecycle begins.  
+
+* *Add the policy to an index template.*  When an index is automatically 
+created using the index template, the policy is applied. If the index is rolled 
+over, the policies for any matching index templates are applied to the newly 
+created index. For more information, see {ref}/indices-templates.html[Index templates].   
+
+* *Delete a policy.* You can’t delete a policy that is currently in use or 
+recover a deleted index.
+
+
diff --git a/docs/migration/migrate_7_0.asciidoc b/docs/migration/migrate_7_0.asciidoc
@@ -103,3 +103,16 @@ The port is now protocol dependent: https ports will use 443, and http ports wil
 `server.ssl.supportedProtocols`
 
 *Impact:* Users relying upon TLSv1 will be unable to use Kibana unless `server.ssl.supportedProtocols` is explicitly set.
+
+[float]
+=== kibana.yml setting `server.ssl.cert` is no longer valid
+*Details:* This deprecated setting has been removed and `server.ssl.certificate` should be used instead.
+
+*Impact:* Users with `server.ssl.cert` set should use `server.ssl.certificate` instead
+
+[float]
+=== kibana.yml `server.ssl.enabled` must be set to `true` to enable SSL
+*Details:* Previously, if `server.ssl.certificate` and `server.ssl.key` were set, SSL would automatically be enabled. 
+It's now required that the user sets `server.ssl.enabled` to true for this to occur.
+
+*Impact:* Users with both `server.ssl.certificate` and `server.ssl.key` set must now also set `server.ssl.enabled` to enable SSL.
diff --git a/docs/ml/images/ml-annotations-list.jpg b/docs/ml/images/ml-annotations-list.jpg
diff --git a/docs/ml/images/ml-calendar-management.jpg b/docs/ml/images/ml-calendar-management.jpg
diff --git a/docs/ml/images/ml-create-job.jpg b/docs/ml/images/ml-create-job.jpg
diff --git a/docs/ml/images/ml-data-visualizer-sample.jpg b/docs/ml/images/ml-data-visualizer-sample.jpg
diff --git a/docs/ml/images/ml-job-management.jpg b/docs/ml/images/ml-job-management.jpg
diff --git a/docs/ml/images/ml-settings.jpg b/docs/ml/images/ml-settings.jpg
diff --git a/docs/ml/images/ml-single-metric-viewer.jpg b/docs/ml/images/ml-single-metric-viewer.jpg
diff --git a/docs/ml/index.asciidoc b/docs/ml/index.asciidoc
@@ -46,6 +46,16 @@ The *Anomaly Explorer* and *Single Metric Viewer* display the results of your
 [role="screenshot"]
 image::ml/images/ml-single-metric-viewer.jpg[Single Metric Viewer]
 
+You can optionally add annotations by drag-selecting a period of time in
+the *Single Metric Viewer* and adding a description. For example, you can add an
+explanation for anomalies in that time period or provide notes about what is
+occurring in your operational environment at that time:
+
+[role="screenshot"]
+image::ml/images/ml-annotations-list.jpg[Single Metric Viewer with annotations]
+
+The *Job Management* pane shows the full list of annotations for each job.
+
 NOTE: The {kib} {ml-features} use pop-ups. You must configure your
 web browser so that it does not block pop-up windows or create an exception for
 your {kib} URL.

diff --git a/docs/visualize/time-series-visual-builder.asciidoc b/docs/visualize/time-series-visual-builder.asciidoc
@@ -1,8 +1,6 @@
 [[time-series-visual-builder]]
 == Time Series Visual Builder
 
-*Experimental Feature*
-
 Time Series Visual Builder is a time series data visualizer with an emphasis
 on allowing you to use the full power of Elasticsearch aggregation framework.
 Time Series Visual Builder allows you to combine an infinite number of

diff --git a/package.json b/package.json
@@ -95,7 +95,7 @@
   },
   "dependencies": {
     "@elastic/datemath": "5.0.2",
-    "@elastic/eui": "6.0.1",
+    "@elastic/eui": "6.3.1",
     "@elastic/filesaver": "1.1.2",
     "@elastic/good": "8.1.1-kibana2",
     "@elastic/numeral": "2.3.2",

diff --git a/packages/kbn-es/src/install/snapshot.js b/packages/kbn-es/src/install/snapshot.js
@@ -45,7 +45,7 @@ exports.downloadSnapshot = async function installSnapshot({
   log = defaultLog,
 }) {
   const fileName = getFilename(license, version);
-  const url = `https://snapshots.elastic.co/downloads/elasticsearch/${fileName}`;
+  const url = getUrl(fileName);
   const dest = path.resolve(basePath, 'cache', fileName);
 
   log.info('version: %s', chalk.bold(version));
@@ -150,3 +150,13 @@ function getFilename(license, version) {
 
   return `${basename}-SNAPSHOT.${extension}`;
 }
+
+function getUrl(fileName) {
+  if (process.env.TEST_ES_SNAPSHOT_VERSION) {
+    return `https://snapshots.elastic.co/${
+      process.env.TEST_ES_SNAPSHOT_VERSION
+    }/downloads/elasticsearch/${fileName}`;
+  } else {
+    return `https://snapshots.elastic.co/downloads/elasticsearch/${fileName}`;
+  }
+}
diff --git a/...reter/src/plugin/functions/common/clog.js → ...eter/src/plugin/functions/browser/clog.js b/...reter/src/plugin/functions/common/clog.js → ...eter/src/plugin/functions/browser/clog.js
diff --git a/...eter/src/plugin/functions/common/index.js → ...ter/src/plugin/functions/browser/index.js b/...eter/src/plugin/functions/common/index.js → ...ter/src/plugin/functions/browser/index.js
@@ -19,6 +19,6 @@
 
 import { clog } from './clog';
 
-export const commonFunctions = [
+export const browserFunctions = [
   clog,
 ];
diff --git a/packages/kbn-interpreter/src/plugin/functions/browser/register.js b/packages/kbn-interpreter/src/plugin/functions/browser/register.js
@@ -17,4 +17,7 @@
  * under the License.
  */
 
-import '../common/register';
+import { browserFunctions } from './index';
+
+// eslint-disable-next-line no-undef
+browserFunctions.forEach(canvas.register);
diff --git a/packages/kbn-interpreter/src/plugin/functions/common/register.js b/packages/kbn-interpreter/src/plugin/functions/common/register.js
@@ -17,7 +17,4 @@
  * under the License.
  */
 
-import { commonFunctions } from './index';
-
-// eslint-disable-next-line no-undef
-commonFunctions.forEach(canvas.register);
+import '../common/register';
diff --git a/packages/kbn-ui-framework/dist/ui_framework.css b/packages/kbn-ui-framework/dist/ui_framework.css
@@ -2944,8 +2944,7 @@ main {
   /* 1 */
   padding: 10px;
   height: 40px;
-  background-color: #ffffff;
-  border: 1px solid #D3DAE6; }
+  background-color: #ffffff; }
 
 .kuiToolBarFooterSection {
   display: -webkit-box;

diff --git a/src/core/public/chrome/chrome_service.ts b/src/core/public/chrome/chrome_service.ts
@@ -37,6 +37,7 @@ export interface Brand {
 export interface Breadcrumb {
   text: string;
   href?: string;
+  'data-test-subj'?: string;
 }
 
 export class ChromeService {