### Author:  [@tomx1](https://discuss.elastic.co/u/tomx1)
#### Post date: [February 25, 2020, 12:13pm UTC](https://discuss.elastic.co/t/upgrade-to-7-6-stack-monitoring-only-with-security-enabled-possible/220848/1 "2020-02-25T12:13:23Z")
Hey,
since upgrading our cluster to 7.6.0 I'm facing the problem, that it is not possible anymore to use the "Stack Monitoring" App in Kibana. The following error message appears:
```
{
"type": "error",
"@timestamp": "2020-02-25T12:02:44Z",
"tags": [
"error",
"monitoring"
],
"pid": 6,
"level": "error",
"error": {
"message": "[invalid_index_name_exception] Invalid index name [_security], must not start with _, -, or +, with { index_uuid=\"_na_\" & index=\"_security\" }",
"name": "Error",
"stack": "Error: [invalid_index_name_exception] Invalid index name [_security], must not start with _, -, or +, with { index_uuid=\"_na_\" & index=\"_security\" }\n at respond (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:349:15)\n at checkRespForFailure (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:306:7)\n at HttpConnector. (/usr/share/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:173:7)\n at IncomingMessage.wrapper (/usr/share/kibana/node_modules/elasticsearch/node_modules/lodash/lodash.js:4929:19)\n at IncomingMessage.emit (events.js:203:15)\n at endReadableNT (_stream_readable.js:1143:12)\n at process._tickCallback (internal/process/next_tick.js:63:19)"
},
"message": "[invalid_index_name_exception] Invalid index name [_security], must not start with _, -, or +, with { index_uuid=\"_na_\" & index=\"_security\" }"
}
```
I'm collecting monitoring data from our 10 node production cluster nodes with metricbeat and we push it to a standalone single node "cluster" which has no xpack security enabled. Our 10 node production cluster _is_ using xpack security.
After upgrading everything to 7.6.0 it seems that enabling xpack security on the monitoring node is mandatory, but I did not find any hint about that in the release notes?
However, if I enable security at the monitoring node and create a user which exists at the production AND monitoring cluster, the Stack Monitoring App in Kibana is working again?
---
### Author:  [@joshdover](https://discuss.elastic.co/u/joshdover)
#### Post date: [February 25, 2020, 8:14pm UTC](https://discuss.elastic.co/t/upgrade-to-7-6-stack-monitoring-only-with-security-enabled-possible/220848/2 "2020-02-25T20:14:40Z")
Hi there!
Just a few questions for you to help me figure out what is going on here:
- Just to confirm your setup:
- 10 node production cluster w/ security + monitoring enabled (send to separate cluster)
- 1 node monitoring cluster w/ no security
- The error message you are getting, you receive that in the production cluster?
Can you try setting these settings in your kibana.yml? I suspect we may have a bug similar to [this one](https://github.com/elastic/kibana/issues/48824) where we are not merging configurations correctly.
```auto
xpack.monitoring.elasticsearch.username: null
xpack.monitoring.elasticsearch.password: null
```
---
### Author:  [@tomx1](https://discuss.elastic.co/u/tomx1)
#### Post date: [February 26, 2020, 11:53am UTC](https://discuss.elastic.co/t/upgrade-to-7-6-stack-monitoring-only-with-security-enabled-possible/220848/3 "2020-02-26T11:53:15Z")
> 10 node production cluster w/ security + monitoring enabled (send to separate cluster)
Correct. Monitoring stats were collected via a dedicated metricbeat instance and pushed to the monitoring cluster
> 1 node monitoring cluster w/ no security
Yes.
> The error message you are getting, you receive that in the production cluster?
The error message is generated by kibana which is logging to syslog
> Can you try setting these settings in your kibana.yml? I suspect we may have a bug similar to [this one](https://github.com/elastic/kibana/issues/48824) where we are not merging configurations correctly.
I've tried that, unfortunately without success. I'm receiving the same error message as above. I may have to mention that the hole setup is running under docker swarm, maybe that makes a difference for 7.6?
So to describe the Docker setup in short.
_5 baremetal server each running:_
- 1 Docker Elasticsearch Hot Node (SSD Storage)
- 1 Docker Elasticsearch Warm Node (SAS Storage)
- 1 Docker Metricbeat Instance collecting monitoring data from hot and warm nodes and pushes it to monitoring cluster
_Somewhere inside the Docker Swarm cluster the following containers are running (replicated mode):_
- 1 Docker Kibana instance
- 1 Docker Metricbeat instance collect Kibana monitoring stats
_1 Virtual Machine (Part of Swarm Cluster and running on separate hardware):_
- 1 Docker Elasticsearch Monitoring Cluster
---
### Author:  [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [February 26, 2020, 6:01pm UTC](https://discuss.elastic.co/t/upgrade-to-7-6-stack-monitoring-only-with-security-enabled-possible/220848/4 "2020-02-26T18:01:21Z")
Hi @tomx1,
This is a known issue: [https://github.com/elastic/kibana/issues/53129](https://github.com/elastic/kibana/issues/53129)
We have a fix in the works now: [https://github.com/elastic/kibana/pull/53306](https://github.com/elastic/kibana/pull/53306)
---
### Author:  [@tomx1](https://discuss.elastic.co/u/tomx1)
#### Post date: [February 27, 2020, 8:26am UTC](https://discuss.elastic.co/t/upgrade-to-7-6-stack-monitoring-only-with-security-enabled-possible/220848/5 "2020-02-27T08:26:51Z")
Are you sure that we are talking about the same issue here? I'm not talking about "how to setup Stack Monitoring", it's about that Stack Monitoring is not working if xpack.security.enabled is set to true on the monitoring node.
Here are two screenshots...
1.) xpack.security.enabled = true on Monitoring Node
2.) xpack.security.enabled = false on Monitoring Node
---
### Author:  [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [February 27, 2020, 4:00pm UTC](https://discuss.elastic.co/t/upgrade-to-7-6-stack-monitoring-only-with-security-enabled-possible/220848/6 "2020-02-27T16:00:52Z")
@tomx1
You are correct, my mistake. I'm looking into this more now.
---
### Author:  [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [February 27, 2020, 5:22pm UTC](https://discuss.elastic.co/t/upgrade-to-7-6-stack-monitoring-only-with-security-enabled-possible/220848/7 "2020-02-27T17:22:46Z")
It's a new issue and I filed a bug here: [https://github.com/elastic/kibana/issues/58750](https://github.com/elastic/kibana/issues/58750)
Thanks for reporting!
---
### Author:  [@tomx1](https://discuss.elastic.co/u/tomx1)
#### Post date: [March 2, 2020, 8:13am UTC](https://discuss.elastic.co/t/upgrade-to-7-6-stack-monitoring-only-with-security-enabled-possible/220848/8 "2020-03-02T08:13:06Z")
Thanks Chris!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 30, 2020, 8:13am UTC](https://discuss.elastic.co/t/upgrade-to-7-6-stack-monitoring-only-with-security-enabled-possible/220848/9 "2020-03-30T08:13:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.