# Trying to configure Marvel on monitored node gets "Illegal User Settings"

**URL:** https://discuss.elastic.co/t/trying-to-configure-marvel-on-monitored-node-gets-illegal-user-settings/70703
**Category:** Elasticsearch
**Tags:** elastic-stack-monitoring
**Created:** [January 5, 2017, 3:51pm UTC](https://discuss.elastic.co/t/trying-to-configure-marvel-on-monitored-node-gets-illegal-user-settings/70703 "2017-01-05T15:51:12Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![DonL](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/donl/32/12308_2.png) [@DonL](https://discuss.elastic.co/u/DonL)
#### Post date: [January 5, 2017, 3:51pm UTC](https://discuss.elastic.co/t/trying-to-configure-marvel-on-monitored-node-gets-illegal-user-settings/70703/1 "2017-01-05T15:51:12Z")

</div>

I am attempting to follow the documentation to get marvel monitoring set up for my 2.4 cluster. The doc ([https://www.elastic.co/guide/en/shield/current/marvel.html](https://www.elastic.co/guide/en/shield/current/marvel.html)) says to input this in the YAML config:

```auto
marvel.agent.exporters:
  id1:
    type: http
    host: ["http://myhost"]
    auth:
      username: agent-user
      password: password

```

I put in the actual host name, and the agent-user and password that I set up on the separate monitoring node. When I select Update I get the message "Illegal User Setting".

Any suggestions on how to get past this?

---

<div class="post-metadata">

### Author: ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)
#### Post date: [January 5, 2017, 4:59pm UTC](https://discuss.elastic.co/t/trying-to-configure-marvel-on-monitored-node-gets-illegal-user-settings/70703/2 "2017-01-05T16:59:34Z")

</div>

Hi Don,

> When I select Update I get the message "Illegal User Setting".

When you selected update where? On Elastic Cloud?

---

<div class="post-metadata">

### Author: ![DonL](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/donl/32/12308_2.png) [@DonL](https://discuss.elastic.co/u/DonL)
#### Post date: [January 5, 2017, 5:15pm UTC](https://discuss.elastic.co/t/trying-to-configure-marvel-on-monitored-node-gets-illegal-user-settings/70703/3 "2017-01-05T17:15:58Z")

</div>

Yes. I am on Elastic Cloud.

And now that I have my Kibana straightened out, It appears that you don't have to do this step in the documentation, as I seem to be able to see information in Marvel.

---

<div class="post-metadata">

### Author: ![DonL](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/donl/32/12308_2.png) [@DonL](https://discuss.elastic.co/u/DonL)
#### Post date: [January 5, 2017, 5:23pm UTC](https://discuss.elastic.co/t/trying-to-configure-marvel-on-monitored-node-gets-illegal-user-settings/70703/4 "2017-01-05T17:23:50Z")

</div>

So we can close this one out.

---

<div class="post-metadata">

### Author: ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)
#### Post date: [January 5, 2017, 6:04pm UTC](https://discuss.elastic.co/t/trying-to-configure-marvel-on-monitored-node-gets-illegal-user-settings/70703/5 "2017-01-05T18:04:55Z")

</div>

Hi Don,

Yeah, Elastic Cloud automatically configures a lot of things that normal Elasticsearch / Kibana users must do themselves.

Glad that it worked out! I hope that you can upgrade to ES 5.x soon too.

Thanks,  
Chris

---

<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: [February 2, 2017, 6:05pm UTC](https://discuss.elastic.co/t/trying-to-configure-marvel-on-monitored-node-gets-illegal-user-settings/70703/6 "2017-02-02T18:05:16Z")

</div>

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