kibana/x-pack/plugins/ingest_manager
Catherine Liu 532f2d70e8
[Home] Elastic home page redesign (#70571)
Co-authored-by: Catherine Liu <catherine.liu@elastic.co>
Co-authored-by: Ryan Keairns <contactryank@gmail.com>
Co-authored-by: Catherine Liu <catherineqliu@outlook.com>
Co-authored-by: Michael Marcialis <michael.marcialis@elastic.co>
2020-08-26 13:00:00 -07:00
..
common [Ingest Manager] check for packages stuck installing and reinstall (#75226) 2020-08-24 09:42:39 -04:00
dev_docs Update datasets UI copy to data streams (#75618) 2020-08-21 09:16:17 -07:00
public [Home] Elastic home page redesign (#70571) 2020-08-26 13:00:00 -07:00
scripts [Ingest] Add Fleet & EPM features (#59376) 2020-03-12 18:52:06 -04:00
server [Home] Elastic home page redesign (#70571) 2020-08-26 13:00:00 -07:00
CHANGELOG.md [EPM] update epm filepath route (#61910) 2020-03-31 08:43:24 -04:00
kibana.json [Home] Elastic home page redesign (#70571) 2020-08-26 13:00:00 -07:00
package.json [Ingest Manager] Use long polling for agent checkin (#68922) 2020-06-18 14:42:27 -04:00
README.md [Ingest Manager] Rename agent/package config(s) to agent/package policy(ies) (#74914) 2020-08-19 13:52:06 -07:00
yarn.lock [Ingest Manager] Use long polling for agent checkin (#68922) 2020-06-18 14:42:27 -04:00

Ingest Manager

Plugin

  • The plugin is enabled by default. See the TypeScript type for the the available plugin configuration options
  • Adding xpack.ingestManager.enabled=false will disable the plugin including the EPM and Fleet features. It will also remove the PACKAGE_POLICY_API_ROUTES and AGENT_POLICY_API_ROUTES values in common/constants/routes.ts
  • Adding --xpack.ingestManager.fleet.enabled=false will disable the Fleet API & UI
  • Both EPM and Fleet require ingestManager be enabled. They are not standalone features.
  • For Gold+ license, a custom package registry URL can be used by setting xpack.ingestManager.registryUrl=http://localhost:8080

Fleet Requirements

Fleet needs to have Elasticsearch API keys enabled, and also to have TLS enabled on kibana, (if you want to run Kibana without TLS you can provide the following config flag --xpack.ingestManager.fleet.tlsCheckDisabled=false)

Also you need to configure the hosts your agent is going to use to comunication with Elasticsearch and Kibana (Not needed if you use Elastic cloud). You can use the following flags:

--xpack.ingestManager.fleet.elasticsearch.host=http://localhost:9200
--xpack.ingestManager.fleet.kibana.host=http://localhost:5601

Development

Getting started

See the Kibana docs for how to set up your dev environment, run Elasticsearch, and start Kibana

One common development workflow is:

  • Bootstrap Kibana
    yarn kbn bootstrap
    
  • Start Elasticsearch in one shell
    yarn es snapshot -E xpack.security.authc.api_key.enabled=true
    
  • Start Kibana in another shell
    yarn start --xpack.ingestManager.enabled=true --no-base-path
    

This plugin follows the common, server, public structure from the Architecture Style Guide . We also follow the pattern of developing feature branches under your personal fork of Kibana.

Tests

API integration tests

You need to have docker to run ingest manager api integration tests

  1. In one terminal, run the tests from the Kibana root directory with

    INGEST_MANAGEMENT_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:server --config x-pack/test/ingest_manager_api_integration/config.ts
    
  2. in a second terminal, run the tests from the Kibana root directory with

    INGEST_MANAGEMENT_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:runner --config x-pack/test/ingest_manager_api_integration/config.ts
    

    Optionally you can filter which tests you want to run using --grep

    INGEST_MANAGEMENT_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:runner --config x-pack/test/ingest_manager_api_integration/config.ts --grep='fleet'