Metricbeat collects system metrics for interfaces you didn't configure
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
The System module specifies several metricsets that are enabled by default unless you explicitly disable them. To disable a default metricset, comment it out in the modules.d/system.yml configuration file. If all metricsets are commented out and the System module is enabled, Metricbeat uses the default metricsets.
For example, to disable the network metricset, comment it out:
- module: system
period: 10s
metricsets:
- cpu
- load
- memory
#- network
- process
- process_summary
- socket_summary
#- entropy
#- core
#- diskio
#- socket
You cannot override the default configuration by adding another module definition to the configuration. There is no concept of inheritance. Metricbeat combines all module configurations at runtime. This enables you to specify module definitions that use different combinations of metricsets, periods, and hosts.