Configure the Kibana endpointedit

Here’s a sample configuration:

apm-server.kibana.enabled: true "http://localhost:5601"
Kibana endpoint configuration optionsedit

You can specify the following options in the apm-server.kibana section of the apm-server.yml config file. These options are not required for a Fleet-managed APM Server.


Defaults to false. Must be true to use APM Agent configuration.


The Kibana host that APM Server will communicate with. The default is The value of host can be a URL or IP:PORT. For example:, 192:15.3.2:5601 or If no port is specified, 5601 is used.

When a node is defined as an IP:PORT, the scheme and path are taken from the apm-server.kibana.protocol and apm-server.kibana.path config options.

IPv6 addresses must be defined using the following format: https://[2001:db8::1]:5601.


The name of the protocol Kibana is reachable on. The options are: http or https. The default is http. However, if you specify a URL for host, the value of protocol is overridden by whatever scheme you specify in the URL.

Example config: ""
apm-server.kibana.protocol: "http"
apm-server.kibana.path: /kibana

The basic authentication username for connecting to Kibana.


The basic authentication password for connecting to Kibana.


Authentication with an API key. Formatted as id:api_key


An HTTP path prefix that is prepended to the HTTP API calls. This is useful for the cases where Kibana listens behind an HTTP reverse proxy that exports the API under a custom prefix.


Enables APM Server to use SSL settings when connecting to Kibana via HTTPS. If you configure APM Server to connect over HTTPS, this setting defaults to true and APM Server uses the default SSL settings.

Example configuration: ""
apm-server.kibana.ssl.enabled: true
apm-server.kibana.ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
apm-server.kibana.ssl.certificate: "/etc/pki/client/cert.pem"
apm-server.kibana.ssl.key: "/etc/pki/client/cert.key"

For information on the additional SSL configuration options, see SSL/TLS output settings.