[influxdb] Is there an equivalent of IN () for the SELECT queries

[tanya . unterberger]

Hi, 

I was wondering whether there is an equivalent of 

SELECT * FROM measurement WHERE tag in ('a', 'b', 'c')

I can write an OR query of course, but if there are more than a couple of 
options, it becomes quite tedious to dynamically construct a query.

Thanks :)

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to influxdb+unsubscr...@googlegroups.com.
To post to this group, send email to influxdb@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/e2557f5a-ec7c-4f5b-9e17-782e8c774600%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] What happens to telegraf when there is no internet?

[Peng Wei]

I have installed Influx on a AWS instance.  I have configured telegraf to 
write to it.  What happens when there is no internet? Does telegraf drop 
messages it can't send? Or does it keep them buffered somewhere and retries?
>From the documentation I found metric_buffer_limit.  Is it used to buffer 
data locally if telegraf can't reach it's destination?  What happens when 
the buffer is full? Does it drop older messages and add new messages to the 
buffer? Or does it drop new messages?

Thank you.

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to influxdb+unsubscr...@googlegroups.com.
To post to this group, send email to influxdb@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/2ecdf506-a2f0-46c2-99a2-a671586a0318%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Re: filter data to be written to a measurement

[Sean Beckett]

Could be a duplicate point issue. InfluxDB does not store multiple copies
of a point. If each load injector is sending identical points with
identical timestamps, that's all going to end up as one record in the
system. Use a tag to differentiate the load injectors if that is in fact
the issue.

https://docs.influxdata.com/influxdb/v0.13/troubleshooting/frequently_encountered_issues/#writing-duplicate-points

On Thu, Sep 1, 2016 at 2:00 PM,  wrote:

> Hi Aidy,
>
> First of all, I would like to thank you for documenting this thoroughly. I
> was able to set this up pretty quickly by following your guide.
>
> I have a question about how influxdb ingests data from multiple sources.
> We have 4 load injectors in our setup all running the SAME test and
> shipping stats to influxdb. I'm observing the same throughput through
> grafana regardless of the number of load injectors I am running, while the
> ELB logs clearly displayed higher throughput proportional to the number of
> load injectors running.
>
> Part of this might be my lack of understanding on how time series
> databases work, but it seems influxdb is not aggregating data correctly, as
> least in this set up. I was wondering if you have any input on this. Any
> help would be greatly appreciated.
>
> Thanks!
> Wei
>
>
> On Wednesday, March 9, 2016 at 10:06:47 AM UTC-5, Adrian Lewis wrote:
> > Hi Michael
> >
> >
> >
> > > the template ... is working fine for me. I'd check your file for the
> special characters. When I went to copy any paste the example you gave, it
> had a couple special quotes.
> >
> > Yes, thanks. I replaced the special characters with double quotes. Is
> #facepalm still a tag?
> >
> >
> > > It may not be possible to prevent data with certain tags from being
> written
> >
> >
> > Your solution is fine. I don't care if the data is written, just as long
> as it isn't written to the gatling measurement.
> >
> >
> > I will write your suggestions up here, if you do not mind.
> > https://github.com/bbc/notes-on-perf-testing/blob/master/
> ch/gatling/real_time_graphs.md
> >
> >
> >
> > Thanks for your help.
> >
> >
> > Aidy
>
> --
> Remember to include the InfluxDB version number with all issue reports
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to influxdb+unsubscr...@googlegroups.com.
> To post to this group, send email to influxdb@googlegroups.com.
> Visit this group at https://groups.google.com/group/influxdb.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/influxdb/61682d8a-0153-4d4c-8412-65459d60dd1a%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Sean Beckett
Director of Support and Professional Services
InfluxDB

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to influxdb+unsubscr...@googlegroups.com.
To post to this group, send email to influxdb@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/CALGqCvNKSSsrwEEpDtvvwrGpRTegJ541%3DZ5-nbapwVYjg_6%3DsA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] InfluxDB .10 - drop measurement strange behavior

[Sean Beckett]

On Thu, Sep 1, 2016 at 9:53 AM, bsharma  wrote:

> Having two issues ...
>
> 1) Measurements that were deleted seem to have 're-appeared' after restart
> of Influx. Is this possible?


InfluxDB 0.10 is a very out-of-date version which introduced the new
storage engine. Bugs with DROP and DELETE are common. Please upgrade to the
latest InfluxDB 0.13 or a 1.0 release candidate.


> 2) 'show measurements' seems to consistently show no more than ~ 10,000
> measures.
>

