# Why .monitoring-es-7-mb-\* size is increasing?

**URL:** https://discuss.elastic.co/t/why-monitoring-es-7-mb-size-is-increasing/285988
**Category:** Elasticsearch
**Created:** [October 6, 2021, 7:37am UTC](https://discuss.elastic.co/t/why-monitoring-es-7-mb-size-is-increasing/285988 "2021-10-06T07:37:29Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Aniket\_Pant](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@Aniket\_Pant](https://discuss.elastic.co/u/Aniket_Pant)
#### Post date: [October 6, 2021, 7:37am UTC](https://discuss.elastic.co/t/why-monitoring-es-7-mb-size-is-increasing/285988/1 "2021-10-06T07:37:29Z")

</div>

Using metricbeat version 7.13.2 and elk version 7.13.2  
I've installed and setup metricbeat in master nodes only  
Here is metricbeat.yml file

```auto
###################### Metricbeat Configuration Example #######################

# This file is an example configuration file highlighting only the most common
# options. The metricbeat.reference.yml file from the same directory contains all the
# supported options with more comments. You can use it as a reference.
#
# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/beats/metricbeat/index.html

# =========================== Modules configuration ============================

metricbeat.config.modules:
  # Glob pattern for configuration loading
  path: ${path.config}/modules.d/*.yml

  # Set to true to enable config reloading
  reload.enabled: true

  # Period on which files under path should be checked for changes
  reload.period: 1s

# ======================= Elasticsearch template setting =======================

setup.template.settings:
  index.number_of_shards: 1
  index.codec: best_compression
  #_source.enabled: false

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

# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
#name:

# The tags of the shipper are included in their own field with each
# transaction published.
#tags: ["service-X", "web-tier"]

# Optional fields that you can specify to add additional information to the
# output.
#fields:
# env: staging

# ================================= Dashboards =================================
# These settings control loading the sample dashboards to the Kibana index. Loading
# the dashboards is disabled by default and can be enabled either by setting the
# options here or by using the `setup` command.
#setup.dashboards.enabled: false

# The URL from where to download the dashboards archive. By default this URL
# has a value which is computed based on the Beat name and version. For released
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
# website.
#setup.dashboards.url:

# =================================== Kibana ===================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:

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

  # Kibana Space ID
  # ID of the Kibana Space into which the dashboards should be loaded. By default,
  # the Default Space will be used.
  #space.id:

# =============================== Elastic Cloud ================================

# These settings simplify using Metricbeat with the Elastic Cloud (https://cloud.elastic.co/).

# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
# `setup.kibana.host` options.
# You can find the `cloud.id` in the Elastic Cloud web UI.
#cloud.id:

# The cloud.auth setting overwrites the `output.elasticsearch.username` and
# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
#cloud.auth:

# ================================== Outputs ===================================

# Configure what output to use when sending the data collected by the beat.

# ---------------------------- Elasticsearch Output ----------------------------
output.elasticsearch:
  # Array of hosts to connect to.
  hosts:
    - "https://xx.xx.xx.xx:9200"
    - "https://1xx.xx.xx.xx:9200"

  # Protocol - either `http` (default) or `https`.
  #protocol: "https"
  ssl.certificate_authorities: ["/etc/elasticsearch/certs/ca/ca.crt"]
  # Authentication credentials - either API key or username/password.
  #api_key: "id:api_key"
  username: "aniket"
  password: "xxxxx"
logging.level: debug
logging.selectors: ["*"]
logging.to_files: true
logging.files:
  path: /var/log/metricbeat
  name: metricbeat
  keepfiles: 7
  permissions: 0644
# ------------------------------ Logstash Output -------------------------------
#output.logstash:
  # The Logstash hosts
  #hosts: ["localhost:5044"]

  # Optional SSL. By default is off.
  # 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"

# ================================= Processors =================================

# Configure processors to enhance or manipulate events generated by the beat.

processors:
  - add_host_metadata: ~
  - add_cloud_metadata: ~
  - add_docker_metadata: ~
  - add_kubernetes_metadata: ~

# ================================== Logging ===================================

# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
#logging.level: debug

# At debug level, you can selectively enable logging only for some components.
# To enable all selectors use ["*"]. Examples of other selectors are "beat",
# "publisher", "service".
#logging.selectors: ["*"]

# ============================= X-Pack Monitoring ==============================
# Metricbeat can export internal metrics to a central Elasticsearch monitoring
# cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
# reporting is disabled by default.

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

# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
# Metricbeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
#monitoring.cluster_uuid:

# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well.
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration, so if you have the Elasticsearch output configured such
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
# uncomment the following line.
#monitoring.elasticsearch:

# ============================== Instrumentation ===============================

# Instrumentation support for the metricbeat.
#instrumentation:
    # Set to true to enable instrumentation of metricbeat.
    #enabled: false

    # Environment in which metricbeat is running on (eg: staging, production, etc.)
    #environment: ""

    # APM Server hosts to report instrumentation results to.
    #hosts:
    # - http://localhost:8200

    # API Key for the APM Server(s).
    # If api_key is set then secret_token will be ignored.
    #api_key:

    # Secret token for the APM Server(s).
    #secret_token:

# ================================= Migration ==================================

# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true

```

and given below is /modules.d/Elasticsearch-xpack.yml file

```auto
# Module: elasticsearch
# Docs: https://www.elastic.co/guide/en/beats/metricbeat/7.10/metricbeat-module-elasticsearch.html

- module: elasticsearch
  xpack.enabled: true
  period: 10s
  #metricsets:
  #- cluster_stats
  #- index
  #- index_recovery
  #- index_summary
  #- node
  #- node_stats
  #- pending_tasks
  #- shard
  scope: cluster
  hosts:
    - "https://xx.xx.xx.xx:9200" #em1
    - "https://xx.xx.xx.xx:9200" #em2
    - "https://xx.xx.xx.xx:9200" #em3

  ssl.certificate_authorities: ["/etc/elasticsearch/certs/ca/ca.crt"]
  username: "aniket"
  password: "xxxx

```

i don't know why my monitor-es size is increasing day by day earlier it was 20 to 50gb size but now its is increasing

```auto
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open .monitoring-es-7-mb-2021.10.06 RFhbberbTIy6fxU5OgBVJA 1 1 21626826 0 33.6gb 16.9gb
green open .monitoring-es-7-mb-2021.10.05 Jg5m_P5-T9-XBvDR5dR-2w 1 1 51205974 0 78.9gb 39.4gb
green open .monitoring-es-7-mb-2021.10.04 0z2dprepTEetBCQRajsmBg 1 1 56555054 0 87.5gb 43.7gb
green open .monitoring-es-7-mb-2021.10.03 xumFYcFcR1CF1R98q-t6XQ 1 1 63201813 0 97.5gb 48.7gb
green open .monitoring-es-7-mb-2021.10.02 uCJdSZiwRKCCD9jLQX9unw 1 1 66309480 0 102.2gb 51.1gb
green open .monitoring-es-7-mb-2021.10.01 ec0ZPFFESxu4u60A87OEBA 1 1 68579358 0 106.5gb 53.2gb
green open .monitoring-es-7-mb-2021.09.30 6jpA04IyR1Cihze8MZo6-Q 1 1 68286780 0 106.7gb 53.3gb

```

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [October 6, 2021, 9:06am UTC](https://discuss.elastic.co/t/why-monitoring-es-7-mb-size-is-increasing/285988/2 "2021-10-06T09:06:34Z")

</div>

You mean "decreasing" right?

---

<div class="post-metadata">

### Author: ![Aniket\_Pant](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@Aniket\_Pant](https://discuss.elastic.co/u/Aniket_Pant)
#### Post date: [October 6, 2021, 9:08am UTC](https://discuss.elastic.co/t/why-monitoring-es-7-mb-size-is-increasing/285988/3 "2021-10-06T09:08:24Z")

</div>

no.. _pri.store.size_ is increasing

---

<div class="post-metadata">

### Author: ![Aniket\_Pant](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@Aniket\_Pant](https://discuss.elastic.co/u/Aniket_Pant)
#### Post date: [October 6, 2021, 9:10am UTC](https://discuss.elastic.co/t/why-monitoring-es-7-mb-size-is-increasing/285988/4 "2021-10-06T09:10:46Z")

</div>

sorry , i mean sometime .monitoring-es-7-mb size gets increases.

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [October 6, 2021, 10:08am UTC](https://discuss.elastic.co/t/why-monitoring-es-7-mb-size-is-increasing/285988/5 "2021-10-06T10:08:38Z")

</div>

It's decreasing in time.

I can't tell why there is a difference though. May be more events one day vs another day?

---

<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: [November 3, 2021, 10:09am UTC](https://discuss.elastic.co/t/why-monitoring-es-7-mb-size-is-increasing/285988/6 "2021-11-03T10:09:10Z")

</div>

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