# Continuous query couldn't create MEASUREMENTS

**URL:** <https://community.influxdata.com/t/continuous-query-couldnt-create-measurements/1378>\
**Category:** Store\
**Tags:** influxdb\
**Created:** [June 21, 2017, 6:52am UTC](https://community.influxdata.com/t/continuous-query-couldnt-create-measurements/1378 "2017-06-21T06:52:10Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![darkrasid](https://avatars.discourse-cdn.com/v4/letter/d/e9bcb4/32.png) [@darkrasid](https://community.influxdata.com/u/darkrasid)\
**Post date:** [June 21, 2017, 6:52am UTC](https://community.influxdata.com/t/continuous-query-couldnt-create-measurements/1378/1 "2017-06-21T06:52:10Z")

</div>

Hello, everyone.

I’m newbie on influx db.  
I try to monitoring my gitlab instance using influxdb and I need help 😥

First, I use influxdb 1.2.4 version on docker container.

I have some problem on continuous query.

My cq exmaple is

```auto
CREATE CONTINUOUS QUERY rails_allocated_memory_per_action ON gitlab
BEGIN
    SELECT percentile(allocated_memory, 95) AS allocated_memory_95th,
           percentile(allocated_memory, 99) AS allocated_memory_99th,
           mean(allocated_memory) AS allocated_memory_mean,
           max(allocated_memory) AS allocated_memory_max
    INTO downsampled.rails_allocated_memory_per_action
    FROM one_hour.rails_transactions
    WHERE action =~ /.+/
    AND action !~ /^Grape#/
    GROUP BY time(1m), action
END

```

From log I found this.

```auto
[I] 2017-06-21T06:17:00Z executing continuous query rails_allocated_memory_per_action (2017-06-21 06:16:00 +0000 UTC to 2017-06-21 06:17:00 +0000 UTC) service=continuous_querier
[I] 2017-06-21T06:17:00Z SELECT percentile(allocated_memory, 95) AS allocated_memory_95th, percentile(allocated_memory, 99) AS allocated_memory_99th, mean(allocated_memory) AS allocated_memory_mean, max(allocated_memory) AS allocated_mem
ory_max INTO gitlab.downsampled.rails_allocated_memory_per_action FROM gitlab.one_hour.rails_transactions WHERE action =~ /.+/ AND action !~ /^Grape#/ AND time >= '2017-06-21T06:16:00Z' AND time < '2017-06-21T06:17:00Z' GROUP BY time(1m)
, action service=query
[I] 2017-06-21T06:17:00Z finished continuous query rails_allocated_memory_per_action (2017-06-21 06:16:00 +0000 UTC to 2017-06-21 06:17:00 +0000 UTC) in 5.363964ms service=continuous_querier

```

I guess CQ executed well however when I execute `SHOW MEASUREMENTS`, there isn’t `rails_allocated_memory_per_action`.

If I execute below query

```auto
SELECT percentile(allocated_memory, 95) AS allocated_memory_95th, percentile(allocated_memory, 99) AS allocated_memory_99th, mean(allocated_memory) AS allocated_memory_mean, max(allocated_memory) AS allocated_memory_max 
FROM gitlab.one_hour.rails_transactions 
WHERE action =~ /.+/ AND action !~ /^Grape#/ AND time >= '2017-06-21T06:16:00Z' AND time < '2017-06-21T06:17:00Z'
GROUP BY time(1m), action

```

it has data something like this

```auto
...

time allocated_memory_95th allocated_memory_99th allocated_memory_mean allocated_memory_max
---- --------------------- --------------------- --------------------- --------------------
1498025760000000000 4.759552e+06 5.607424e+06 1.3684254117647058e+06 5.607424e+06

name: rails_transactions
tags: action=Projects::GitHttpController#info_refs.txt
time allocated_memory_95th allocated_memory_99th allocated_memory_mean allocated_memory_max
---- --------------------- --------------------- --------------------- --------------------
1498025760000000000 718131.2 3.514368e+06

...

```

And if I execute `INTO query` manually,

```auto
SELECT percentile(allocated_memory, 95) AS allocated_memory_95th, percentile(allocated_memory, 99) AS allocated_memory_99th, mean(allocated_memory) AS allocated_memory_mean, max(allocated_memory) AS allocated_memory_max 
INTO gitlab.downsampled.rails_allocated_memory_per_action 
FROM gitlab.one_hour.rails_transactions 
WHERE action =~ /.+/ AND action !~ /^Grape#/ AND time >= '2017-06-21T06:16:00Z' AND time < '2017-06-21T06:17:00Z'
GROUP BY time(1m), action

```

`rails_allocated_memory_per_action` MEASUREMENTS is created however no more data stored.

I think the CQs doesn’t work well so they can’t store data to MEASUREMENTS.

If anyone has hints why this happen, I’d really appreciate it!

---

<div class="post-metadata">

**Author:** ![jackzampolin](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/jackzampolin/32/5_2.png) [@jackzampolin](https://community.influxdata.com/u/jackzampolin)\
**Post date:** [June 21, 2017, 3:26pm UTC](https://community.influxdata.com/t/continuous-query-couldnt-create-measurements/1378/2 "2017-06-21T15:26:27Z")

</div>

@darkrasid I think you are running into issues with [Retention Policies](https://docs.influxdata.com/influxdb/v1.2/concepts/key_concepts/#retention-policy). Can you share the output of `SHOW RETENTION POLICIES ON gitlab`?

---

<div class="post-metadata">

**Author:** ![darkrasid](https://avatars.discourse-cdn.com/v4/letter/d/e9bcb4/32.png) [@darkrasid](https://community.influxdata.com/u/darkrasid)\
**Post date:** [June 22, 2017, 2:16am UTC](https://community.influxdata.com/t/continuous-query-couldnt-create-measurements/1378/3 "2017-06-22T02:16:17Z")

</div>

Sure 🙂

```auto
> SHOW RETENTION POLICIES ON gitlab
name duration shardGroupDuration replicaN default
---- -------- ------------------ -------- -------
autogen 0s 168h0m0s 1 false
one_hour 1h0m0s 1h0m0s 1 true
downsampled 168h0m0s 24h0m0s 1 false
year 8736h0m0s 168h0m0s 1 false
forever 0s 168h0m0s 1 false

```

Thank you

---

<div class="post-metadata">

**Author:** ![jackzampolin](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/jackzampolin/32/5_2.png) [@jackzampolin](https://community.influxdata.com/u/jackzampolin)\
**Post date:** [June 22, 2017, 5:32pm UTC](https://community.influxdata.com/t/continuous-query-couldnt-create-measurements/1378/4 "2017-06-22T17:32:26Z")

</div>

@darkrasid It seems like maybe if there is no data in that measurement when the CQ runs then it won’t calculate properly. Have you tried adding an [`EVERY ... FOR ...`](https://docs.influxdata.com/influxdb/v1.2/query_language/continuous_queries/#advanced-syntax) clause to your CQ? Another thing that might help here is adding [`fill()`](https://docs.influxdata.com/influxdb/v1.2//query_language/data_exploration/#group-by-time-intervals-and-fill) to your query as well.

---

<div class="post-metadata">

**Author:** ![darkrasid](https://avatars.discourse-cdn.com/v4/letter/d/e9bcb4/32.png) [@darkrasid](https://community.influxdata.com/u/darkrasid)\
**Post date:** [June 23, 2017, 4:38am UTC](https://community.influxdata.com/t/continuous-query-couldnt-create-measurements/1378/5 "2017-06-23T04:38:50Z")

</div>

@jackzampolin

Thank you for your hint. But when I use EVERY…FOR it wasn’t work.  
And I think there are data within 1 minute.

I found something strange behavior about my CQs.

I tried to execute CQs changing `group by time(1m)` to `group by time(2m)` and then the measurements were created and everything worked well. And `group by time(100s)` also works but under 100s (eg 90s , 60s …) aren’t worked.

I don’t have any idea why this situation happens. When I try test it on my local machine, setting `group by time(1m)` is also worked well (also use docker )

Could you please provide me any clue about this issue that can help me to find the way to solve it?

---

<div class="post-metadata">

**Author:** ![jackzampolin](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/jackzampolin/32/5_2.png) [@jackzampolin](https://community.influxdata.com/u/jackzampolin)\
**Post date:** [June 23, 2017, 5:44pm UTC](https://community.influxdata.com/t/continuous-query-couldnt-create-measurements/1378/6 "2017-06-23T17:44:41Z")

</div>

@darkrasid From the information I have here that would seem to indicate there is some latency in metric delivery and there is no data in the measurements when your CQ is running.

---

<div class="post-metadata">

**Author:** ![darkrasid](https://avatars.discourse-cdn.com/v4/letter/d/e9bcb4/32.png) [@darkrasid](https://community.influxdata.com/u/darkrasid)\
**Post date:** [June 27, 2017, 4:06am UTC](https://community.influxdata.com/t/continuous-query-couldnt-create-measurements/1378/7 "2017-06-27T04:06:50Z")

</div>

Yes, there was latency and time difference between servers was also existed.

Using `Every For` , as you suggest, is solving my issue.

I’d really appreciate for you help!

Thank you

---

<div class="post-metadata">

**Author:** ![jackzampolin](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/jackzampolin/32/5_2.png) [@jackzampolin](https://community.influxdata.com/u/jackzampolin)\
**Post date:** [June 27, 2017, 3:36pm UTC](https://community.influxdata.com/t/continuous-query-couldnt-create-measurements/1378/8 "2017-06-27T15:36:30Z")

</div>

@darkrasid Glad you were able to get that working!