Probably
https://docs.influxdata.com/influxdb/v0.10/troubleshooting/frequently_encountered_issues/#getting-large-query-returns-in-batches-when-using-the-http-api


>
> --
> Remember to include the InfluxDB version number with all issue reports
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to influxdb+unsubscr...@googlegroups.com.
> To post to this group, send email to influxdb@googlegroups.com.
> Visit this group at https://groups.google.com/group/influxdb.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/influxdb/6ad8a6c2-2bd0-4c1e-8ff6-a193be27ec23%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Sean Beckett
Director of Support and Professional Services
InfluxDB

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to influxdb+unsubscr...@googlegroups.com.
To post to this group, send email to influxdb@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/CALGqCvNbRCgyaPK3kmVFYJ5hB2fQ7JZD%2BM8ubp-gYieUg6vx0Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Telegraf issue: data points missing when using procstat with multi pids

[Sean Beckett]

Thanks for the GitHub issue. We will follow up there.

On Wed, Aug 31, 2016 at 8:01 PM,  wrote:

> This issue has been initially posted on github telegraf issues several
> days ago, got no reply yet. So I repost it here.
>
> link to github issue: https://github.com/influxdata/telegraf/issues/1668
>
> Details:
>
> ## Bug report
>
> When using prostat plugin with pattern matching, if it matches multi pids,
> multi data points are generated with **identical tags and timestamp**. when
> these points are sent to influxdb, only the last point was stored
> correctly, former points will be overwritten repeatedly.
>
> This will result in only one pid's data will be found in the database,
> instead of one point per pid.
>
> ### Relevant telegraf.conf:
>
> [[input:procstat]]
> # Use pattern matching
> pattern = "ANY PATTERN MATCHING MULTI PIDS"
>
> ### System info:
>
> telegraf-1.0.0-beta3_linux_amd64
>
> ### Steps to reproduce:
>
> 1. Use prostat input's pattern matching method, match multi pids.
> 2. Produce to influxdb output
>
> ### Expected behavior:
>
> One data point per pid will be written to database.
>
> ### Actual behavior:
>
> Only the last pid data point can be found, others got overwritten.
>
> ### Additional info:
>
> - [Influxdb Issue on data rewritten](https://github.com/
> influxdata/influxdb/issues/1920)
>
> ---
>
> Looking forward to your replay, thank you.
>
> --
> Remember to include the InfluxDB version number with all issue reports
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to influxdb+unsubscr...@googlegroups.com.
> To post to this group, send email to influxdb@googlegroups.com.
> Visit this group at https://groups.google.com/group/influxdb.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/influxdb/855001cf-f028-4e95-996f-07c4de82e0d3%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Sean Beckett
Director of Support and Professional Services
InfluxDB

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to influxdb+unsubscr...@googlegroups.com.
To post to this group, send email to influxdb@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/CALGqCvN_9fjOT_H6mS0usUz%2BTAUAfoaoTLvu0-XXTm67CZ2M2Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Re: Median Window tick Script

[nathaniel]

Glad its working. My best guess as to why it wasn't working before is the 
difference between the `.` and the `|` operators.

The `|` means add a new node to the task DAG, or in other words add a new 
step. The `.` means change a property of an existing step/node.

Since performing a median action is a new step in the task pipeline it 
requires the `|` operator. Using `.meadian` would have resulted in an error 
that the property function didn't exist, but should have also suggested 
using `|` since that function does.

If I am off, just ignore me ;)

On Thursday, September 1, 2016 at 11:35:16 AM UTC-6, Bubba Hines wrote:
>
> This seems to work, but I swear I tried something very similar and got 
> `function median not defined` ... but copy/paste this and it runs.
>

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to influxdb+unsubscr...@googlegroups.com.
To post to this group, send email to influxdb@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/421024ba-e799-47cd-aa78-d7fa16ca8c8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Re: Median Window tick Script

[Bubba Hines]

This seems to work, but I swear I tried something very similar and got 
`function median not defined` ... but copy/paste this and it runs.

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to influxdb+unsubscr...@googlegroups.com.
To post to this group, send email to influxdb@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/da3f66ce-6c60-4a09-b5b7-87bf9bb8b6bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Re: Median Window tick Script

[nathaniel]

Try this:

stream
// Select just the queue count measurement from our database.
|from()
.database('service')
.retentionPolicy('default')
.measurement('httpjson_flash_conversion_workers')
|window()
.period(5m)
.every(5m)
|median('queued')
.as('queued')
|alert()
.id('IronWorker Conversions Queue')
.message('{{ .ID }} is {{ .Level }} messages queued:{{ index 
.Fields "queued" }}')
.info(lambda: "queued" >  100)
.warn(lambda: "queued" >  250)
.crit(lambda: "queued" >  500)
.stateChangesOnly()
// Whenever we get an alert write it to slack
.slack()
.channel('#dev')



