History

Cauê Marcondes 3b5bd02347 [APM] Fleet: Add secret_token to agent instructions in legacy Getting Started guide (#102669 ) * Register tutorial on APM plugin * using files from apm * removing tutorial from apm_oss * removing export * fixing i18n * adding fleet section * adding fleet information on APM tutorial * adding fleet typing * fixing i18n * adding fleet information on APM tutorial * checks apm fleet integration when pushing button * adding fleet information on APM tutorial * refactoring * registering status check callback * addin custom component registration function * fixing TS issue * addressing PR comments * fixing tests * adding i18n * fixing issues * adding environment credencials * refactoring * adjusting size * adding unit test * adding unit test * refactoring * addressing PR comments * refactoring eui component * adding unit test * fixing TS issue * fixing TS issue * adding help text * renaming * moving tutorial to a common directory * moving files * updating apm int version * adding storybook * adding storybook * refactoring * removing commented code * fixing unit tests * addressing PR comments * fixing lint errors * changing to url * addressing PR comments Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>		2021-06-29 08:55:30 -04:00
..
common	[Fleet] Add UI and mappings for agent policy unenroll_timeout (#102970 )	2021-06-23 14:46:04 -04:00
dev_docs	[Fleet] Move integrations to a separate app (#99848 )	2021-06-07 10:43:44 -04:00
public	Upgrade EUI to v34.5.1 (#103297 )	2021-06-28 11:31:23 -05:00
server	[APM] Fleet: Add secret_token to agent instructions in legacy Getting Started guide (#102669 )	2021-06-29 08:55:30 -04:00
CHANGELOG.md
jest.config.js
kibana.json	[Fleet] Add packages to global search results (#102227 )	2021-06-17 15:45:28 +02:00
package.json
README.md	[Fleet] Update docker image of registry used in integration tests (#101911 )	2021-06-17 14:55:17 -04:00
tsconfig.json

README.md

Fleet

Plugin

The plugin is enabled by default. See the TypeScript type for the the available plugin configuration options
Adding xpack.fleet.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.fleet.agents.enabled=false will disable the Fleet API & UI
- code for adding the routes
- Integration tests
Both EPM and Fleet require ingestManager be enabled. They are not standalone features.
For Enterprise license, a custom package registry URL can be used by setting xpack.fleet.registryUrl=http://localhost:8080
- This property is currently only for internal Elastic development and is unsupported

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.fleet.agents.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.fleet.agents.elasticsearch.host=http://localhost:9200
--xpack.fleet.agents.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.fleet.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.

Note: The plugin was previously named Ingest Manager it's possible that some variables are still named with that old plugin name.

Tests

API integration tests

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

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

FLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:server --config x-pack/test/fleet_api_integration/config.ts

in a second terminal, run the tests from the Kibana root directory with

FLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:runner --config x-pack/test/fleet_api_integration/config.ts

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

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

Note you can also supply which docker image to use for the package registry via the FLEET_PACKAGE_REGISTRY_DOCKER_IMAGE env variable. For example,

FLEET_PACKAGE_REGISTRY_DOCKER_IMAGE='docker.elastic.co/package-registry/distribution:production' FLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:runner