-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wildcard support for fields in continuous queries. #5750
Comments
As far as I know, there isn't better way and all fields must be listed. |
Would be nice to have. |
+1 |
If I understood correctly, in order to downsample data, I need have create cq query for every single field in every single measurement, that will take like whole week. And every time I add new fields, I will have to add more continuous queries. I am currently filling up influxdb with new 0.10 version of telegraf, cadvisor and heapster. And after I do all this, grafana will not recognise this new retention policies unless I change data source. This is pretty much deal breaker for influxdb, |
This seems like a really important feature, since the old style (just a single value) is very simple to downsample but when taking advantage of multiple values per measurements you need to make many continuous queries to get the same result, and could easily miss adding new CQs when new data points are added |
+1 |
+1 I reckon a blog post on how to set retention policies for many (random) metrics that you do not even know or manage would be good. For instance in the following examples, you would like influxdb to automagically handle the 'retention rules' of any new metrics :
FWIW, our setup: collectd-client --> collectd-server --> influx |
This will be fixed by #6529 when that's merged. |
+1 |
Wildcard support for only fields is now supported. |
@jsternberg This seems to be the right issue for field wildcards. I think it was closed by mistake. This functionality definitely does not yet exist. |
We do now support The original ask is to support something like:
|
when the only value was "value", there was a simple way to create a dynamic CQ when backreferencing
:measurement
however the new format telegraf uses seems to break this.https://docs.influxdata.com/influxdb/v0.10/query_language/continuous_queries/#cqs-with-backreferencing
I'm wondering if there is a better way to do this so sub measurements are included.
The text was updated successfully, but these errors were encountered: