Elasticsearch 中的 .reporting-* 和 .monitoring-* 索引是什么

发布于 2025-01-09 23:27:11 字数 1368 浏览 0 评论 0原文

我在我们的elasticsearch集群中看到一些索引(.reporting-*和.monitoring-*)如下,

green open .monitoring-kibana-7-2022.02.22 FPl-nNnAQE-8aawMEVWoaw 3 1    8640      0   4.2mb   2.1mb
green open .reporting-2020.11.15           4rS-SCGGGS-7YKg28FdyFw 1 1      30      1 323.2mb 161.6mb
green open .reporting-2021.05.09           7wnfwIsSe4rQC5hBFC3o2g 1 1      14      0 324.3mb 162.1mb
  1. 这些索引是什么以及它们是如何创建的?
  2. 我需要这些索引吗?我可以删除它们吗?
  3. 如何停止创建此类索引?

我检查过的一些参考文献是。

(对于 .monitoring- 索引):*

https://www.elastic.co/guide/en/x-pack/current/xpack-introduction.html

(用于 .reporting -索引):*

https:// www.elastic.co/guide/en/kibana/current/reporting-settings-kb.html

这就是我的 kibana.yml 的样子:

server.host: ffb-supply-kibana-server
elasticsearch.hosts: ["http://master-2:9200","http://master-3:9200","http://fdata-1:9200","http://data-2:9200","http://data-3:9200"]
kibana.index: ".kibana"
elasticsearch.username: "something"
elasticsearch.password: "something"
xpack.reporting.csv.maxSizeBytes: 52428800
logging.quiet: true```

I see some indexes (.reporting-* and .monitoring-*) as follows in our elasticsearch cluster,

green open .monitoring-kibana-7-2022.02.22 FPl-nNnAQE-8aawMEVWoaw 3 1    8640      0   4.2mb   2.1mb
green open .reporting-2020.11.15           4rS-SCGGGS-7YKg28FdyFw 1 1      30      1 323.2mb 161.6mb
green open .reporting-2021.05.09           7wnfwIsSe4rQC5hBFC3o2g 1 1      14      0 324.3mb 162.1mb
  1. What are these indexes and how do they get created?
  2. Do I need these indexes? Can I delete them?
  3. How do I stop the creation of such indexes?

Some of the references which I checked are.

(for .monitoring- indexes):*

https://www.elastic.co/guide/en/x-pack/current/xpack-introduction.html

(for .reporting- indexes):*

https://www.elastic.co/guide/en/kibana/current/reporting-settings-kb.html

This is what my kibana.yml looks like:

server.host: ffb-supply-kibana-server
elasticsearch.hosts: ["http://master-2:9200","http://master-3:9200","http://fdata-1:9200","http://data-2:9200","http://data-3:9200"]
kibana.index: ".kibana"
elasticsearch.username: "something"
elasticsearch.password: "something"
xpack.reporting.csv.maxSizeBytes: 52428800
logging.quiet: true```

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

谈场末日恋爱 2025-01-16 23:27:11

.monitoring-* 索引包含来自堆栈中任何组件的监控数据,受到监控。如果您不启用/设置监控,则不会创建这些索引。

.reporting* 索引包含 您在 Kibana 中设置的报告。如果您不使用这些报告功能,则不会创建索引。

你需要它们吗?如果你问它们是什么,很可能你并不真正需要它们。

你能删除它们吗?是的,但如果您不禁用监控,新的 .monitoring 索引将在 10 秒后再次出现。对于 .reporting* 也是如此,如果您或其他人在 Kibana 中运行报告,索引将再次重新创建。

正如前面提到的,要停止创建监控索引,您需要禁用监控(请参阅第一个链接),但这样做不一定是个好主意,因为您会盲目并且并不真正知道集群的运行情况。但是,将监控数据存储在与生产集群不同的集群中始终是一个好主意。

要停止创建报告索引,您只需停止创建报告即可。

The .monitoring-* indexes contain monitoring data from any component of the stack that is monitored. If you don't enable/setup the monitoring, then those indexes are not created.

The .reporting* indexes contain reports you've setup in Kibana. If you don't use those reporting features, the index doesn't get created.

Do you need them? Odds are that if you're asking what they are, you don't really need them.

Can you delete them? Yes, but if you don't disable monitoring, new .monitoring indexes are going to appear 10 seconds later again. Same for .reporting*, if you or someone else runs a report in Kibana, the index is going to recreated again.

As mentioned earlier, to stop the creation of monitoring indexes, you need to disable monitoring (see first link), but it's not necessarily a good idea to do so, because you'd be blind and not really know how your cluster is doing. However, it's always a good idea to store monitoring data in a different cluster than the production one.

To stop the creation of reporting indexes, you simply need to stop creating reports.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文