# APM Agent remote configuration error

**URL:** <https://discuss.elastic.co/t/apm-agent-remote-configuration-error/231545>\
**Category:** APM\
**Tags:** ui\
**Created:** [May 7, 2020, 1:15pm UTC](https://discuss.elastic.co/t/apm-agent-remote-configuration-error/231545 "2020-05-07T13:15:41Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexandros888](https://avatars.discourse-cdn.com/v4/letter/a/3ec8ea/32.png) [@Alexandros888](https://discuss.elastic.co/u/Alexandros888)\
**Post date:** [May 7, 2020, 1:15pm UTC](https://discuss.elastic.co/t/apm-agent-remote-configuration-error/231545/1 "2020-05-07T13:15:41Z")

</div>

Hello,

I have APM version 7.6.2  
APM succesfully brings me the log info in kibana as the image show below;

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/c/3c4471c494588e9c7014c6da4410509647f140e3.png)

Nevertheless, I receive the following error when navigating in APM settings in kibana

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/b/cb484754eb0ac288ceca6af455fbade485e85269.png)

The critical parts of my APM yml file are as follows:

```
  kibana:
    # For APM Agent configuration in Kibana, enabled must be true.
    enabled: true

    # Scheme and port can be left out and will be set to the default (`http` and `5601`).
    # In case you specify an additional path, the scheme is required: `http://localhost:5601/path`.
    # IPv6 addresses should always be defined as: `https://[2001:db8::1]:5601`.
    host: "http://sag-tst-es-001.sag.services:5601"

    # Optional protocol and basic auth credentials.
    #protocol: "https"
    username: "myuser"
    password: "myuser"

    # Optional HTTP path.
    #path: ""

    # Enable custom SSL settings. Set to false to ignore custom SSL settings for secure communication.
    #ssl.enabled: true

    # Optional SSL configuration options. SSL is off by default, change the `protocol` option if you want to enable `https`.
    # Configure SSL verification mode. If `none` is configured, all server hosts
    # and certificates will be accepted. In this mode, SSL based connections are
    # susceptible to man-in-the-middle attacks. Use only for testing. Default is
    # `full`.
    #ssl.verification_mode: full

    # List of supported/valid TLS versions. By default all TLS versions 1.0 up to
    # 1.2 are enabled.
    #ssl.supported_protocols: [TLSv1.0, TLSv1.1, TLSv1.2]

    # List of root certificates for HTTPS server verifications.
    #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

    # Certificate for SSL client authentication.
    #ssl.certificate: "/etc/pki/client/cert.pem"

    # Client Certificate Key
    #ssl.key: "/etc/pki/client/cert.key"

    # Optional passphrase for decrypting the Certificate Key.
    # It is recommended to use the provided keystore instead of entering the passphrase in plain text.
    #ssl.key_passphrase: ''

    # Configure cipher suites to be used for SSL connections.
    #ssl.cipher_suites: []

    # Configure curve types for ECDHE based cipher suites.
    #ssl.curve_types: []

#================================= General =================================

# Data is buffered in a memory queue before it is published to the configured output.
# The memory queue will present all available events (up to the outputs
# bulk_max_size) to the output, the moment the output is ready to serve
# another batch of events.
queue:
  # Queue type by name (default 'mem').
  mem:
    # Max number of events the queue can buffer.
    events: 12288

    # Hints the minimum number of events stored in the queue,
    # before providing a batch of events to the outputs.
    # The default value is set to 2048.
    # A value of 0 ensures events are immediately available
    # to be sent to the outputs.
    #flush.min_events: 2048

    # Maximum duration after which events are available to the outputs,
    # if the number of events stored in the queue is < `flush.min_events`.
    #flush.timeout: 1s

# Sets the maximum number of CPUs that can be executing simultaneously. The
# default is the number of logical CPUs available in the system.
#max_procs:

