mirror of https://github.com/empayre/fleet.git synced 2024-11-06 08:55:24 +00:00

History

Martin Angers 792d76e2cd Fix stack trace, duplicates and better coverage of captured errors in APM (#16516 )		2024-02-05 11:53:39 -05:00
..
.apm-server.yml	Fix stack trace, duplicates and better coverage of captured errors in APM (#16516 )	2024-02-05 11:53:39 -05:00
docker-compose.yml	Fix stack trace, duplicates and better coverage of captured errors in APM (#16516 )	2024-02-05 11:53:39 -05:00
README.md	Fix stack trace, duplicates and better coverage of captured errors in APM (#16516 )	2024-02-05 11:53:39 -05:00

README.md

Running a local Elastic/Kibana APM

Setup

To setup a full Elastic APM stack, from this directory, run:

$ docker-compose up -d
$ docker-compose exec apm-server ./apm-server setup

Give it a few seconds to complete setup, and then you should be able to view the APM website at http://localhost:5601.

Configuring local Fleet

Make sure Fleet is ready to run locally (docker services are started, binary is built, etc., see Testing and local development).

Start the locally-built Fleet (fleet serve) and provide the --logging_tracing_enabled --logging_tracing_type=elasticapm flags (note that sending those options using environment variables does not seem to work).

Navigate the Fleet website and you should start seeing API requests and (eventually) errors show up in the APM dashboard (http://localhost:5601/app/apm).

You may set the following environment variables to further configure the APM data collection:

ELASTIC_APM_SERVICE_NAME=fleet
ELASTIC_APM_ENVIRONMENT=development
ELASTIC_APM_TRANSACTION_SAMPLE_RATE=1

The default values should be fine for a local environment (in particular, the sample rate defaults to 1.0 so all events are recorded).