# Monitoring query sent to Elasticsearch
**URL:** https://discuss.elastic.co/t/monitoring-query-sent-to-elasticsearch/206849
**Category:** Elasticsearch
**Created:** [November 6, 2019, 6:36pm UTC](https://discuss.elastic.co/t/monitoring-query-sent-to-elasticsearch/206849 "2019-11-06T18:36:56Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@rschirin](https://discuss.elastic.co/u/rschirin)
#### Post date: [November 6, 2019, 6:36pm UTC](https://discuss.elastic.co/t/monitoring-query-sent-to-elasticsearch/206849/1 "2019-11-06T18:36:56Z")
hi guys,
currently I have one cluster with v5.6.x and, even thought we have scheduled to upgrade it to v6.8, I have to dive deeper regarding the query sent to ES just to check what is happening in that moment.
I found this [Elastic's blog article](https://www.elastic.co/blog/monitoring-the-search-queries) and I would like to know if I can still consider it valid or not.
Furthermore, I would like to know if the `xpack.monitoring` feature (available on v6.x) could be considered as equivalent to Packetbeat usage described in that article or not.
thanks
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [November 7, 2019, 9:17am UTC](https://discuss.elastic.co/t/monitoring-query-sent-to-elasticsearch/206849/2 "2019-11-07T09:17:38Z")
Hey,
this article is already three years old, so it's time for a quick update. 🙂
First, the current stack monitoring has nothing to do with packetbeat. Take a look at [https://www.elastic.co/what-is/elasticsearch-monitoring](https://www.elastic.co/what-is/elasticsearch-monitoring) (go to the getting started link at the end to see how to get going).
Also, you might want to check out the documentation at [https://www.elastic.co/guide/en/kibana/6.8/xpack-monitoring.html](https://www.elastic.co/guide/en/kibana/6.8/xpack-monitoring.html)
Hope this helps!
--Alex
---
### Author:  [@rschirin](https://discuss.elastic.co/u/rschirin)
#### Post date: [November 7, 2019, 10:50am UTC](https://discuss.elastic.co/t/monitoring-query-sent-to-elasticsearch/206849/3 "2019-11-07T10:50:04Z")
thanks @spinscale.
I already use `xpack.monitoring` and `xpack.monitoring.collection` on another cluster.
unfortunately, in my current situation, I would like to trace the `search` request sent to my ES cluster; using `xpack.monitoring` I'm seeing that I cannot to that. Am I wrong?
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [November 7, 2019, 3:08pm UTC](https://discuss.elastic.co/t/monitoring-query-sent-to-elasticsearch/206849/4 "2019-11-07T15:08:20Z")
you could use the [slow log](https://www.elastic.co/guide/en/elasticsearch/reference/7.4/index-modules-slowlog.html) to log every query or indeed packetbeat, if your data is not encrypted.
---
### Author:  [@rschirin](https://discuss.elastic.co/u/rschirin)
#### Post date: [November 7, 2019, 3:37pm UTC](https://discuss.elastic.co/t/monitoring-query-sent-to-elasticsearch/206849/5 "2019-11-07T15:37:30Z")
Yes, my data is encrypted so https could not be linked to Packetbeat usage. anyway, I suppose that I should try to use `slow log` feature but I don't know if I could then visualize them using Kibana.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 5, 2019, 3:37pm UTC](https://discuss.elastic.co/t/monitoring-query-sent-to-elasticsearch/206849/6 "2019-12-05T15:37:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.