#-------------------------- Elasticsearch output --------------------------
output.elasticsearch:
  # Array of hosts to connect to.
  # Scheme and port can be left out and will be set to the default (`http` and `9200`).
  # In case you specify and additional path, the scheme is required: `http://localhost:9200/path`.
  # IPv6 addresses should always be defined as: `https://[2001:db8::1]:9200`.
  hosts: ["sag-tst-es-001.sag.services:9200", "sag-tst-es-002.sag.services:9200"]

  # Boolean flag to enable or disable the output module.
  #enabled: true

  # Set gzip compression level.
  #compression_level: 0

  # Optional protocol and basic auth credentials.
  #protocol: "https"
  username: "myuser"
  password: "myuser"

  # Dictionary of HTTP parameters to pass within the url with index operations.
  #parameters:
    #param1: value1
    #param2: value2

  # Number of workers per Elasticsearch host.
  worker: 2

#============================= X-pack Monitoring =============================

# APM server can export internal metrics to a central Elasticsearch monitoring
# cluster. This requires x-pack monitoring to be enabled in Elasticsearch. The
# reporting is disabled by default.

# Set to true to enable the monitoring reporter.
monitoring.enabled: true

# Most settings from the Elasticsearch output are accepted here as well.
# Note that these settings should be configured to point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration. This means that if you have the Elasticsearch output configured,
# you can simply uncomment the following line.
monitoring.elasticsearch:

  # Optional protocol and basic auth credentials.
  #protocol: "https"
  #username: "apm_system"
  #password: "apm_system"

  # Array of hosts to connect to.
  # Scheme and port can be left out and will be set to the default (`http` and `9200`).
  # In case you specify and additional path, the scheme is required: `http://localhost:9200/path`.
  # IPv6 addresses should always be defined as: `https://[2001:db8::1]:9200`.
  #hosts: ["localhost:9200"]#============================= X-pack Monitoring =============================

# APM server can export internal metrics to a central Elasticsearch monitoring
# cluster. This requires x-pack monitoring to be enabled in Elasticsearch. The
# reporting is disabled by default.

# Set to true to enable the monitoring reporter.
monitoring.enabled: true

# Most settings from the Elasticsearch output are accepted here as well.
# Note that these settings should be configured to point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration. This means that if you have the Elasticsearch output configured,
# you can simply uncomment the following line.
monitoring.elasticsearch:

  # Optional protocol and basic auth credentials.
  #protocol: "https"
  #username: "apm_system"
  #password: "apm_system"

  # Array of hosts to connect to.
  # Scheme and port can be left out and will be set to the default (`http` and `9200`).
  # In case you specify and additional path, the scheme is required: `http://localhost:9200/path`.
  # IPv6 addresses should always be defined as: `https://[2001:db8::1]:9200`.
  #hosts: ["localhost:9200"]

