# How to add multiple metricbeat parameter to query

**URL:** <https://discuss.elastic.co/t/how-to-add-multiple-metricbeat-parameter-to-query/211634>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [December 12, 2019, 11:29am UTC](https://discuss.elastic.co/t/how-to-add-multiple-metricbeat-parameter-to-query/211634 "2019-12-12T11:29:00Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![arvindK\_sharma](https://avatars.discourse-cdn.com/v4/letter/a/a9a28c/32.png) [@arvindK\_sharma](https://discuss.elastic.co/u/arvindK_sharma)\
**Post date:** [December 12, 2019, 11:29am UTC](https://discuss.elastic.co/t/how-to-add-multiple-metricbeat-parameter-to-query/211634/1 "2019-12-12T11:29:01Z")

</div>

Hi,

I want to expose endpoint of Metricbeat system parameters (Same as KIBANA) with the help of NEST to create a page similar to KIBANA dashboard in my application. I want to fetch all the parameters like CPU, Memory, diskio etc. I write following query which gives me latest one hit for cpu parameter

```
get /metricbeat*/_search?pretty=true
{"size":1,
 "query":{"bool":{"must": [{"range": {"system.cpu.idle.pct": {"gte": 0}}}]}},
   "sort":[{"@timestamp": {"order": "desc"}}]}

```

I want to add memoery, diskio and some more parameter to it so I get on hit per parameter. I tried to add by this way but no luck

```
{"range": {"system.cpu.idle.pct": {"gte": 0}}}, {"range": {"system.memory.used.pct": {"gte": 0}}}

```

Please suggest how to implement it.

---

<div class="post-metadata">

**Author:** ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)\
**Post date:** [December 12, 2019, 12:05pm UTC](https://discuss.elastic.co/t/how-to-add-multiple-metricbeat-parameter-to-query/211634/2 "2019-12-12T12:05:04Z")

</div>

Hi!

I would suggest to create the search you want in Kibana and then Inspect it in order to take the query and reuse it in your app.

---

<div class="post-metadata">

**Author:** ![arvindK\_sharma](https://avatars.discourse-cdn.com/v4/letter/a/a9a28c/32.png) [@arvindK\_sharma](https://discuss.elastic.co/u/arvindK_sharma)\
**Post date:** [December 13, 2019, 3:13am UTC](https://discuss.elastic.co/t/how-to-add-multiple-metricbeat-parameter-to-query/211634/3 "2019-12-13T03:13:05Z")

</div>

Will you please elaborate more on how to do that ?

---

<div class="post-metadata">

**Author:** ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)\
**Post date:** [December 13, 2019, 8:58am UTC](https://discuss.elastic.co/t/how-to-add-multiple-metricbeat-parameter-to-query/211634/4 "2019-12-13T08:58:02Z")

</div>

Hey,

have a look at [https://www.elastic.co/guide/en/kibana/master/save-open-search.html](https://www.elastic.co/guide/en/kibana/master/save-open-search.html).

After you have saved a search you can inspect this and see the source query. For instance:

 ![14](https://us1.discourse-cdn.com/elastic/original/3X/8/1/816da1da64ad1fbedf7687901da08bd37661b172.png)

---

<div class="post-metadata">

**Author:** ![arvindK\_sharma](https://avatars.discourse-cdn.com/v4/letter/a/a9a28c/32.png) [@arvindK\_sharma](https://discuss.elastic.co/u/arvindK_sharma)\
**Post date:** [December 17, 2019, 5:59am UTC](https://discuss.elastic.co/t/how-to-add-multiple-metricbeat-parameter-to-query/211634/5 "2019-12-17T05:59:06Z")

</div>

> [@ChrsMark](#):
>
> search you can inspect this and see the source query. For instance:

Thanks Chris,

Sorry for late reply, I was busy with other stuff for time being.

I found your suggestion very helpful and write my query with multiple fields now.  
Eventually , I found that query gives me result if I club same metricset name fields like memory or CPU. like:  
{"range": {  
"system.cpu.iowait.pct": {  
"gte": 0,  
"lt": 1  
} }},  
{"range": {  
"system.cpu.idle.pct": {  
"gte": 0,  
"lt": 1 }}},

But if I add different metricset name than it wont give anything  
{ "range": {  
"system.memory.actual.used.pct": {  
"gte": 0,  
"lt": 1  
}}},  
{"range": {  
"system.cpu.idle.pct": {  
"gte": 0,  
"lt": 1}}}

Here I add 'Memory' type with 'CPU' so query result is empty

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/c/9c1f588023a45e68ec53a7170ded7f4c3a5910a6.png)

My objective is to get all system parameters of metricset.name.

---

<div class="post-metadata">

**Author:** ![arvindK\_sharma](https://avatars.discourse-cdn.com/v4/letter/a/a9a28c/32.png) [@arvindK\_sharma](https://discuss.elastic.co/u/arvindK_sharma)\
**Post date:** [December 17, 2019, 6:04am UTC](https://discuss.elastic.co/t/how-to-add-multiple-metricbeat-parameter-to-query/211634/6 "2019-12-17T06:04:39Z")

</div>

Actully I want to return % in below screen should return by my endpoints.

![Untitled2](https://us1.discourse-cdn.com/elastic/original/3X/2/f/2f959c169538182bec20a755a2c96e57a5309da2.png)

---

<div class="post-metadata">

**Author:** ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)\
**Post date:** [December 17, 2019, 8:23am UTC](https://discuss.elastic.co/t/how-to-add-multiple-metricbeat-parameter-to-query/211634/7 "2019-12-17T08:23:15Z")

</div>

Hi!

Glad that you found inspecting useful!

For your question now I would suggest something like this:

 ![Screenshot 2019-12-17 at 10.20.27](https://us1.discourse-cdn.com/elastic/original/3X/d/9/d92aff21939fd07b171e13d58b87c59214bdd11f.png)

However since your question tends to be more Elasticsearch oriented, you could also ask in Elasticsearch's forum so as to get the most optimised query for your purposes.

Thanks!

---

<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:** [January 14, 2020, 8:23am UTC](https://discuss.elastic.co/t/how-to-add-multiple-metricbeat-parameter-to-query/211634/8 "2020-01-14T08:23:17Z")

</div>

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