# Redirecting problems in Stack Monitoring after changing to Metricbeat

**URL:** <https://discuss.elastic.co/t/redirecting-problems-in-stack-monitoring-after-changing-to-metricbeat/249788>\
**Category:** Kibana\
**Tags:** elastic-stack-monitoring\
**Created:** [September 24, 2020, 9:36am UTC](https://discuss.elastic.co/t/redirecting-problems-in-stack-monitoring-after-changing-to-metricbeat/249788 "2020-09-24T09:36:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![peterol](https://avatars.discourse-cdn.com/v4/letter/p/6a8cbe/32.png) [@peterol](https://discuss.elastic.co/u/peterol)\
**Post date:** [September 24, 2020, 9:36am UTC](https://discuss.elastic.co/t/redirecting-problems-in-stack-monitoring-after-changing-to-metricbeat/249788/1 "2020-09-24T09:36:46Z")

</div>

Hello everyone!

I have a redirecting problem with the stack monitoring: Until now I used the internal method for collecting monitoring data of my cluster, which worked fine. Now I want to use Metricbeat to collect data, so I installed it on the Elasticsearch, Kibana and Logstash nodes, according to the documentation. So far everything works, indices and dashboards have been created and data is flowing into the cluster.

Now to my problem: When I click on "Stack Monitoring" in Kibana, the Dialog asking whether to set up monitoring with Metricbeat or internal collection shows up for about 1-2 Seconds until I get directed to an empty site:

 ![elastic_minitoring_after_start_no_setup](https://us1.discourse-cdn.com/elastic/original/3X/a/7/a7fd8839d9ab8f739d135f3b2a4fe9d18a347255.png)

If I'm fast enough to click on "Set up monitoring with Metricbeat" I get directed to the setup mode. After exiting setup mode the monitoring looks quite fine:

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

But the next time I click on "Stack Monitoring" the same happens again and I get an empty site. I also noticed that the URL on the empty site contains `/monitoring#/home?_g=` while after exiting the setup mode it is `/monitoring#/overview?_g=` Changing `home` to `overview` also calls the correct site.

My first thought were conflicting indices of internal and Metricbeat collection, but the problem still occurs after I deleted all old monitoring indices.

My monitoring settings in elasticsearch.yml:

```auto
xpack.monitoring.collection.enabled: true   
xpack.monitoring.elasticsearch.collection.enabled: false
xpack.monitoring.exporters.my_local.type: local

```

My monitoring settings in kibana.yml:

```auto
xpack.monitoring.enabled: true
xpack.monitoring.ui.enabled: true
xpack.monitoring.ui.container.elasticsearch.enabled: false
xpack.monitoring.ui.container.logstash.enabled: true
xpack.monitoring.ui.elasticsearch.username: "monitoring_internal"
xpack.monitoring.ui.elasticsearch.password: "..."
xpack.monitoring.kibana.collection.enabled: false

```

Any help would be great, thank you! 🙂

---

<div class="post-metadata">

**Author:** ![peterol](https://avatars.discourse-cdn.com/v4/letter/p/6a8cbe/32.png) [@peterol](https://discuss.elastic.co/u/peterol)\
**Post date:** [September 24, 2020, 10:45am UTC](https://discuss.elastic.co/t/redirecting-problems-in-stack-monitoring-after-changing-to-metricbeat/249788/2 "2020-09-24T10:45:31Z")

</div>

I found the solution, it was no redirecting problem, it was [this](https://github.com/elastic/kibana/issues/77130) issue. The upgrade to 7.9.1 and the change to Metricbeat just occurred at the same time.

---

<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:** [October 22, 2020, 10:45am UTC](https://discuss.elastic.co/t/redirecting-problems-in-stack-monitoring-after-changing-to-metricbeat/249788/3 "2020-10-22T10:45:38Z")

</div>

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