# Monitoring query stats
**URL:** https://discuss.elastic.co/t/monitoring-query-stats/43445
**Category:** Elasticsearch
**Tags:** elastic-stack-monitoring
**Created:** [March 3, 2016, 9:29pm UTC](https://discuss.elastic.co/t/monitoring-query-stats/43445 "2016-03-03T21:29:09Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Karthik\_Ramachandran](https://discuss.elastic.co/u/Karthik_Ramachandran)
#### Post date: [March 3, 2016, 9:29pm UTC](https://discuss.elastic.co/t/monitoring-query-stats/43445/1 "2016-03-03T21:29:09Z")
How do i monitor individual query stats viz. What is the exact search/filter request and time taken to execute the same + other stats. I need
1. What exact request came in
2. What is the response time
3. Did it fail
4. Number of nodes/shards it has to depend on
5. Perf/Stress metrics on memory/cpu etc.
---
### Author:  [@skearns](https://discuss.elastic.co/u/skearns)
#### Post date: [March 3, 2016, 9:41pm UTC](https://discuss.elastic.co/t/monitoring-query-stats/43445/2 "2016-03-03T21:41:30Z")
Hi Karthik,
Marvel doesn't provide this level of visibility today. This sort of query analysis is something we're considering adding in the future though!
For now, I suggest starting with the Elasticsearch slow log and using the query profile API to help you understand why expensive queries are so expensive.
Thanks,
Steve
---
### Author:  [@Karthik\_Ramachandran](https://discuss.elastic.co/u/Karthik_Ramachandran)
#### Post date: [March 3, 2016, 9:43pm UTC](https://discuss.elastic.co/t/monitoring-query-stats/43445/3 "2016-03-03T21:43:08Z")
Thansk Steve.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:45pm UTC](https://discuss.elastic.co/t/monitoring-query-stats/43445/4 "2017-07-06T13:45:08Z")