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 :/










share|improve this question
























  • 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















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 :/










share|improve this question
























  • 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













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 :/










share|improve this question















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 14 at 12:01

























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


















  • 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

















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















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






























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














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





















































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







Popular posts from this blog

How to change which sound is reproduced for terminal bell?

Can I use Tabulator js library in my java Spring + Thymeleaf project?

Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents