# X-pack not generating indices **URL:** \ **Category:** Elasticsearch\ **Created:** [June 13, 2017, 1:59am UTC](https://discuss.elastic.co/t/x-pack-not-generating-indices/89128 "2017-06-13T01:59:29Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![Sjaak01](https://avatars.discourse-cdn.com/v4/letter/s/73ab20/32.png) [@Sjaak01](https://discuss.elastic.co/u/Sjaak01)\ **Post date:** [June 13, 2017, 5:08am UTC](https://discuss.elastic.co/t/x-pack-not-generating-indices/89128/7 "2017-06-13T05:08:24Z")
> [@bohyun](#): > > To view the raw objects in your .reporting index, run GET .reporting-2017.06.11/\_search and you will be able to see all of the reports that were generated from 2017.06.11 to today. Thanks. Something like this but because I don't know what I'm doing its not really going anywhere at the moment. > [@Alert on SUM of field exeeding certain value?](https://discuss.elastic.co/t/alert-on-sum-of-field-exeeding-certain-value/88654/2): > > Hey, this sounds possible to me. The important part here is to write a proper search query (independent from the watch). The search query needs to do the following have a range filter in your query that filters from the first of the month until now have a term filter in your query (or a match query), that filters for the host you are interested in have a sum aggregation in your request, that counts up your bytes (use the [sum aggregation](https://www.elastic.co/guide/en/elasticsearch/reference/5.4/search-aggregations-metrics-sum-aggregation.html) Now you got the correct data (a single aggregation re… --- _[View the full topic](https://discuss.elastic.co/t/x-pack-not-generating-indices/89128)._