```

Also to add that the user named: myuser that i use in the previous yml file has superuser rights and me as a user when i navigate in kibana i have superuser rights.

What i need to change in order to fix the issue?

---

<div class="post-metadata">

**Author:** ![Alexandros888](https://avatars.discourse-cdn.com/v4/letter/a/3ec8ea/32.png) [@Alexandros888](https://discuss.elastic.co/u/Alexandros888)\
**Post date:** [May 11, 2020, 2:51pm UTC](https://discuss.elastic.co/t/apm-agent-remote-configuration-error/231545/2 "2020-05-11T14:51:51Z")

</div>

Any help on that one please?

---

<div class="post-metadata">

**Author:** ![Oliver\_Gupte](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oliver_gupte/32/41850_2.png) [@Oliver\_Gupte](https://discuss.elastic.co/u/Oliver_Gupte)\
**Post date:** [May 11, 2020, 7:00pm UTC](https://discuss.elastic.co/t/apm-agent-remote-configuration-error/231545/3 "2020-05-11T19:00:48Z")

</div>

Hello, can you check if you have the `.apm-agent-configuration` index created:

With curl, you should get a 200 response from:  
`curl -XGET "<ElasticsearchHost>/.apm-agent-configuration"`

or you can go to the Index Managemet in Kibana and search for it (turn on "Include system indices"):

 ![Screen Shot 2020-05-11 at 11.51.36 AM](https://us1.discourse-cdn.com/elastic/original/3X/a/8/a83b716259e12db0e61855b145204b55da4bbaae.png)

If either of those doesn't return with an index, then there might be some issue with the automatic creation of that index.

---

<div class="post-metadata">

**Author:** ![Alexandros888](https://avatars.discourse-cdn.com/v4/letter/a/3ec8ea/32.png) [@Alexandros888](https://discuss.elastic.co/u/Alexandros888)\
**Post date:** [May 11, 2020, 9:12pm UTC](https://discuss.elastic.co/t/apm-agent-remote-configuration-error/231545/4 "2020-05-11T21:12:17Z")

</div>

Hello Oliver,

You are absolutely right the index does not exist. So what do you suggest to do now?

Thank you in advance

---

<div class="post-metadata">

**Author:** ![Oliver\_Gupte](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oliver_gupte/32/41850_2.png) [@Oliver\_Gupte](https://discuss.elastic.co/u/Oliver_Gupte)\
**Post date:** [May 11, 2020, 11:40pm UTC](https://discuss.elastic.co/t/apm-agent-remote-configuration-error/231545/5 "2020-05-11T23:40:55Z")

</div>

Restart Kibana and take a look at the log when it starts up. Look for an error like `Could not create APM Agent configuration: <specific error message>`. This should give us an idea if there is a permissions or validation issue when creating the new index. If we can't figure it out from there, the last resort is to manual create this index with:

```auto
curl -XPUT "https://<ElasticsearchHost>:9200/.apm-agent-configuration" -H 'Content-Type: application/json' -d'{"settings":{"index":{"auto_expand_replicas":"0-1"}},"mappings":{"properties":{"@timestamp":{"type":"date"},"service":{"properties":{"name":{"type":"keyword","ignore_above":1024},"environment":{"type":"keyword","ignore_above":1024}}},"settings":{"properties":{"transaction_sample_rate":{"type":"scaled_float","scaling_factor":1000,"ignore_malformed":true,"coerce":false},"capture_body":{"type":"keyword","ignore_above":1024},"transaction_max_spans":{"type":"short"}}},"applied_by_agent":{"type":"boolean"},"agent_name":{"type":"keyword","ignore_above":1024},"etag":{"type":"keyword","ignore_above":1024}}}}'

```

---

<div class="post-metadata">

**Author:** ![Alexandros888](https://avatars.discourse-cdn.com/v4/letter/a/3ec8ea/32.png) [@Alexandros888](https://discuss.elastic.co/u/Alexandros888)\
**Post date:** [May 12, 2020, 7:03am UTC](https://discuss.elastic.co/t/apm-agent-remote-configuration-error/231545/6 "2020-05-12T07:03:15Z")

</div>

Hello Oliver,

Thank you very much i restarted kibana and that was the solution!!!!!.  
Do you possibly know why it didnt create the index at the first place and i had to restart kibana in order to create it?

---

<div class="post-metadata">

**Author:** ![Oliver\_Gupte](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oliver_gupte/32/41850_2.png) [@Oliver\_Gupte](https://discuss.elastic.co/u/Oliver_Gupte)\
**Post date:** [May 12, 2020, 9:07am UTC](https://discuss.elastic.co/t/apm-agent-remote-configuration-error/231545/7 "2020-05-12T09:07:47Z")

</div>

I'm not totally sure why the index wasn't created in the first place. Some migration work was just completed with respect to how the APM plugin initializes within Kibana, and I don't anticipate this being an issue in future releases. I'm glad it's working on your end. Cheers! -Oliver

---

<div class="post-metadata">

**Author:** ![Alexandros888](https://avatars.discourse-cdn.com/v4/letter/a/3ec8ea/32.png) [@Alexandros888](https://discuss.elastic.co/u/Alexandros888)\
**Post date:** [May 12, 2020, 9:57am UTC](https://discuss.elastic.co/t/apm-agent-remote-configuration-error/231545/8 "2020-05-12T09:57:27Z")

</div>

Thank you very much Oliver. 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 9, 2020, 9:57am UTC](https://discuss.elastic.co/t/apm-agent-remote-configuration-error/231545/9 "2020-06-09T09:57:31Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.