Metricbeat sends process metrics even if it is disabled
up vote
0
down vote
favorite
i have the following config for metricbeat:
metricbeat.config.modules:
path: ${path.config}/modules.d/*.yml
reload.enabled: false
metricbeat_modules:
- module: system
metricsets:
- cpu
- load
- memory
- network
- diskio
enabled: true
period: 10s
tags: ['os']
cpu.metrics: ['percentages']
core.metrics: ['percentages']
setup.template:
name: {{ metricbeat_index }}
pattern: {{ metricbeat_index }}-*
settings:
index:
number_of_shards: 1
codec: best_compression
tags: [{{ metricbeat_tags | join(', ') }}]
fields:
env: {{ metricbeat_env }}
output.elasticsearch:
hosts: {{ metricbeat_output_es_hosts | to_json }}
index: "{{ metricbeat_index }}-%{+yyyy-MM-dd}"
setup.dashboards.directory: /usr/share/metricbeat/kibana
setup.kibana:
host: {{ metricbeat_kibana_url }}
processors:
- drop_fields:
fields: ["beat.name","beat.hostname"]
processors:
- add_host_metadata:
netinfo.enabled: false
processors:
- add_cloud_metadata: ~
it worked as expected as i had the metricsets process and process_summary enabled. since i removed them it seems still to harvest those metrics. i restarted, stopped/started metricbeat again but it still has no effect.
Thanks for ideas as i cannot see any reason why this should happen this way :/
elasticsearch logging metricbeat asked Nov 13 at 15:10
SteelSailor
317
add a comment |
up vote
0
down vote
favorite
i have the following config for metricbeat:
metricbeat.config.modules:
path: ${path.config}/modules.d/*.yml
reload.enabled: false
metricbeat_modules:
- module: system
metricsets:
- cpu
- load
- memory
- network
- diskio
enabled: true
period: 10s
tags: ['os']
cpu.metrics: ['percentages']
core.metrics: ['percentages']
setup.template:
name: {{ metricbeat_index }}
pattern: {{ metricbeat_index }}-*
settings:
index:
number_of_shards: 1
codec: best_compression
tags: [{{ metricbeat_tags | join(', ') }}]
fields:
env: {{ metricbeat_env }}
output.elasticsearch:
hosts: {{ metricbeat_output_es_hosts | to_json }}
index: "{{ metricbeat_index }}-%{+yyyy-MM-dd}"
setup.dashboards.directory: /usr/share/metricbeat/kibana
setup.kibana:
host: {{ metricbeat_kibana_url }}
processors:
- drop_fields:
fields: ["beat.name","beat.hostname"]
processors:
- add_host_metadata:
netinfo.enabled: false
processors:
- add_cloud_metadata: ~
it worked as expected as i had the metricsets process and process_summary enabled. since i removed them it seems still to harvest those metrics. i restarted, stopped/started metricbeat again but it still has no effect.
Thanks for ideas as i cannot see any reason why this should happen this way :/
elasticsearch logging metricbeat asked Nov 13 at 15:10
SteelSailor
317
Which version of metricbeats are you running ? Do you have any other config files in modules.d directory ? Can you post your full metricbeat.yml ?
– ben5556
Nov 14 at 9:58
I edited the config. im running metricbeat v 6.4.2 on aws ec2. the only processor which takes effect is the cloud_meta_data. the other ones are ignored as well
– SteelSailor
Nov 14 at 12:03
Does your logs show anything helpful ?
– ben5556
Nov 14 at 21:37
Unfortunately they look as intended. I fixed the processors issue, i thought i could specify multiple processors keys but it only works if i stack them under one key... i guess the process issue rises from one of the modules as they might store infos under that key otherwise i cannot explain this behaviour
– SteelSailor
Nov 15 at 15:05
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
i have the following config for metricbeat:
metricbeat.config.modules:
path: ${path.config}/modules.d/*.yml
reload.enabled: false
metricbeat_modules:
- module: system
metricsets:
- cpu
- load
- memory
- network
- diskio
enabled: true
period: 10s
tags: ['os']
cpu.metrics: ['percentages']
core.metrics: ['percentages']
setup.template:
name: {{ metricbeat_index }}
pattern: {{ metricbeat_index }}-*
settings:
index:
number_of_shards: 1
codec: best_compression
tags: [{{ metricbeat_tags | join(', ') }}]
fields:
env: {{ metricbeat_env }}
output.elasticsearch:
hosts: {{ metricbeat_output_es_hosts | to_json }}
index: "{{ metricbeat_index }}-%{+yyyy-MM-dd}"
setup.dashboards.directory: /usr/share/metricbeat/kibana
setup.kibana:
host: {{ metricbeat_kibana_url }}
processors:
- drop_fields:
fields: ["beat.name","beat.hostname"]
processors:
- add_host_metadata:
netinfo.enabled: false
processors:
- add_cloud_metadata: ~
it worked as expected as i had the metricsets process and process_summary enabled. since i removed them it seems still to harvest those metrics. i restarted, stopped/started metricbeat again but it still has no effect.
Thanks for ideas as i cannot see any reason why this should happen this way :/
elasticsearch logging metricbeat asked Nov 13 at 15:10
SteelSailor
317
i have the following config for metricbeat:
metricbeat.config.modules:
path: ${path.config}/modules.d/*.yml
reload.enabled: false
metricbeat_modules:
- module: system
metricsets:
- cpu
- load
- memory
- network
- diskio
enabled: true
period: 10s
tags: ['os']
cpu.metrics: ['percentages']
core.metrics: ['percentages']
setup.template:
name: {{ metricbeat_index }}
pattern: {{ metricbeat_index }}-*
settings:
index:
number_of_shards: 1
codec: best_compression
tags: [{{ metricbeat_tags | join(', ') }}]
fields:
env: {{ metricbeat_env }}
output.elasticsearch:
hosts: {{ metricbeat_output_es_hosts | to_json }}
index: "{{ metricbeat_index }}-%{+yyyy-MM-dd}"
setup.dashboards.directory: /usr/share/metricbeat/kibana
setup.kibana:
host: {{ metricbeat_kibana_url }}
processors:
- drop_fields:
fields: ["beat.name","beat.hostname"]
processors:
- add_host_metadata:
netinfo.enabled: false
processors:
- add_cloud_metadata: ~
it worked as expected as i had the metricsets process and process_summary enabled. since i removed them it seems still to harvest those metrics. i restarted, stopped/started metricbeat again but it still has no effect.
Thanks for ideas as i cannot see any reason why this should happen this way :/
elasticsearch logging metricbeat elasticsearch logging metricbeat asked Nov 13 at 15:10
SteelSailor
317
asked Nov 13 at 15:10
SteelSailor
317
edited Nov 14 at 12:01
asked Nov 13 at 15:10
SteelSailor
317
asked Nov 13 at 15:10
SteelSailor
317
asked Nov 13 at 15:10
SteelSailor
317
317
Which version of metricbeats are you running ? Do you have any other config files in modules.d directory ? Can you post your full metricbeat.yml ?
– ben5556
Nov 14 at 9:58
I edited the config. im running metricbeat v 6.4.2 on aws ec2. the only processor which takes effect is the cloud_meta_data. the other ones are ignored as well
– SteelSailor
Nov 14 at 12:03
Does your logs show anything helpful ?
– ben5556
Nov 14 at 21:37
Unfortunately they look as intended. I fixed the processors issue, i thought i could specify multiple processors keys but it only works if i stack them under one key... i guess the process issue rises from one of the modules as they might store infos under that key otherwise i cannot explain this behaviour
– SteelSailor
Nov 15 at 15:05
add a comment |
Which version of metricbeats are you running ? Do you have any other config files in modules.d directory ? Can you post your full metricbeat.yml ?
– ben5556
Nov 14 at 9:58
I edited the config. im running metricbeat v 6.4.2 on aws ec2. the only processor which takes effect is the cloud_meta_data. the other ones are ignored as well
– SteelSailor
Nov 14 at 12:03
Does your logs show anything helpful ?
– ben5556
Nov 14 at 21:37
Unfortunately they look as intended. I fixed the processors issue, i thought i could specify multiple processors keys but it only works if i stack them under one key... i guess the process issue rises from one of the modules as they might store infos under that key otherwise i cannot explain this behaviour
– SteelSailor
Nov 15 at 15:05
Which version of metricbeats are you running ? Do you have any other config files in modules.d directory ? Can you post your full metricbeat.yml ?
– ben5556
Nov 14 at 9:58
Which version of metricbeats are you running ? Do you have any other config files in modules.d directory ? Can you post your full metricbeat.yml ?
– ben5556
Nov 14 at 9:58
I edited the config. im running metricbeat v 6.4.2 on aws ec2. the only processor which takes effect is the cloud_meta_data. the other ones are ignored as well
– SteelSailor
Nov 14 at 12:03
I edited the config. im running metricbeat v 6.4.2 on aws ec2. the only processor which takes effect is the cloud_meta_data. the other ones are ignored as well
– SteelSailor
Nov 14 at 12:03
Does your logs show anything helpful ?
– ben5556
Nov 14 at 21:37
Does your logs show anything helpful ?
– ben5556
Nov 14 at 21:37
Unfortunately they look as intended. I fixed the processors issue, i thought i could specify multiple processors keys but it only works if i stack them under one key... i guess the process issue rises from one of the modules as they might store infos under that key otherwise i cannot explain this behaviour
– SteelSailor
Nov 15 at 15:05
Unfortunately they look as intended. I fixed the processors issue, i thought i could specify multiple processors keys but it only works if i stack them under one key... i guess the process issue rises from one of the modules as they might store infos under that key otherwise i cannot explain this behaviour
– SteelSailor
Nov 15 at 15:05
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53283979%2fmetricbeat-sends-process-metrics-even-if-it-is-disabled%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Which version of metricbeats are you running ? Do you have any other config files in modules.d directory ? Can you post your full metricbeat.yml ?
– ben5556
Nov 14 at 9:58
I edited the config. im running metricbeat v 6.4.2 on aws ec2. the only processor which takes effect is the cloud_meta_data. the other ones are ignored as well
– SteelSailor
Nov 14 at 12:03
Does your logs show anything helpful ?
– ben5556
Nov 14 at 21:37
Unfortunately they look as intended. I fixed the processors issue, i thought i could specify multiple processors keys but it only works if i stack them under one key... i guess the process issue rises from one of the modules as they might store infos under that key otherwise i cannot explain this behaviour
– SteelSailor
Nov 15 at 15:05