# Rollup-Jobs - How to visualize Raw and Rolledup-Data

**URL:** <https://discuss.elastic.co/t/rollup-jobs-how-to-visualize-raw-and-rolledup-data/282065>\
**Category:** Kibana\
**Tags:** vega, rollups\
**Created:** [August 20, 2021, 10:34am UTC](https://discuss.elastic.co/t/rollup-jobs-how-to-visualize-raw-and-rolledup-data/282065 "2021-08-20T10:34:33Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![cwiechmann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cwiechmann/32/80908_2.png) [@cwiechmann](https://discuss.elastic.co/u/cwiechmann)\
**Post date:** [August 20, 2021, 10:34am UTC](https://discuss.elastic.co/t/rollup-jobs-how-to-visualize-raw-and-rolledup-data/282065/1 "2021-08-20T10:34:33Z")

</div>

Hi Experts,

I'm using the Elasticstack version 7.14.0 and have started to use Rollup-Jobs. Based on the documentation is seems, that rolled-up query results should include Raw-Data (as long as available) and automatically switch over to Rolled-Up data.

"_A useful feature of Rollup is the ability to query both "live", realtime data in addition to historical "rolled" data in a single query._"

> **[Rollup overview | Elasticsearch Guide \[7.14\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.14/rollup-overview.html)**

When making a manual query including both index-patterns I do get the expected result:

```json
GET apigw-traffic-summary*,rollup-hourly-apigw-traffic-summary/_rollup_search
{
  "aggregations": {
    "finalStatus": {
      "terms": {
        "field": "finalStatus"
      }
    }
  },
  "size": 0
}

```

But in all of the visualizations in Kibana (maybe besides Vega), I cannot select two index patterns at the same time and when selecting the Rollup-Index-Pattern only, I do get only rolled up data.

How is it intended that you can display rolled up and raw data in a visualization in Kibana?

---

<div class="post-metadata">

**Author:** ![cwiechmann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cwiechmann/32/80908_2.png) [@cwiechmann](https://discuss.elastic.co/u/cwiechmann)\
**Post date:** [August 20, 2021, 1:24pm UTC](https://discuss.elastic.co/t/rollup-jobs-how-to-visualize-raw-and-rolledup-data/282065/2 "2021-08-20T13:24:44Z")

</div>

I tried to use an Index-Pattern that matches both, the regular and the rolled-up index.  
But it seems, with that only the data from the regular index is shown, because once I delete the regular index no data is shown anymore.

Of course, the rolled-up index has already the information, because if I use an Index-Pattern matching only to the Rolled-Up index I can see the data.

---

<div class="post-metadata">

**Author:** ![cwiechmann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cwiechmann/32/80908_2.png) [@cwiechmann](https://discuss.elastic.co/u/cwiechmann)\
**Post date:** [August 20, 2021, 2:13pm UTC](https://discuss.elastic.co/t/rollup-jobs-how-to-visualize-raw-and-rolledup-data/282065/3 "2021-08-20T14:13:45Z")

</div>

I have realized, it is working okay using a Lens but not with a TSVB, when using an index-pattern matching Rolled-Up and Regular-Index.

---

<div class="post-metadata">

**Author:** ![cwiechmann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cwiechmann/32/80908_2.png) [@cwiechmann](https://discuss.elastic.co/u/cwiechmann)\
**Post date:** [August 20, 2021, 6:00pm UTC](https://discuss.elastic.co/t/rollup-jobs-how-to-visualize-raw-and-rolledup-data/282065/4 "2021-08-20T18:00:00Z")

</div>

One more comment. Also the manual query seems not work as I expect based on the documentation.  
The following query includes the RAW-Index and the Rolled-Up:

```json
GET apigw-traffic-summary*,apigw-traffic-sum-hourly-rolledup/_rollup_search
{
  "aggregations": {
    "finalStatus": {
      "terms": {
        "field": "finalStatus"
      }
    }
  },
  "size": 0
}

```

The result includes only the data from the RAW-Index:

```json
  "aggregations" : {
    "finalStatus" : {
      "doc_count_error_upper_bound" : 0,
      "sum_other_doc_count" : 0,
      "buckets" : [
        {
          "key" : "Pass",
          "doc_count" : 11
        },
        {
          "key" : "Fail",
          "doc_count" : 8
        }
      ]
    }
  }

```

Now, when performing the query on the rolled up index only it returns already rolled up data:

```json
GET apigw-traffic-sum-hourly-rolledup/_rollup_search
{
  "aggregations": {
    "finalStatus": {
      "terms": {
        "field": "finalStatus"
      }
    }
  },
  "size": 0
}

```

This is the result:

```json
  "aggregations" : {
    "finalStatus" : {
      "doc_count_error_upper_bound" : 0,
      "sum_other_doc_count" : 0,
      "buckets" : [
        {
          "key" : "Pass",
          "doc_count" : 67
        },
        {
          "key" : "Fail",
          "doc_count" : 35
        }
      ]
    }
  }

```

I expected, that the first query merges the result from both indices or I missunderstood the entire Rollup-Feature.

Any help/idea/hint is much appreciated.

Thanks!  
Chris

---

<div class="post-metadata">

**Author:** ![cwiechmann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cwiechmann/32/80908_2.png) [@cwiechmann](https://discuss.elastic.co/u/cwiechmann)\
**Post date:** [August 23, 2021, 9:08am UTC](https://discuss.elastic.co/t/rollup-jobs-how-to-visualize-raw-and-rolledup-data/282065/5 "2021-08-23T09:08:34Z")

</div>

Looks like the issue reported here: [[Rollup] Rollup search ignores rolledup data in weird case · Issue #50155 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/50155).

Does anyone has an idea on this?

---

<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:** [September 20, 2021, 9:08am UTC](https://discuss.elastic.co/t/rollup-jobs-how-to-visualize-raw-and-rolledup-data/282065/6 "2021-09-20T09:08:39Z")

</div>

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