Skip to content

Commit

Permalink
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'feature/ingest-node-pipelines' of github.com:elastic/ki…
Browse files Browse the repository at this point in the history
…bana into ingest-node-pipelines/privileges

* 'feature/ingest-node-pipelines' of github.com:elastic/kibana: (126 commits)
  [SEARCH] Cleanup fetch soon (elastic#63320)
  skip flaky suite (elastic#58692)
  [Uptime] Refresh index and also show more info to user regardi… (elastic#62606)
  [Drilldowns] Fix back button by removing panels from url in dashboard in view mode (elastic#62415)
  [platform] serve plugins from /bundles/plugin:${id}
  [Alerting] Documentation for how to pre-configure connectors. (elastic#63807)
  skip flaky suite (elastic#63621)
  Revert "skip flaky suite (elastic#63747)"
  skip flaky suite (elastic#63747)
  [SIEM][Detections Engine] - Update rule.lists to be rule.exceptions_list (elastic#63717)
  [SIEM] Flaky test fix: Bump find_statuses timeout (elastic#63900)
  [Uptime] Add cert API request and runtime type checking (elastic#63062)
  [Lens] Allow table to scroll horizontally (elastic#63805)
  [Metrics UI] Allow users to create alerts from the central Alerts UI (elastic#63803)
  Migrate legacy maps licensing (x-pack/tilemap) to NP (elastic#63539)
  [Alerting] "Create alert" and alert list design improvements (elastic#63515)
  [Lens] Fix existence for dotted paths in _source (elastic#63752)
  Example plugins in X-Pack (elastic#63823)
  [ML] Migrate Mocha unit tests to Jest: migrate job utils and query utils tests (elastic#63775)
  Endpoint: middleware receive immutable versions of state and actions (elastic#63802)
  ...
jloleysens committed Apr 20, 2020

Verified

This commit was signed with the committer’s verified signature.
jloleysens Jean-Louis Leysens
2 parents 9532955 + 8d18877 commit 0c9eee7
Showing 3,107 changed files with 38,188 additions and 61,668 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
4 changes: 2 additions & 2 deletions .eslintignore
Original file line number Diff line number Diff line change
@@ -9,14 +9,14 @@ bower_components
/built_assets
/html_docs
/src/plugins/data/common/es_query/kuery/ast/_generated_/**
/src/legacy/core_plugins/vis_type_timelion/public/_generated_/**
/src/plugins/vis_type_timelion/public/_generated_/**
src/legacy/core_plugins/vis_type_vislib/public/vislib/__tests__/lib/fixtures/mock_data
/src/legacy/ui/public/flot-charts
/test/fixtures/scenarios
/src/legacy/core_plugins/console/public/webpackShims
/src/legacy/core_plugins/console/public/tests/webpackShims
/src/legacy/ui/public/utils/decode_geo_hash.js
/src/legacy/core_plugins/vis_type_timelion/public/webpackShims/jquery.flot.*
/src/plugins/vis_type_timelion/public/webpackShims/jquery.flot.*
/src/core/lib/kbn_internal_native_observable
/packages/*/target
/packages/eslint-config-kibana
16 changes: 11 additions & 5 deletions .eslintrc.js
Original file line number Diff line number Diff line change
@@ -109,7 +109,7 @@ module.exports = {
},
},
{
files: ['x-pack/legacy/plugins/lens/**/*.{js,ts,tsx}'],
files: ['x-pack/plugins/lens/**/*.{js,ts,tsx}'],
rules: {
'react-hooks/exhaustive-deps': 'off',
'react-hooks/rules-of-hooks': 'off',
@@ -536,9 +536,15 @@ module.exports = {
* ML overrides
*/
{
files: ['x-pack/legacy/plugins/ml/**/*.js'],
files: ['x-pack/plugins/ml/**/*.js'],
rules: {
'no-shadow': 'error',
'import/no-extraneous-dependencies': [
'error',
{
packageDir: './x-pack',
},
],
},
},

@@ -561,7 +567,7 @@ module.exports = {
},
{
// typescript only for front and back end
files: ['x-pack/legacy/plugins/siem/**/*.{ts,tsx}'],
files: ['x-pack/{,legacy/}plugins/siem/**/*.{ts,tsx}'],
rules: {
// This will be turned on after bug fixes are complete
// '@typescript-eslint/explicit-member-accessibility': 'warn',
@@ -607,7 +613,7 @@ module.exports = {
// },
{
// typescript and javascript for front and back end
files: ['x-pack/legacy/plugins/siem/**/*.{js,ts,tsx}'],
files: ['x-pack/{,legacy/}plugins/siem/**/*.{js,ts,tsx}'],
plugins: ['eslint-plugin-node', 'react'],
env: {
mocha: true,
@@ -728,7 +734,7 @@ module.exports = {
* Lens overrides
*/
{
files: ['x-pack/legacy/plugins/lens/**/*.{ts,tsx}', 'x-pack/plugins/lens/**/*.{ts,tsx}'],
files: ['x-pack/plugins/lens/**/*.{ts,tsx}'],
rules: {
'@typescript-eslint/no-explicit-any': 'error',
},
26 changes: 18 additions & 8 deletions .github/CODEOWNERS
This CODEOWNERS file contains errors

CODEOWNERS errors

  • Unknown owner on line 6: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/lens/ @elastic/kibana-app
  • Unknown owner on line 7: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/graph/ @elastic/kibana-app
  • Unknown owner on line 8: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …legacy/server/url_shortening/ @elastic/kibana-app
  • Unknown owner on line 9: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …rc/legacy/server/sample_data/ @elastic/kibana-app
  • Unknown owner on line 10: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …gins/kibana/public/dashboard/ @elastic/kibana-app
  • Unknown owner on line 11: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …ugins/kibana/public/discover/ @elastic/kibana-app
  • Unknown owner on line 12: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …ic/local_application_service/ @elastic/kibana-app
  • Unknown owner on line 13: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …gins/kibana/public/dev_tools/ @elastic/kibana-app
  • Unknown owner on line 14: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …core_plugins/vis_type_vislib/ @elastic/kibana-app
  • Unknown owner on line 15: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /src/plugins/vis_type_xy/ @elastic/kibana-app
  • Unknown owner on line 16: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /src/plugins/kibana_legacy/ @elastic/kibana-app
  • Unknown owner on line 17: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …rc/plugins/vis_type_timelion/ @elastic/kibana-app
  • Unknown owner on line 18: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /src/plugins/dashboard/ @elastic/kibana-app
  • Unknown owner on line 19: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /src/plugins/discover/ @elastic/kibana-app
  • Unknown owner on line 20: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /src/plugins/visualize/ @elastic/kibana-app
  • Unknown owner on line 21: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …/plugins/vis_type_timeseries/ @elastic/kibana-app
  • Unknown owner on line 22: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /src/plugins/vis_type_metric/ @elastic/kibana-app
  • Unknown owner on line 23: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …rc/plugins/vis_type_markdown/ @elastic/kibana-app
  • Unknown owner on line 27: make sure the team @elastic/kibana-core-ui exists, is publicly visible, and has write access to the repository
    /src/plugins/home/public @elastic/kibana-core-ui
  • Unknown owner on line 28: make sure the team @elastic/kibana-core-ui exists, is publicly visible, and has write access to the repository
    /src/plugins/home/server/*.ts @elastic/kibana-core-ui
  • Unknown owner on line 29: make sure the team @elastic/kibana-core-ui exists, is publicly visible, and has write access to the repository
    …plugins/home/server/services/ @elastic/kibana-core-ui
  • Unknown owner on line 31: make sure the team @elastic/kibana-core-ui exists, is publicly visible, and has write access to the repository
    …ugins/kibana/public/home/*.ts @elastic/kibana-core-ui
  • Unknown owner on line 32: make sure the team @elastic/kibana-core-ui exists, is publicly visible, and has write access to the repository
    …ins/kibana/public/home/*.scss @elastic/kibana-core-ui
  • Unknown owner on line 33: make sure the team @elastic/kibana-core-ui exists, is publicly visible, and has write access to the repository
    …/kibana/public/home/np_ready/ @elastic/kibana-core-ui
  • Unknown owner on line 36: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …ples/url_generators_examples/ @elastic/kibana-app-arch
  • Unknown owner on line 37: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …ples/url_generators_explorer/ @elastic/kibana-app-arch
  • Unknown owner on line 38: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /packages/kbn-interpreter/ @elastic/kibana-app-arch
  • Unknown owner on line 39: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …/core_plugins/embeddable_api/ @elastic/kibana-app-arch
  • Unknown owner on line 40: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …acy/core_plugins/interpreter/ @elastic/kibana-app-arch
  • Unknown owner on line 41: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …cy/core_plugins/kibana_react/ @elastic/kibana-app-arch
  • Unknown owner on line 42: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …ins/kibana/public/management/ @elastic/kibana-app-arch
  • Unknown owner on line 43: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …server/routes/api/management/ @elastic/kibana-app-arch
  • Unknown owner on line 44: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …/core_plugins/visualizations/ @elastic/kibana-app-arch
  • Unknown owner on line 45: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …legacy/server/index_patterns/ @elastic/kibana-app-arch
  • Unknown owner on line 46: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …rc/plugins/advanced_settings/ @elastic/kibana-app-arch
  • Unknown owner on line 47: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/bfetch/ @elastic/kibana-app-arch
  • Unknown owner on line 48: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/data/ @elastic/kibana-app-arch
  • Unknown owner on line 49: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/embeddable/ @elastic/kibana-app-arch
  • Unknown owner on line 50: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/expressions/ @elastic/kibana-app-arch
  • Unknown owner on line 51: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/inspector/ @elastic/kibana-app-arch
  • Unknown owner on line 52: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/kibana_react/ @elastic/kibana-app-arch
  • Unknown owner on line 53: make sure the team @elastic/kibana-canvas exists, is publicly visible, and has write access to the repository
    …bana_react/public/code_editor @elastic/kibana-canvas
  • Unknown owner on line 54: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/kibana_utils/ @elastic/kibana-app-arch
  • Unknown owner on line 55: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/management/ @elastic/kibana-app-arch
  • Unknown owner on line 56: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/navigation/ @elastic/kibana-app-arch
  • Unknown owner on line 57: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/share/ @elastic/kibana-app-arch
  • Unknown owner on line 58: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/ui_actions/ @elastic/kibana-app-arch
  • Unknown owner on line 59: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/visualizations/ @elastic/kibana-app-arch
  • Unknown owner on line 60: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …/plugins/advanced_ui_actions/ @elastic/kibana-app-arch
  • Unknown owner on line 61: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …x-pack/plugins/data_enhanced/ @elastic/kibana-app-arch
  • Unknown owner on line 62: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/drilldowns/ @elastic/kibana-app-arch
  • Unknown owner on line 65: make sure the team @elastic/apm-ui exists, is publicly visible, and has write access to the repository
    /x-pack/legacy/plugins/apm/  @elastic/apm-ui
  • Unknown owner on line 66: make sure the team @elastic/apm-ui exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/apm/  @elastic/apm-ui
  • Unknown owner on line 67: make sure the team @elastic/apm-ui exists, is publicly visible, and has write access to the repository
    …ck/test/functional/apps/apm/  @elastic/apm-ui
  • Unknown owner on line 68: make sure the team @elastic/apm-ui exists, is publicly visible, and has write access to the repository
    …legacy/core_plugins/apm_oss/  @elastic/apm-ui
  • Unknown owner on line 69: make sure the team @elastic/apm-ui exists, is publicly visible, and has write access to the repository
    /src/plugins/apm_oss/  @elastic/apm-ui
  • Unknown owner on line 70: make sure @watson exists and has write access to the repository
    /src/apm.js @watson
  • Unknown owner on line 73: make sure the team @elastic/beats exists, is publicly visible, and has write access to the repository
    …cy/plugins/beats_management/  @elastic/beats
  • Unknown owner on line 76: make sure the team @elastic/kibana-canvas exists, is publicly visible, and has write access to the repository
    …-pack/legacy/plugins/canvas/  @elastic/kibana-canvas
  • Unknown owner on line 79: make sure the team @elastic/logs-metrics-ui exists, is publicly visible, and has write access to the repository
    /x-pack/legacy/plugins/infra/ @elastic/logs-metrics-ui
  • Unknown owner on line 80: make sure the team @elastic/logs-metrics-ui exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/infra/ @elastic/logs-metrics-ui
  • Unknown owner on line 81: make sure the team @elastic/ingest-management exists, is publicly visible, and has write access to the repository
    …-pack/plugins/ingest_manager/ @elastic/ingest-management
  • Unknown owner on line 82: make sure the team @elastic/ingest-management exists, is publicly visible, and has write access to the repository
    …egacy/plugins/ingest_manager/ @elastic/ingest-management
  • Unknown owner on line 83: make sure the team @elastic/uptime exists, is publicly visible, and has write access to the repository
    …gs-metrics-ui @elastic/apm-ui @elastic/uptime @elastic/ingest-management
  • Unknown owner on line 83: make sure the team @elastic/logs-metrics-ui exists, is publicly visible, and has write access to the repository
    …x-pack/plugins/observability/ @elastic/logs-metrics-ui @elastic/apm-ui @elastic/uptime @elastic/ingest-management
  • Unknown owner on line 83: make sure the team @elastic/apm-ui exists, is publicly visible, and has write access to the repository
    …ity/ @elastic/logs-metrics-ui @elastic/apm-ui @elastic/uptime @elastic/ingest-management
  • Unknown owner on line 83: make sure the team @elastic/ingest-management exists, is publicly visible, and has write access to the repository
    …lastic/apm-ui @elastic/uptime @elastic/ingest-management
  • Unknown owner on line 84: make sure the team @elastic/stack-monitoring-ui exists, is publicly visible, and has write access to the repository
    …ck/legacy/plugins/monitoring/ @elastic/stack-monitoring-ui
  • Unknown owner on line 85: make sure the team @elastic/uptime exists, is publicly visible, and has write access to the repository
    /x-pack/legacy/plugins/uptime @elastic/uptime
  • Unknown owner on line 86: make sure the team @elastic/uptime exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/uptime @elastic/uptime
  • Unknown owner on line 89: make sure the team @elastic/ml-ui exists, is publicly visible, and has write access to the repository
    /x-pack/legacy/plugins/ml/  @elastic/ml-ui
  • Unknown owner on line 90: make sure the team @elastic/ml-ui exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/ml/  @elastic/ml-ui
  • Unknown owner on line 91: make sure the team @elastic/ml-ui exists, is publicly visible, and has write access to the repository
    …ional/apps/machine_learning/  @elastic/ml-ui
  • Unknown owner on line 92: make sure the team @elastic/ml-ui exists, is publicly visible, and has write access to the repository
    …l/services/machine_learning/  @elastic/ml-ui
  • Unknown owner on line 93: make sure the team @elastic/ml-ui exists, is publicly visible, and has write access to the repository
    …st/functional/services/ml.ts  @elastic/ml-ui
  • Unknown owner on line 95: make sure the team @elastic/ml-ui exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/transform/  @elastic/ml-ui
  • Unknown owner on line 96: make sure the team @elastic/ml-ui exists, is publicly visible, and has write access to the repository
    …st/functional/apps/transform/ @elastic/ml-ui
  • Unknown owner on line 97: make sure the team @elastic/ml-ui exists, is publicly visible, and has write access to the repository
    …tional/services/transform_ui/ @elastic/ml-ui
  • Unknown owner on line 98: make sure the team @elastic/ml-ui exists, is publicly visible, and has write access to the repository
    …ctional/services/transform.ts @elastic/ml-ui
  • Unknown owner on line 101: make sure the team @elastic/kibana-gis exists, is publicly visible, and has write access to the repository
    /x-pack/legacy/plugins/maps/ @elastic/kibana-gis
  • Unknown owner on line 102: make sure the team @elastic/kibana-gis exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/maps/ @elastic/kibana-gis
  • Unknown owner on line 103: make sure the team @elastic/kibana-gis exists, is publicly visible, and has write access to the repository
    …st/api_integration/apis/maps/ @elastic/kibana-gis
  • Unknown owner on line 104: make sure the team @elastic/kibana-gis exists, is publicly visible, and has write access to the repository
    …ck/test/functional/apps/maps/ @elastic/kibana-gis
  • Unknown owner on line 105: make sure the team @elastic/kibana-gis exists, is publicly visible, and has write access to the repository
    …/functional/es_archives/maps/ @elastic/kibana-gis
  • Unknown owner on line 106: make sure the team @elastic/kibana-gis exists, is publicly visible, and has write access to the repository
    …egression/tests/maps/index.js @elastic/kibana-gis
  • Unknown owner on line 109: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /src/dev/ @elastic/kibana-operations
  • Unknown owner on line 110: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /src/setup_node_env/ @elastic/kibana-operations
  • Unknown owner on line 111: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /src/optimize/ @elastic/kibana-operations
  • Unknown owner on line 112: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /src/es_archiver/ @elastic/kibana-operations
  • Unknown owner on line 113: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /packages/*eslint*/ @elastic/kibana-operations
  • Unknown owner on line 114: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /packages/*babel*/ @elastic/kibana-operations
  • Unknown owner on line 115: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /packages/kbn-dev-utils*/ @elastic/kibana-operations
  • Unknown owner on line 116: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /packages/kbn-es/ @elastic/kibana-operations
  • Unknown owner on line 117: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /packages/kbn-optimizer/ @elastic/kibana-operations
  • Unknown owner on line 118: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /packages/kbn-pm/ @elastic/kibana-operations
  • Unknown owner on line 119: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /packages/kbn-test/ @elastic/kibana-operations
  • Unknown owner on line 120: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /packages/kbn-ui-shared-deps/ @elastic/kibana-operations
  • Unknown owner on line 121: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /src/legacy/server/keystore/ @elastic/kibana-operations
  • Unknown owner on line 122: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /src/legacy/server/pid/ @elastic/kibana-operations
  • Unknown owner on line 123: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /src/legacy/server/sass/ @elastic/kibana-operations
  • Unknown owner on line 124: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /src/legacy/server/utils/ @elastic/kibana-operations
  • Unknown owner on line 125: make sure the team @elastic/kibana-operations exists, is publicly visible, and has write access to the repository
    /src/legacy/server/warnings/ @elastic/kibana-operations
  • Unknown owner on line 128: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /src/core/  @elastic/kibana-platform
  • Unknown owner on line 129: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /config/kibana.yml @elastic/kibana-platform
  • Unknown owner on line 130: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/features/  @elastic/kibana-platform
  • Unknown owner on line 131: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/licensing/  @elastic/kibana-platform
  • Unknown owner on line 132: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /packages/kbn-config-schema/ @elastic/kibana-platform
  • Unknown owner on line 133: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /src/legacy/server/config/ @elastic/kibana-platform
  • Unknown owner on line 134: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /src/legacy/server/http/ @elastic/kibana-platform
  • Unknown owner on line 135: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /src/legacy/server/logging/ @elastic/kibana-platform
  • Unknown owner on line 136: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    …legacy/server/saved_objects/  @elastic/kibana-platform
  • Unknown owner on line 137: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /src/legacy/server/status/ @elastic/kibana-platform
  • Unknown owner on line 138: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /src/plugins/status_page/ @elastic/kibana-platform
  • Unknown owner on line 139: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    …ins/saved_objects_management/ @elastic/kibana-platform
  • Unknown owner on line 140: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    …heck_published_api_changes.ts @elastic/kibana-platform
  • Unknown owner on line 143: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    …sp/  @elastic/kibana-security @elastic/kibana-platform
  • Unknown owner on line 143: make sure the team @elastic/kibana-security exists, is publicly visible, and has write access to the repository
    /src/core/server/csp/  @elastic/kibana-security @elastic/kibana-platform
  • Unknown owner on line 144: make sure the team @elastic/kibana-security exists, is publicly visible, and has write access to the repository
    …ack/legacy/plugins/security/  @elastic/kibana-security
  • Unknown owner on line 145: make sure the team @elastic/kibana-security exists, is publicly visible, and has write access to the repository
    …-pack/legacy/plugins/spaces/  @elastic/kibana-security
  • Unknown owner on line 146: make sure the team @elastic/kibana-security exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/spaces/  @elastic/kibana-security
  • Unknown owner on line 147: make sure the team @elastic/kibana-security exists, is publicly visible, and has write access to the repository
    …ins/encrypted_saved_objects/  @elastic/kibana-security
  • Unknown owner on line 148: make sure the team @elastic/kibana-security exists, is publicly visible, and has write access to the repository
    …ins/encrypted_saved_objects/  @elastic/kibana-security
  • Unknown owner on line 149: make sure the team @elastic/kibana-security exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/security/  @elastic/kibana-security
  • Unknown owner on line 150: make sure the team @elastic/kibana-security exists, is publicly visible, and has write access to the repository
    …pi_integration/apis/security/ @elastic/kibana-security
  • Unknown owner on line 153: make sure the team @elastic/kibana-localization exists, is publicly visible, and has write access to the repository
    /src/dev/i18n/  @elastic/kibana-localization
  • Unknown owner on line 154: make sure the team @elastic/kibana-localization exists, is publicly visible, and has write access to the repository
    /src/legacy/server/i18n/  @elastic/kibana-localization
  • Unknown owner on line 155: make sure the team @elastic/kibana-localization exists, is publicly visible, and has write access to the repository
    /src/core/public/i18n/  @elastic/kibana-localization
  • Unknown owner on line 156: make sure the team @elastic/kibana-localization exists, is publicly visible, and has write access to the repository
    /packages/kbn-i18n/  @elastic/kibana-localization
  • Unknown owner on line 159: make sure the team @elastic/pulse exists, is publicly visible, and has write access to the repository
    /packages/kbn-analytics/ @elastic/pulse
  • Unknown owner on line 160: make sure the team @elastic/pulse exists, is publicly visible, and has write access to the repository
    …egacy/core_plugins/ui_metric/ @elastic/pulse
  • Unknown owner on line 161: make sure the team @elastic/pulse exists, is publicly visible, and has write access to the repository
    /src/plugins/telemetry/ @elastic/pulse
  • Unknown owner on line 162: make sure the team @elastic/pulse exists, is publicly visible, and has write access to the repository
    …telemetry_collection_manager/ @elastic/pulse
  • Unknown owner on line 163: make sure the team @elastic/pulse exists, is publicly visible, and has write access to the repository
    …telemetry_management_section/ @elastic/pulse
  • Unknown owner on line 164: make sure the team @elastic/pulse exists, is publicly visible, and has write access to the repository
    …src/plugins/usage_collection/ @elastic/pulse
  • Unknown owner on line 165: make sure the team @elastic/pulse exists, is publicly visible, and has write access to the repository
    …s/telemetry_collection_xpack/ @elastic/pulse
  • Unknown owner on line 168: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …pack/legacy/plugins/alerting/ @elastic/kibana-alerting-services
  • Unknown owner on line 169: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …-pack/legacy/plugins/actions/ @elastic/kibana-alerting-services
  • Unknown owner on line 170: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/alerting/ @elastic/kibana-alerting-services
  • Unknown owner on line 171: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/actions/ @elastic/kibana-alerting-services
  • Unknown owner on line 172: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/event_log/ @elastic/kibana-alerting-services
  • Unknown owner on line 173: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/task_manager/ @elastic/kibana-alerting-services
  • Unknown owner on line 174: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …est/alerting_api_integration/ @elastic/kibana-alerting-services
  • Unknown owner on line 175: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …gration/plugins/task_manager/ @elastic/kibana-alerting-services
  • Unknown owner on line 176: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …ion/test_suites/task_manager/ @elastic/kibana-alerting-services
  • Unknown owner on line 177: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …/plugins/triggers_actions_ui/ @elastic/kibana-alerting-services
  • Unknown owner on line 178: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …/plugins/triggers_actions_ui/ @elastic/kibana-alerting-services
  • Unknown owner on line 179: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …ssl/apps/triggers_actions_ui/ @elastic/kibana-alerting-services
  • Unknown owner on line 180: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …_ssl/fixtures/plugins/alerts/ @elastic/kibana-alerting-services
  • Unknown owner on line 183: make sure the team @elastic/kibana-design exists, is publicly visible, and has write access to the repository
    **/*.scss  @elastic/kibana-design
  • Unknown owner on line 186: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    /src/plugins/dev_tools/ @elastic/es-ui
  • Unknown owner on line 187: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    /src/plugins/console/  @elastic/es-ui
  • Unknown owner on line 188: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    /src/plugins/es_ui_shared/  @elastic/es-ui
  • Unknown owner on line 189: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …s/cross_cluster_replication/  @elastic/es-ui
  • Unknown owner on line 190: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …/index_lifecycle_management/  @elastic/es-ui
  • Unknown owner on line 191: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …cy/plugins/index_management/  @elastic/es-ui
  • Unknown owner on line 192: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …/plugins/license_management/  @elastic/es-ui
  • Unknown owner on line 193: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …-pack/legacy/plugins/rollup/  @elastic/es-ui
  • Unknown owner on line 194: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …cy/plugins/snapshot_restore/  @elastic/es-ui
  • Unknown owner on line 195: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …y/plugins/upgrade_assistant/  @elastic/es-ui
  • Unknown owner on line 196: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …/plugins/console_extensions/  @elastic/es-ui
  • Unknown owner on line 197: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …x-pack/plugins/es_ui_shared/  @elastic/es-ui
  • Unknown owner on line 198: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …x-pack/plugins/grokdebugger/  @elastic/es-ui
  • Unknown owner on line 199: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …ck/plugins/index_management/  @elastic/es-ui
  • Unknown owner on line 200: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …/plugins/license_management/  @elastic/es-ui
  • Unknown owner on line 201: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …x-pack/plugins/painless_lab/  @elastic/es-ui
  • Unknown owner on line 202: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …ack/plugins/remote_clusters/  @elastic/es-ui
  • Unknown owner on line 203: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/rollup/  @elastic/es-ui
  • Unknown owner on line 204: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …pack/plugins/searchprofiler/  @elastic/es-ui
  • Unknown owner on line 205: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …ck/plugins/snapshot_restore/  @elastic/es-ui
  • Unknown owner on line 206: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …k/plugins/upgrade_assistant/  @elastic/es-ui
  • Unknown owner on line 207: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/watcher/  @elastic/es-ui
  • Unknown owner on line 208: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …ck/plugins/ingest_pipelines/  @elastic/es-ui
  • Unknown owner on line 211: make sure the team @elastic/endpoint-app-team exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/endpoint/ @elastic/endpoint-app-team
  • Unknown owner on line 212: make sure the team @elastic/endpoint-app-team exists, is publicly visible, and has write access to the repository
    …pi_integration/apis/endpoint/ @elastic/endpoint-app-team
  • Unknown owner on line 213: make sure the team @elastic/endpoint-app-team exists, is publicly visible, and has write access to the repository
    …nt_api_integration_no_ingest/ @elastic/endpoint-app-team
  • Unknown owner on line 214: make sure the team @elastic/endpoint-app-team exists, is publicly visible, and has write access to the repository
    …ack/test/functional_endpoint/ @elastic/endpoint-app-team
  • Unknown owner on line 215: make sure the team @elastic/endpoint-app-team exists, is publicly visible, and has write access to the repository
    …onal_endpoint_ingest_failure/ @elastic/endpoint-app-team
  • Unknown owner on line 216: make sure the team @elastic/endpoint-app-team exists, is publicly visible, and has write access to the repository
    …ctional/es_archives/endpoint/ @elastic/endpoint-app-team
  • Unknown owner on line 217: make sure the team @elastic/endpoint-app-team exists, is publicly visible, and has write access to the repository
    …tional/plugins/resolver_test/ @elastic/endpoint-app-team
  • Unknown owner on line 218: make sure the team @elastic/endpoint-app-team exists, is publicly visible, and has write access to the repository
    …ctional/test_suites/resolver/ @elastic/endpoint-app-team
  • Unknown owner on line 221: make sure the team @elastic/siem exists, is publicly visible, and has write access to the repository
    /x-pack/legacy/plugins/siem/ @elastic/siem
  • Unknown owner on line 222: make sure the team @elastic/siem exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/siem/ @elastic/siem
  • Unknown owner on line 223: make sure the team @elastic/siem exists, is publicly visible, and has write access to the repository
    …ection_engine_api_integration @elastic/siem
  • Unknown owner on line 224: make sure the team @elastic/siem exists, is publicly visible, and has write access to the repository
    …est/api_integration/apis/siem @elastic/siem
  • Unknown owner on line 225: make sure the team @elastic/siem exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/case @elastic/siem
  • Unknown owner on line 228: make sure the team @elastic/security-intelligence-analytics exists, is publicly visible, and has write access to the repository
    …ngine/rules/prepackaged_rules @elastic/security-intelligence-analytics
  • Unknown owner on line 229: make sure the team @elastic/security-intelligence-analytics exists, is publicly visible, and has write access to the repository
    …ngine/rules/prepackaged_rules @elastic/security-intelligence-analytics
Original file line number Diff line number Diff line change
@@ -3,22 +3,24 @@
# For more info, see https://help.github.com/articles/about-codeowners/

# App
/x-pack/legacy/plugins/lens/ @elastic/kibana-app
/x-pack/legacy/plugins/graph/ @elastic/kibana-app
/x-pack/plugins/lens/ @elastic/kibana-app
/x-pack/plugins/graph/ @elastic/kibana-app
/src/legacy/server/url_shortening/ @elastic/kibana-app
/src/legacy/server/sample_data/ @elastic/kibana-app
/src/legacy/core_plugins/kibana/public/dashboard/ @elastic/kibana-app
/src/legacy/core_plugins/kibana/public/discover/ @elastic/kibana-app
/src/legacy/core_plugins/kibana/public/visualize/ @elastic/kibana-app
/src/legacy/core_plugins/kibana/public/local_application_service/ @elastic/kibana-app
/src/legacy/core_plugins/kibana/public/dev_tools/ @elastic/kibana-app
/src/legacy/core_plugins/metrics/ @elastic/kibana-app
/src/legacy/core_plugins/vis_type_vislib/ @elastic/kibana-app
/src/legacy/core_plugins/vis_type_xy/ @elastic/kibana-app
/src/plugins/vis_type_xy/ @elastic/kibana-app
/src/plugins/kibana_legacy/ @elastic/kibana-app
/src/plugins/timelion/ @elastic/kibana-app
/src/plugins/vis_type_timelion/ @elastic/kibana-app
/src/plugins/dashboard/ @elastic/kibana-app
/src/plugins/discover/ @elastic/kibana-app
/src/plugins/visualize/ @elastic/kibana-app
/src/plugins/vis_type_timeseries/ @elastic/kibana-app
/src/plugins/vis_type_metric/ @elastic/kibana-app
/src/plugins/vis_type_markdown/ @elastic/kibana-app

# Core UI
# Exclude tutorials folder for now because they are not owned by Kibana app and most will move out soon
@@ -80,6 +82,8 @@
/x-pack/legacy/plugins/ingest_manager/ @elastic/ingest-management
/x-pack/plugins/observability/ @elastic/logs-metrics-ui @elastic/apm-ui @elastic/uptime @elastic/ingest-management
/x-pack/legacy/plugins/monitoring/ @elastic/stack-monitoring-ui
/x-pack/legacy/plugins/uptime @elastic/uptime
/x-pack/plugins/uptime @elastic/uptime

# Machine Learning
/x-pack/legacy/plugins/ml/ @elastic/ml-ui
@@ -95,6 +99,7 @@

# Maps
/x-pack/legacy/plugins/maps/ @elastic/kibana-gis
/x-pack/plugins/maps/ @elastic/kibana-gis
/x-pack/test/api_integration/apis/maps/ @elastic/kibana-gis
/x-pack/test/functional/apps/maps/ @elastic/kibana-gis
/x-pack/test/functional/es_archives/maps/ @elastic/kibana-gis
@@ -127,7 +132,6 @@
/packages/kbn-config-schema/ @elastic/kibana-platform
/src/legacy/server/config/ @elastic/kibana-platform
/src/legacy/server/http/ @elastic/kibana-platform
/src/legacy/server/i18n/ @elastic/kibana-platform
/src/legacy/server/logging/ @elastic/kibana-platform
/src/legacy/server/saved_objects/ @elastic/kibana-platform
/src/legacy/server/status/ @elastic/kibana-platform
@@ -146,7 +150,10 @@
/x-pack/test/api_integration/apis/security/ @elastic/kibana-security

# Kibana Localization
/src/dev/i18n/ @elastic/kibana-localization
/src/dev/i18n/ @elastic/kibana-localization
/src/legacy/server/i18n/ @elastic/kibana-localization
/src/core/public/i18n/ @elastic/kibana-localization
/packages/kbn-i18n/ @elastic/kibana-localization

# Pulse
/packages/kbn-analytics/ @elastic/pulse
@@ -203,9 +210,12 @@
# Endpoint
/x-pack/plugins/endpoint/ @elastic/endpoint-app-team
/x-pack/test/api_integration/apis/endpoint/ @elastic/endpoint-app-team
/x-pack/test/endpoint_api_integration_no_ingest/ @elastic/endpoint-app-team
/x-pack/test/functional_endpoint/ @elastic/endpoint-app-team
/x-pack/test/functional_endpoint_ingest_failure/ @elastic/endpoint-app-team
/x-pack/test/functional/es_archives/endpoint/ @elastic/endpoint-app-team
/x-pack/test/plugin_functional/plugins/resolver_test/ @elastic/endpoint-app-team
/x-pack/test/plugin_functional/test_suites/resolver/ @elastic/endpoint-app-team

# SIEM
/x-pack/legacy/plugins/siem/ @elastic/siem
3 changes: 3 additions & 0 deletions .github/paths-labeller.yml
Original file line number Diff line number Diff line change
@@ -8,3 +8,6 @@
- "Feature:ExpressionLanguage":
- "src/plugins/expressions/**/*.*"
- "src/plugins/bfetch/**/*.*"
- "Team:uptime":
- "x-pack/plugins/uptime/**/*.*"
- "x-pack/legacy/plugins/uptime/**/*.*"
9 changes: 5 additions & 4 deletions .i18nrc.json
Original file line number Diff line number Diff line change
@@ -43,18 +43,19 @@
"src/plugins/telemetry_management_section"
],
"tileMap": "src/legacy/core_plugins/tile_map",
"timelion": ["src/legacy/core_plugins/timelion", "src/legacy/core_plugins/vis_type_timelion", "src/plugins/timelion"],
"timelion": ["src/legacy/core_plugins/timelion", "src/plugins/vis_type_timelion"],
"uiActions": "src/plugins/ui_actions",
"visDefaultEditor": "src/plugins/vis_default_editor",
"visTypeMarkdown": "src/legacy/core_plugins/vis_type_markdown",
"visTypeMetric": "src/legacy/core_plugins/vis_type_metric",
"visTypeMarkdown": "src/plugins/vis_type_markdown",
"visTypeMetric": "src/plugins/vis_type_metric",
"visTypeTable": "src/legacy/core_plugins/vis_type_table",
"visTypeTagCloud": "src/legacy/core_plugins/vis_type_tagcloud",
"visTypeTimeseries": ["src/legacy/core_plugins/vis_type_timeseries", "src/plugins/vis_type_timeseries"],
"visTypeVega": "src/legacy/core_plugins/vis_type_vega",
"visTypeVislib": "src/legacy/core_plugins/vis_type_vislib",
"visTypeXy": "src/legacy/core_plugins/vis_type_xy",
"visualizations": "src/plugins/visualizations"
"visualizations": "src/plugins/visualizations",
"visualize": "src/plugins/visualize"
},
"exclude": [
"src/legacy/ui/ui_render/ui_render_mixin.js"
5 changes: 3 additions & 2 deletions .sass-lint.yml
Original file line number Diff line number Diff line change
@@ -8,10 +8,11 @@ files:
- 'x-pack/legacy/plugins/security/**/*.s+(a|c)ss'
- 'x-pack/legacy/plugins/canvas/**/*.s+(a|c)ss'
- 'x-pack/plugins/triggers_actions_ui/**/*.s+(a|c)ss'
- 'x-pack/plugins/lens/**/*.s+(a|c)ss'
- 'x-pack/legacy/plugins/maps/**/*.s+(a|c)ss'
- 'x-pack/plugins/maps/**/*.s+(a|c)ss'
ignore:
- 'x-pack/legacy/plugins/canvas/shareable_runtime/**/*.s+(a|c)ss'
- 'x-pack/legacy/plugins/lens/**/*.s+(a|c)ss'
- 'x-pack/legacy/plugins/maps/**/*.s+(a|c)ss'
rules:
quotes:
- 2
2 changes: 1 addition & 1 deletion Jenkinsfile
Original file line number Diff line number Diff line change
@@ -41,7 +41,7 @@ kibanaPipeline(timeoutMinutes: 135, checkPrChanges: true) {
'xpack-ciGroup10': kibanaPipeline.xpackCiGroupProcess(10),
'xpack-accessibility': kibanaPipeline.functionalTestProcess('xpack-accessibility', './test/scripts/jenkins_xpack_accessibility.sh'),
'xpack-siemCypress': { processNumber ->
whenChanged(['x-pack/legacy/plugins/siem/', 'x-pack/test/siem_cypress/']) {
whenChanged(['x-pack/plugins/siem/', 'x-pack/legacy/plugins/siem/', 'x-pack/test/siem_cypress/']) {
kibanaPipeline.functionalTestProcess('xpack-siemCypress', './test/scripts/jenkins_siem_cypress.sh')(processNumber)
}
},
4 changes: 2 additions & 2 deletions docs/api/saved-objects/create.asciidoc
Original file line number Diff line number Diff line change
@@ -57,12 +57,12 @@ any data that you send to the API is properly formed.

[source,sh]
--------------------------------------------------
$ curl -X POST "localhost:5601/api/saved_objects/index-pattern/my-pattern"
$ curl -X POST "localhost:5601/api/saved_objects/index-pattern/my-pattern" -H 'kbn-xsrf: true' -H 'Content-Type: application/json' -d '
{
"attributes": {
"title": "my-pattern-*"
}
}
}'
--------------------------------------------------
// KIBANA

16 changes: 8 additions & 8 deletions docs/api/saved-objects/export.asciidoc
Original file line number Diff line number Diff line change
@@ -68,46 +68,46 @@ Export all index pattern saved objects:

[source,sh]
--------------------------------------------------
$ curl -X POST "localhost:5601/api/saved_objects/_export"
$ curl -X POST "localhost:5601/api/saved_objects/_export" -H 'kbn-xsrf: true' -H 'Content-Type: application/json' -d '
{
"type": "index-pattern"
}
}'
--------------------------------------------------
// KIBANA

Export all index pattern saved objects and exclude the export summary from the stream:

[source,sh]
--------------------------------------------------
$ curl -X POST "localhost:5601/api/saved_objects/_export"
$ curl -X POST "localhost:5601/api/saved_objects/_export" -H 'kbn-xsrf: true' -H 'Content-Type: application/json' -d '
{
"type": "index-pattern",
"excludeExportDetails": true
}
}'
--------------------------------------------------
// KIBANA

Export a specific saved object:

[source,sh]
--------------------------------------------------
$ curl -X POST "localhost:5601/api/saved_objects/_export"
$ curl -X POST "localhost:5601/api/saved_objects/_export" -H 'kbn-xsrf: true' -H 'Content-Type: application/json' -d '
{
"objects": [
{
"type": "dashboard",
"id": "be3733a0-9efe-11e7-acb3-3dab96693fab"
}
]
}
}'
--------------------------------------------------
// KIBANA

Export a specific saved object and it's related objects :

[source,sh]
--------------------------------------------------
$ curl -X POST "localhost:5601/api/saved_objects/_export"
$ curl -X POST "localhost:5601/api/saved_objects/_export" -H 'kbn-xsrf: true' -H 'Content-Type: application/json' -d '
{
"objects": [
{
@@ -116,6 +116,6 @@ $ curl -X POST "localhost:5601/api/saved_objects/_export"
}
],
"includeReferencesDeep": true
}
}'
--------------------------------------------------
// KIBANA
30 changes: 18 additions & 12 deletions docs/apm/advanced-queries.asciidoc
Original file line number Diff line number Diff line change
@@ -1,14 +1,11 @@
[role="xpack"]
[[advanced-queries]]
=== Advanced queries
=== Query your data

When querying in the APM app, you're simply searching and selecting data from fields in Elasticsearch documents.
Queries entered into the query bar are also added as parameters to the URL,
so it's easy to share a specific query or view with others.

You can begin to see some of the transaction fields available for filtering:

[role="screenshot"]
image::apm/images/apm-query-bar.png[Example of the Kibana Query bar in APM app in Kibana]
Querying your APM data is a powerful tool that can make finding bottlenecks in your code even easier.
Imagine you have a user that complains about a slow response time in a specific service.
With the query bar, you can easily filter the APM app to only display trace data for that user,
or, to only show transactions that are slower than a specified time threshold.

[float]
==== Example APM app queries
@@ -17,23 +14,32 @@ image::apm/images/apm-query-bar.png[Example of the Kibana Query bar in APM app i
* Filter by response status code: `context.response.status_code >= 400`
* Filter by single user ID: `context.user.id : 12`

When querying in the APM app, you're merely searching and selecting data from fields in Elasticsearch documents.
Queries entered into the query bar are also added as parameters to the URL,
so it's easy to share a specific query or view with others.

When you type, you can begin to see some of the transaction fields available for filtering:

[role="screenshot"]
image::apm/images/apm-query-bar.png[Example of the Kibana Query bar in APM app in Kibana]

TIP: Read the {kibana-ref}/kuery-query.html[Kibana Query Language Enhancements] documentation to learn more about the capabilities of the {kib} query language.

[float]
[[discover-advanced-queries]]
=== Querying in Discover

It may also be helpful to view your APM data in {kibana-ref}/discover.html[*Discover*].
Alternatively, you can query your APM documents in {kibana-ref}/discover.html[*Discover*].
Querying documents in *Discover* works the same way as querying in the APM app,
and all of the example APM app queries can also be used in *Discover*.
and *Discover* supports all of the example APM app queries shown on this page.

[float]
==== Example Discover query

One example where you may want to make use of *Discover*,
is for viewing _all_ transactions for an endpoint, instead of just a sample.

TIP: Starting in v7.6, you can view 10 samples per bucket in the APM app, instead of just one.
TIP: Starting in v7.6, you can view ten samples per bucket in the APM app, instead of just one.

Use the APM app to find a transaction name and time bucket that you're interested in learning more about.
Then, switch to *Discover* and make a search:
27 changes: 15 additions & 12 deletions docs/apm/agent-configuration.asciidoc
Original file line number Diff line number Diff line change
@@ -1,42 +1,45 @@
[role="xpack"]
[[agent-configuration]]
=== APM Agent configuration
=== APM Agent central configuration

APM Agent configuration allows you to fine-tune your agent configuration directly in Kibana.
Best of all, changes are automatically propagated to your APM agents so there's no need to redeploy.
++++
<titleabbrev>Configure APM agents with central config</titleabbrev>
++++

To get started, simply choose the services and environments you wish to configure.
The APM app will let you know when your configurations have been applied by your agents.
APM Agent configuration allows you to fine-tune your agent configuration from within the APM app.
Changes are automatically propagated to your APM agents, so there's no need to redeploy.

To get started, choose the services and environments you wish to configure.
The APM app will let you know when your agents have applied your configurations.

[role="screenshot"]
image::apm/images/apm-agent-configuration.png[APM Agent configuration in Kibana]

[float]
==== Precedence

Configurations set with APM Agent configuration take precedence over configurations set locally in the Agent.
Configurations set from the APM app take precedence over configurations set locally in each Agent.
However, if APM Server is slow to respond, is offline, reports an error, etc.,
APM agents will use local defaults until they're able to update the configuration.
For this reason, it is still important to set custom default configurations locally in each of your agents.
For this reason, it is still essential to set custom default configurations locally in each of your agents.

[float]
==== APM Server setup

This feature requires {apm-server-ref}/setup-kibana-endpoint.html[Kibana endpoint configuration] in APM Server.

Why is additional configuration needed in APM Server?
That's because APM Server acts as a proxy between the agents and Kibana.
APM Server acts as a proxy between the agents and Kibana.
Kibana communicates any changed settings to APM Server so that your agents only need to poll APM Server to determine which settings have changed.

[float]
==== Supported configurations

Each Agent has its own list of supported configurations.
Each Agent has a list of supported configurations.
After selecting a Service name and environment in the APM app,
a list of all available configuration options,
a list of all supported configuration options,
including descriptions and default values, will be displayed.

Supported configurations are also marked in each Agent's configuration documentation:
Supported configurations are also tagged with the image:./images/dynamic-config.svg[] badge in each Agent's configuration reference:

[horizontal]
Go Agent:: {apm-go-ref}/configuration.html[Configuration reference]
Loading

0 comments on commit 0c9eee7

Please sign in to comment.