On Thursday, September 1, 2016 at 9:11:22 AM UTC-6, Bubba Hines wrote:
>
> I currently have tick script like so:
>
>
> stream
> // Select just the queue count measurement from our database.
> |from()
> .database('service')
> .retentionPolicy('default')
> .measurement('httpjson_flash_conversion_workers')
> |alert()
> .id('IronWorker Conversions Queue')
> .message('{{ .ID }} is {{ .Level }} messages queued:{{ index 
> .Fields "queued" }}')
> .info(lambda: "queued" >  100)
> .warn(lambda: "queued" >  250)
> .crit(lambda: "queued" >  500)
> .stateChangesOnly()
> // Whenever we get an alert write it to slack
> .slack()
> .channel('#dev')
>
>
> I'd like to convert it so that it alerts when the median message count has 
> been above the levels for a period of time (demonstrating that the queue is 
> backed up), say 5 minutes. I'm struggling to comprehend how the .window() 
> and .median() nodes can be combined to achieve this. I'd certainly 
> appreciate any assistance and pointers to documentation demonstrating 
> something like this.
>

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to influxdb+unsubscr...@googlegroups.com.
To post to this group, send email to influxdb@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/1bd78194-4973-4bb0-9078-dd64f2e3244e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Re: Kapacitor global dead man switch

[nathaniel]

Have you defined any tasks? The global options apply to all tasks, but it 
you don't have any tasks then nothing will happen. 

Based on this: 

>I'm trying to use kapacitor to warn us if one of the measurements (in 
different databases) on the influxdb doesn't receive any data.

My suggestion would be to create a task per database/measurement you have. 
If you have lots of them then task templates (a 1.0 feature) are a good 
solution to managing them all.

On Thursday, September 1, 2016 at 1:33:25 AM UTC-6, Bart Verleye wrote:
>
> Hi,
>
> I'm trying to use kapacitor to warn us if one of the measurements (in 
> different databases) on the influxdb doesn't receive any data.
>
> I installed kapacitor, and made changes in the config:
>
> - deadman, set global true
>
> - influxdb, added credentials 
>
> - added api for opsgenie and slack, and set them to global true. 
>
> As everything is set to global, I would expect this to work, but when I 
> start kapacitor, I get the output below, however, no warnings. 
>
> Thanks,
> Bart
>
> [run] 2016/08/31 15:39:57 I! Kapacitor starting, version 0.13.1, branch 
> master, commit ae7dde3aa467c46c06a5a2058a80c6125203f599
> [run] 2016/08/31 15:39:57 I! Go version go1.6.2, GOMAXPROCS set to 2
> [srv] 2016/08/31 15:39:57 I! Kapacitor hostname: localhost
> [srv] 2016/08/31 15:39:57 I! ClusterID: ** ServerID: **
> [task_master] 2016/08/31 15:39:57 I! opened
> [deadman] 2016/08/31 15:39:57 I! Deadman's switch is configured globally
> [influxdb] 2016/08/31 15:39:57 I! linking subscriptions
> [udp:db1.default] 2016/08/31 15:39:57 I! Started listening on UDP: 
> 127.0.0.1:54630
> [influxdb] 2016/08/31 15:39:57 I! started UDP listener for db1 default
> [udp:tes01.default] 2016/08/31 15:39:57 I! Started listening on UDP: 
> 127.0.0.1:59663
> [influxdb] 2016/08/31 15:39:57 I! started UDP listener for tes01 default
> [udp:db2.default] 2016/08/31 15:39:57 I! Started listening on UDP: 
> 127.0.0.1:46834
> [influxdb] 2016/08/31 15:39:57 I! started UDP listener for db2 default
> [udp:testenv.default] 2016/08/31 15:39:57 I! Started listening on UDP: 
> 127.0.0.1:32982
> [influxdb] 2016/08/31 15:39:57 I! started UDP listener for testenv default
> [udp:_internal.monitor] 2016/08/31 15:39:57 I! Started listening on UDP: 
> 127.0.0.1:55836
> [influxdb] 2016/08/31 15:39:57 I! started UDP listener for _internal 
> monitor
> [task_store] 2016/08/31 15:39:57 W! could not open old boltd for 
> task_store. Not performing migration. Remove the `task_store.dir` 
> configuration to disable migration.
> [stats] 2016/08/31 15:39:57 I! opened service
> [httpd] 2016/08/31 15:39:57 I! Starting HTTP service
> [httpd] 2016/08/31 15:39:57 I! Authentication enabled: true
> [httpd] 2016/08/31 15:39:57 I! Listening on HTTP: [::]:9092
> [run] 2016/08/31 15:39:57 I! Listening for signals
>

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to influxdb+unsubscr...@googlegroups.com.
To post to this group, send email to influxdb@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/c226ca24-e918-485c-b833-d1302ae3aa15%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Median Window tick Script

