Server Code

    will start the server with Node’s inspect flag. Kibana’s development mode will start three processes on ports 9229, 9230, and 9231. Chrome’s developer tools need to be configured to connect to all three connections. Add for each Kibana process in Chrome’s developer tools connection tab.

    Instrumenting with Elastic APM

    Kibana ships with the built-in for debugging purposes.

    To change the location where data is sent, use the serverUrl APM config option. To activate the APM agent, use the APM config option.

    All config options can be set either via environment variables, or by creating an appropriate config file under config/apm.dev.js. For more information about configuring the APM agent, please refer to the documentation.

    APM is not available in the Kibana distributables, however the agent can be enabled by setting ELASTIC_APM_ACTIVE to true. flags

    1. ELASTIC_APM_ACTIVE=true yarn start

    Once the agent is active, it will trace all incoming HTTP requests to Kibana, monitor for errors, and collect process-level metrics. The collected data will be sent to the APM Server and is viewable in the APM UI in Kibana.