[Bubba Hines]

I currently have tick script like so:


stream
// Select just the queue count measurement from our database.
|from()
.database('service')
.retentionPolicy('default')
.measurement('httpjson_flash_conversion_workers')
|alert()
.id('IronWorker Conversions Queue')
.message('{{ .ID }} is {{ .Level }} messages queued:{{ index 
.Fields "queued" }}')
.info(lambda: "queued" >  100)
.warn(lambda: "queued" >  250)
.crit(lambda: "queued" >  500)
.stateChangesOnly()
// Whenever we get an alert write it to slack
.slack()
.channel('#dev')


I'd like to convert it so that it alerts when the median message count has 
been above the levels for a period of time (demonstrating that the queue is 
backed up), say 5 minutes. I'm struggling to comprehend how the .window() 
and .median() nodes can be combined to achieve this. I'd certainly 
appreciate any assistance and pointers to documentation demonstrating 
something like this.

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to influxdb+unsubscr...@googlegroups.com.
To post to this group, send email to influxdb@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/a9995f5b-9396-4b71-8abf-ede2f812a504%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Kapacitor global dead man switch

[Bart Verleye]

Hi,

I'm trying to use kapacitor to warn us if one of the measurements (in 
different databases) on the influxdb doesn't receive any data.

I installed kapacitor, and made changes in the config:

- deadman, set global true

- influxdb, added credentials 

- added api for opsgenie and slack, and set them to global true. 

As everything is set to global, I would expect this to work, but when I 
start kapacitor, I get the output below, however, no warnings. 

Thanks,
Bart

[run] 2016/08/31 15:39:57 I! Kapacitor starting, version 0.13.1, branch 
master, commit ae7dde3aa467c46c06a5a2058a80c6125203f599
[run] 2016/08/31 15:39:57 I! Go version go1.6.2, GOMAXPROCS set to 2
[srv] 2016/08/31 15:39:57 I! Kapacitor hostname: localhost
[srv] 2016/08/31 15:39:57 I! ClusterID: ** ServerID: **
[task_master] 2016/08/31 15:39:57 I! opened
[deadman] 2016/08/31 15:39:57 I! Deadman's switch is configured globally
[influxdb] 2016/08/31 15:39:57 I! linking subscriptions
[udp:db1.default] 2016/08/31 15:39:57 I! Started listening on UDP: 
127.0.0.1:54630
[influxdb] 2016/08/31 15:39:57 I! started UDP listener for db1 default
[udp:tes01.default] 2016/08/31 15:39:57 I! Started listening on UDP: 
127.0.0.1:59663
[influxdb] 2016/08/31 15:39:57 I! started UDP listener for tes01 default
[udp:db2.default] 2016/08/31 15:39:57 I! Started listening on UDP: 
127.0.0.1:46834
[influxdb] 2016/08/31 15:39:57 I! started UDP listener for db2 default
[udp:testenv.default] 2016/08/31 15:39:57 I! Started listening on UDP: 
127.0.0.1:32982
[influxdb] 2016/08/31 15:39:57 I! started UDP listener for testenv default
[udp:_internal.monitor] 2016/08/31 15:39:57 I! Started listening on UDP: 
127.0.0.1:55836
[influxdb] 2016/08/31 15:39:57 I! started UDP listener for _internal monitor
[task_store] 2016/08/31 15:39:57 W! could not open old boltd for 
task_store. Not performing migration. Remove the `task_store.dir` 
configuration to disable migration.
[stats] 2016/08/31 15:39:57 I! opened service
[httpd] 2016/08/31 15:39:57 I! Starting HTTP service
[httpd] 2016/08/31 15:39:57 I! Authentication enabled: true
[httpd] 2016/08/31 15:39:57 I! Listening on HTTP: [::]:9092
[run] 2016/08/31 15:39:57 I! Listening for signals

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to influxdb+unsubscr...@googlegroups.com.
To post to this group, send email to influxdb@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/52b0a22c-f207-4651-9bad-bea8ee5b91cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.