[influxdb] Re: Setting up SSL with InfluxDB

[ddascalescu]

2016 Update:

Setting up SSL can very easily be done with LetsEncrypt. Please see this post:

https://groups.google.com/d/msg/influxdb/Xf8fLoRIJXc/POJ00_l2AwAJ

-- 
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/18cfcbda-b2dd-403c-99b0-e3f78c45a209%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Re: InfluxDB & letsencrypt

[ddascalescu]

On Thursday, August 25, 2016 at 10:49:37 AM UTC-7, Emiliano Heyns wrote:
> I've installed the nightly from the centos rpm, I don't know where the logs 
> are being redirected to honestly.

On Ubuntu 15.04+, logs go to the newfangled journald, and you can display them 
with:

journalctl -u influxdb.service

To troubleshoot the error, you can also just iterate through editing 
`/etc/influxdb/influxdb/conf` and running just `influxd`, which will dump 
messages to STDERR.

InfluxDB can use the LetsEncrypt cert.pem and privkey.pem files in 
/etc/influxdb/influxdb.conf:

  https-certificate = "/etc/letsencrypt/live/yourdomain/cert.pem"
  https-private-key = "/etc/letsencrypt/live/yourdomain/privkey.pem"

This only works now for the [http] section, not for [admin], and isn't 
documented yet. More at https://github.com/influxdata/influxdb/issues/7283.

-- 
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/5d706ad7-0fce-45a3-8089-c44fd2e6ed26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Re: Aggregating samples when interval in GROUP BY time() is not the same as metric resolution

[higels]

Running 1.0 and Grafana 3.1.1.

-- 
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/61d7a2ab-e8fd-4999-81f2-35120693bb91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Aggregating samples when interval in GROUP BY time() is not the same as metric resolution

[higels]

Hi,

I think the answer to this question is "use CQ", but it seems like an obvious 
use case so maybe I've overlooked a better solution:

I have series collected every minute detailing the number of users per service 
per region. Let's say the measurement is called online_users with tags service 
and region. A region can have more than one service.

I want to view the total number of users in a region in the last day:

SELECT sum(value) FROM online_users WHERE region='xyz' AND time > NOW() - 1d

I get my back expected results with 1 sample per minute with a sum of all users 
in all services in that region. All good so far.

When I use Grafana and want to let it choose an appropriate interval (say 10 
minutes), I would probably try this first:

SELECT sum(value) FROM online_users WHERE region='xyz' AND time > NOW() - 1d 
GROUP BY time(10m)

But this will give me the sum of all samples in that 10 minute period, 
effectively multiplying my results by 10. I could just divide by 10, but I 
don't have a way of conveniently being able to derive the number of expected 
samples per $interval.

I could also take the mean and multiply it by the number of services, but I 
don't think a COUNT(DISTINCT()) works on tags.

sum(mean()) gets thrown out by the parser.

As I mentioned, this is something I do commonly in other TSDBs so I'm hoping 
I'm missing something obvious.

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/133633cd-4010-4a5c-88db-68b97f73e393%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Retention Policy

[Sean Beckett]

As long as you only have hundreds or low thousands of users it should be
okay. Each database incurs a fixed filesystem and RAM cost, but they aren't
very high.

On Tue, Sep 6, 2016 at 8:49 PM, Mathias Herberts  wrote:

> Thanks, the 'database per user' approach seems indeed the most appropriate.
>
> On Tuesday, September 6, 2016 at 11:44:30 PM UTC+2, Sean Beckett wrote:
>>
>> Retention policies are enforced based on the timestamp of the point, not
>> when the point was written. There is no way in the system to drop data
>> based on write time. Presumably you could give each user their own
>> database, or databases, and when the time limit has expired, simply DROP
>> DATABASE.
>>
>> On Tue, Sep 6, 2016 at 3:29 PM, Mathias Herberts 
>> wrote:
>>
>>> I was wondering if RPs only took into consideration the timestamps of
>>> the datapoints or if they could be configured to consider the time at which
>>> the data was inserted into the db.
>>>
>>> My question is to understand how RPs should be enforced for users who
>>> want to insert large historical datasets covering several years but should
>>> not be allowed to keep the data they uploaded past a certain amount of time.
>>>
>>> If RPs are not the way to go, how could this be done?
>>>
>>> --
>>> 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+u...@googlegroups.com.
>>> To post to this group, send email to infl...@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/ms
>>> gid/influxdb/d11bb8f6-facc-4bf1-b67d-54c9b45718c3%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/b261ad0d-4f05-4b06-8c26-5e785f3203d3%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/CALGqCvPmE43UqnQzt5_puYvCMZPGcBvf8qX7bi7au_5gY4OPEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Re: influx 0.13 cli connecting to a remote 0.12.2 server

[kkulkarn]

On Monday, June 6, 2016 at 3:50:22 PM UTC-4, Clayton Dukes wrote:
> Scratch that. I had upgraded the server, but had not restarted it. A simple 
> "service influxdb restart" resolved it :)
> 
> 
> 
> 
> 
> __ 
> 
> Clayton Dukes
> __
> 
> 
> On Mon, Jun 6, 2016 at 1:16 PM,   wrote:
> On Monday, June 6, 2016 at 12:49:05 PM UTC-4, efu...@blueorigin.com wrote:
> 
> > I'm getting the same error on a .13 server with .13 client.
> 
> 
> 
> Same here
> 
> 
> 
> --
> 
> Remember to include the InfluxDB version number with all issue reports
> 
> ---
> 
> You received this message because you are subscribed to a topic in the Google 
> Groups "InfluxDB" group.
> 
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/influxdb/EmNuCoFHHiU/unsubscribe.
> 
> To unsubscribe from this group and all its topics, send an email to 
> influxdb+u...@googlegroups.com.
> 
> To post to this group, send email to infl...@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/061c6aeb-1a5f-4b87-bf0d-a7d4b11779d4%40googlegroups.com.
> 
> For more options, visit https://groups.google.com/d/optout.

This worked for me when I did "service influxdb restart" error was gone.

-- 
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/ca14e594-30f9-4530-90df-c7bb17cc7f39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Multiple points not getting written to influxdb

[indranilr]

Thanks Sean for the clarification.I shall try with millisecond/nanosecond 
time stamp.

On Thursday, September 8, 2016 at 9:11:09 AM UTC+5:30, Sean Beckett wrote:
>
> When no explicit timestamp is supplied, InfluxDB applies the same 
> timestamp to all points in the batch. Since all points belong to the same 
> series, InfluxDB treats them as duplicate points, and stores the union of 
> the points, with the last field winning.
>
>
> https://docs.influxdata.com/influxdb/v0.13/troubleshooting/frequently_encountered_issues/#writing-duplicate-points
>
> To avoid this, you need to explicitly supply timestamps (preferred) or 
> write the points in separate batches so they will inherit unique nanosecond 
> timestamps. Note that not batching writes will lead to significantly 
> reduced write throughput, due to the high HTTP overhead.
>
> On Wed, Sep 7, 2016 at 7:46 AM, indranilr  > wrote:
>
>> I am consuming messages from per-populated Kafka topic and trying to POST 
>> to influxdb (tried via telegraf and node.js client) but seeing that 
>> multiple POSTs issued in short span of time is not getting reflected in 
>> influxdb database.I wasn't sure if this is an actual bug or an issue with 
>> some configuration in my code.Kindly advise.
>>
>> Following are the points I have populated in Kafka queue :
>>
>> {"value":40,"host":"host1"} 
>> {"value":50,"host":"host1"} 
>> {"value":60,"host":"host1"} 
>> {"value":70,"host":"host1"} 
>> {"value":80,"host":"host1"} 
>> Once node.js client consumes (using kafka-node) the same it writes it to 
>> influx (using node-influx)  using *writePoint *method (post some parsing)
>>
>> influxClient.writePoint(target_metric, {value : vl}, {host :  ht} , {db:
>> db_name},callback);
>>
>> Please note* no timestamp* is being sent to influx.
>>
>> However, when I check in target influx measurements I only fewer points 
>> than originally sent (you can see only 4 points below).
>>
>> name: test_ms_1
>> ---
>> timehostvalue
>> 147325124183500 host1   40
>> 147325124183800 host1   80
>> 147325124186000 host1   60
>> 147325124186100 host1   50
>>
>>
>> Could anyone explain the above behavior is due to missing timestamp in 
>> input data or something else is wrong.
>>
>> I checked influx log and I can see equivalent number of POST queries and 
>> relevant message bodies (I have turned on body tracing)
>>
>> [httpd] 2016/09/07 17:57:21 write body received by handler: 
>>> test_ms_1,host=host1 value=40
>>> [tsm1wal] 2016/09/07 17:57:21 tsm1 WAL starting with 10485760 segment 
>>> size
>>> [tsm1wal] 2016/09/07 17:57:21 tsm1 WAL writing to 
>>> /var/lib/influxdb/wal/eridb6/default/12
>>> [shard] 2016/09/07 17:57:21 /var/lib/influxdb/data/eridb6/default/12 
>>> database index loaded in 986ns
>>> [httpd] 2016/09/07 17:57:21 write body received by handler: 
>>> test_ms_1,host=host1 value=80
>>> [httpd] 2016/09/07 17:57:21 write body received by handler: 
>>> test_ms_1,host=host1 value=70
>>> [httpd] 2016/09/07 17:57:21 write body received by handler: 
>>> test_ms_1,host=host1 value=60
>>> [httpd] 2016/09/07 17:57:21 write body received by handler: 
>>> test_ms_1,host=host1 value=50
>>> [httpd] 2016/09/07 17:57:21 10.0.2.2 - root [07/Sep/2016:17:57:21 +0530] 
>>> POST /write?database==eridb6=%5BREDACTED%5D=ms=root 
>>> HTTP/1.1 204 0 - - 6cd985c1-74f6-11e6-8013- 26.071054ms
>>> [httpd] 2016/09/07 17:57:21 10.0.2.2 - root [07/Sep/2016:17:57:21 +0530] 
>>> POST /write?database==eridb6=%5BREDACTED%5D=ms=root 
>>> HTTP/1.1 204 0 - - 6cda049b-74f6-11e6-8014- 29.699655ms
>>> [httpd] 2016/09/07 17:57:21 10.0.2.2 - root [07/Sep/2016:17:57:21 +0530] 
>>> POST /write?database==eridb6=%5BREDACTED%5D=ms=root 
>>> HTTP/1.1 204 0 - - 6cdd57e2-74f6-11e6-8015- 10.920647ms
>>> [httpd] 2016/09/07 17:57:21 10.0.2.2 - root [07/Sep/2016:17:57:21 +0530] 
>>> POST /write?database==eridb6=%5BREDACTED%5D=ms=root 
>>> HTTP/1.1 204 0 - - 6cdd765b-74f6-11e6-8016- 11.097619ms
>>
>> [httpd] 2016/09/07 17:57:21 10.0.2.2 - root [07/Sep/2016:17:57:21 +0530] 
>>> POST /write?database==eridb6=%5BREDACTED%5D=ms=root 
>>> HTTP/1.1 204 0 - - 6cdd7c1a-74f6-11e6-8017- 11.845628ms
>>>
>>>
>> I am using influx 0.13 on CentOS Linux release 7.2.1511 (Core) (64 bit) 
>> on Virtual box:
>>
>>  Static hostname: localhost.centos
>>  Icon name: computer-vm
>>  Chassis: vm
>>  Machine ID: XX
>>  Boot ID: 
>>  Virtualization: kvm
>>  Operating System: CentOS Linux 7 (Core)
>>  CPE OS Name: cpe:/o:centos:centos:7
>>  Kernel: Linux 3.10.0-327.el7.x86_64
>>  Architecture: x86-64
>>  
>> System resources :
>>
>> *Memory :*
>>
>> MemTotal:1016860 kB
>> MemFree:  699836 kB
>> MemAvailable: 716180 kB
>> Cached:   126384 kB
>> SwapCached:0 kB
>> SwapTotal:839676 kB
>> SwapFree: 839676 kB
>>
>>
>> *CPU:*
>>
>> cache size  : 

Re: [influxdb] Re: influx 0.13 cli connecting to a remote 0.12.2 server

[kkulkarn]

On Monday, June 6, 2016 at 3:50:22 PM UTC-4, Clayton Dukes wrote:
> Scratch that. I had upgraded the server, but had not restarted it. A simple 
> "service influxdb restart" resolved it :)
> This solution worked for me as well after few hours of useless attempts.
> 
> 
> 
> 
> __ 
> 
> Clayton Dukes
> __
> 
> 
> On Mon, Jun 6, 2016 at 1:16 PM,   wrote:
> On Monday, June 6, 2016 at 12:49:05 PM UTC-4, efu...@blueorigin.com wrote:
> 
> > I'm getting the same error on a .13 server with .13 client.
> 
> 
> 
> Same here
> 
> 
> 
> --
> 
> Remember to include the InfluxDB version number with all issue reports
> 
> ---
> 
> You received this message because you are subscribed to a topic in the Google 
> Groups "InfluxDB" group.
> 
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/influxdb/EmNuCoFHHiU/unsubscribe.
> 
> To unsubscribe from this group and all its topics, send an email to 
> influxdb+u...@googlegroups.com.
> 
> To post to this group, send email to infl...@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/061c6aeb-1a5f-4b87-bf0d-a7d4b11779d4%40googlegroups.com.
> 
> For more options, visit https://groups.google.com/d/optout.

-- 
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/427d368d-4847-457d-80dc-55c6f137a7c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] BUG? bug in rc1, not in v13. Duplicate and erroneous data returned. Anyone else getting this ?

[ian lutz]

#7263
added (belatedly) on gitbhub 7263
https://github.com/influxdata/influxdb/issues/7263

cheers,
Ian

On Tuesday, 30 August 2016 05:28:56 UTC+10, Sean Beckett wrote:
>
> This is not an issue I recall seeing before. Please open a bug report on 
> the repo: https://github.com/influxdata/influxdb/issues/new.
>
> On Sun, Aug 28, 2016 at 8:57 PM, ian lutz  
> wrote:
>
>> Hi All. Please observe the below, it looks like i have hit a bug. Anyone 
>> else getting this ?
>>
>> both dbs have the same data in it.
>>
>> On  v1-rc1 and on v13 we get this: (the same for both)  -> CORRECT
>>
>>
>>
>> SELECT "time", value_EIGAI, status FROM "egtesta-c1" WHERE "time" <= 
>> 145367999ms ORDER BY time DESC LIMIT 1
>> name: egtesta-c1
>> 
>> timevalue_EIGAI status
>> 14536764000 -23.087604422453467 OK
>>
>>
>>
>>
>>
>> now, lets try and query for another measurement as well:
>>
>>
>>
>> for v1-rc1 we get this, which is the bug: -> we are getting more results 
>> than we expect. We expect a result for each measurement. -> INCORRECT
>>
>> > SELECT "time", value_EIGAI, status FROM "egtesta-c1", "egtesta-a1" 
>> WHERE "time" <= 145367999ms ORDER BY time DESC LIMIT 1
>> name: egtesta-c1
>> 
>> timevalue_EIGAI status
>> 14536764000 -23.087604422453467 OK
>>
>> name: egtesta-a1
>> 
>> timevalue_EIGAI status
>> 14536799900 13.959871755318915  OK
>>
>> name: egtesta-c1
>> 
>> timevalue_EIGAI status
>> 14530716000 -5.323965719289276  OK
>>
>> name: egtesta-a1
>> 
>> timevalue_EIGAI status
>> 14530751900 -6.0113449367000555 OK
>>
>> name: egtesta-c1
>> 
>> timevalue_EIGAI status
>> 14524668000 18.85614054031754   OK
>>
>> name: egtesta-a1
>> 
>> timevalue_EIGAI status
>> 14524703900 -0.2193950233187678 OK
>>
>> name: egtesta-c1
>> 
>> timevalue_EIGAI status
>> 1451862 -7.2098001702068615 OK
>>
>> name: egtesta-a1
>> 
>> timevalue_EIGAI status
>> 14518655900 -3.86140507819  OK
>>
>>
>>
>>
>> for v13, we get what we expect.  -> CORRECT
>>
>>
>>
>> > SELECT "time", value_EIGAI, status FROM "egtesta-c1", "egtesta-a1" 
>> WHERE "time" <= 145367999ms ORDER BY time DESC LIMIT 1
>> name: egtesta-c1
>> 
>> timevalue_EIGAI status
>> 14536764000 -23.087604422453467 OK
>>
>> name: egtesta-a1
>> 
>> timevalue_EIGAI status
>> 14536799900 13.959871755318915  OK
>>
>>
>> Anyone else experiencing this ? Thanks!!
>> Cheers,
>> Ian
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> -- 
>> 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+u...@googlegroups.com .
>> To post to this group, send email to infl...@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/fa586998-e1df-497b-9023-3b53ffb50505%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/9bc36058-6c9f-4bea-8294-8e8abe38ccf7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Database structure

[William Cork]

I figured it out later in the night. Thank you!

- Will

On Thursday, 8 September 2016 09:13:44 UTC-7, Sean Beckett wrote:
>
> SELECT LAST(value) FROM testDB GROUP BY pv
>
> Please review 
> http://docs.influxdata.com/influxdb/v0.13/query_language/data_exploration/ 
> for more on how to use InfluxQL.
>
> On Thu, Sep 8, 2016 at 3:30 AM,  wrote:
>
>> Maybe I'm setting up my db incorrectly.
>>
>> Currently, I have a db set up as such:
>>
>> > CREATE DATABASE "testDB"
>> > INSERT testDB,pv=IOC1_hb,host=host1 value=10
>> > INSERT testDB,pv=IOC1_hb,host=host1 value=11
>> > INSERT testDB,pv=IOC1_hb,host=host1 value=1
>> > INSERT testDB,pv=IOC1_hb,host=host1 value=55
>> > INSERT testDB,pv=IOC2_hb,host=host1 value=10
>> > INSERT testDB,pv=IOC2_hb,host=host1 value=33
>> > INSERT testDB,pv=IOC2_hb,host=host1 value=98
>>
>> Is there a way to select a specific time and get the latest value from 
>> each unique tag (pv) up to that specified time?
>>
>> My efforts in using DISTINCT have failed.
>>
>> (No time limit specified. No LIMIT defined. Returns nothing)
>> > SELECT DISTINCT("pv") FROM testDB
>>
>>
>> Thanks,
>>
>> - Will
>>
>> --
>> 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+u...@googlegroups.com .
>> To post to this group, send email to infl...@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/8cdecefb-be37-46f4-97ea-7600b5787987%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/c68aaf62-4f97-4c5f-b05b-9e3b6eda233e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Retention Policy

[Mathias Herberts]

Thanks, the 'database per user' approach seems indeed the most appropriate.

On Tuesday, September 6, 2016 at 11:44:30 PM UTC+2, Sean Beckett wrote:
>
> Retention policies are enforced based on the timestamp of the point, not 
> when the point was written. There is no way in the system to drop data 
> based on write time. Presumably you could give each user their own 
> database, or databases, and when the time limit has expired, simply DROP 
> DATABASE.
>
> On Tue, Sep 6, 2016 at 3:29 PM, Mathias Herberts  > wrote:
>
>> I was wondering if RPs only took into consideration the timestamps of the 
>> datapoints or if they could be configured to consider the time at which the 
>> data was inserted into the db.
>>
>> My question is to understand how RPs should be enforced for users who 
>> want to insert large historical datasets covering several years but should 
>> not be allowed to keep the data they uploaded past a certain amount of time.
>>
>> If RPs are not the way to go, how could this be done?
>>
>> -- 
>> 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+u...@googlegroups.com .
>> To post to this group, send email to infl...@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/d11bb8f6-facc-4bf1-b67d-54c9b45718c3%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/b261ad0d-4f05-4b06-8c26-5e785f3203d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Re: write failed for shard 35: max series per database exceeded:

[picaudmathieu]

I have change the way I write the data. I have reduce the number of fields. 
It's clearly better. 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/1d04a365-3ca0-472c--517b0a3fdbe0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Re: time difference between first and last entry in windowed stream

[nathaniel]

I have pasted an example below but it might not do what you expect.
The elapsed time will almost always be 10m since that is the period of your 
window, except for  the first 10m where it will still be filling up.
Kapacitor measures time based on the data it sees. This means the window 
will not be emitted until a new point arrives.
If you are expecting the time difference of the window to not be 10m than 
that means that points are arriving less frequently than at 1m intervals. 
In which case emitting the window will be delayed until the next point 
arrives.


var vids = stream
|from()
.measurement('control')
.groupBy('vid')


|window()
.period(10m)
.every(1m)


var mins = vids
|min('ping')
.as('minping')


var first = vids
|first('ping')
.usePointTimes()
.as('ping')


var last = vids
|last('ping')
.usePointTimes()
.as('ping')

first
|union(last)
|elapsed('ping', 1s)
 

On Friday, September 9, 2016 at 7:24:55 AM UTC-6, e.p...@viriciti.com wrote:
>
> I'm trying to get the time difference between the first and the last item 
> within a window of 10 minutes using kapacitor. E.g.
>
> var vids = stream
> |from()
> .measurement('control')
> .groupBy('vid')
>
>
> |window()
> .period(10m)
> .every(1m)
>
>
> var mins = vids
> |min('ping')
> .as('minping')
>
>
> var first = vids
> |first('ping')
>
>
> var last = vids
> |last('ping')
>
>
> It seems that first and last indeed contain the value of 'ping' of the 
> first resp. last time point in the window. 
>
> My question is: is it possible to get the time difference between these 
> two points. 
>
> (too) simply said:  last.time - first.time
>
> 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/080a8a1f-2bcb-42ff-88be-d507c98c0cba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Re: Multiple SNMP input plugins for collecting different data for different hosts

[cameronsparr]

Hi Matt,

can you provide your full config file, the exact commands you are running, and 
the exact output you are getting from each of those.

you can paste them here or put them in a gist: https://gist.github.com/

thanks,
Cam

On Friday, September 9, 2016 at 10:24:39 AM UTC+1, Matt Baker wrote:
> Hi,
> 
> 
> I was after some guidance about having multiple SNMP input plugins.   The 
> reason is that I have lots of different types of machines that I would like 
> to collect different OIDs for.
> 
> 
> I figured maybe the best way was to have separate .conf files under 
> telegraf.d but it while they seemed to load the config they didn't run.  So 
> as a test I put the config back into the main telegraf.conf file and found 
> the same situation.
> 
> 
> Config file:
> 
> 
> 
> [[inputs.snmp]]
> 
>   interval = "10s"
> 
>   agents = [ "192.168.0.1:161", "192.168.0.2:161" ]
> 
>   timeout = "5s"
> 
>   version = 2
> 
>   community = "public"
> 
>   max_repetitions = 50
> 
> 
> 
> 
>   name = "test"
> 
>   [[inputs.snmp.field]]
> 
>   name= "hostname"
> 
>   oid = ".1.3.6.1.2.1.1.5.0"  # sysName
> 
>   is_tag  = true
> 
> 
> [[inputs.snmp]]
>   interval = "10s"
>   agents = [ "192.168.0.3:161" ]
>   timeout = "5s"
>   version = 2
>   community = "public"
>   max_repetitions = 50
> 
> 
>   name = "test"
>   [[inputs.snmp.field]]
>   name= "other"
>   oid = ".1.3.6.1.2.1.1.5.0"
> 
>   is_tag  = true
> 
> 
> 
> 
> The result in the log file looks like:
> 
> 
> * Plugin: snmp, Collection 1
> * Internal: 10s
> 
> 
> 
> > cpu,agent_host=                            (all the stats for the first 
> > [[inputs.snmp]] entry work okay)
> 
> 
> * Plugin: snmp, Collection 1
> 
> 
> * Internal: 10s
> 
> 
> 
> 
> the log then stops. As if the 2nd [[inputs.snmp]] is loaded but not run. No 
> stats are collected for these hosts.
> 
> 
> 
> 
> Is there a correct way to do different collections for different hosts or a 
> better way to achieve 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/0b6c4264-53d2-4d48-8ac0-7b4a2b6089aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Re: are there any logs

[Sean Beckett]

Also
https://docs.influxdata.com/influxdb/v1.0/administration/013_vs_1/#influxdb-logging-change
for this and other changes.

On Fri, Sep 9, 2016 at 10:02 AM, Sean Beckett  wrote:

> To comply with systemd convention, InfluxDB no longer redirects to
> /var/log/influxdb/influxd.log on systemd OSes.
>
> See https://docs.influxdata.com/influxdb/v1.0/administration/logs/#systemd
> for more.
>
> On Fri, Sep 9, 2016 at 4:35 AM,  wrote:
>
>> On Friday, November 8, 2013 at 4:51:57 AM UTC-8, stefand...@gmail.com
>> wrote:
>> > are there any logs for influxdb? where would errors be printed?
>>
>> As of Influx v1.0.0, I can't find any logs in /var/log/influxdb, or in
>> /opt/.
>>
>> `service influxdb status` shows the service is dead, but no indication as
>> to why.
>>
>> I had to run `/usr/bin/influxd -config /etc/influxdb/influxdb.conf` to
>> see the error on STDERR.
>>
>> --
>> 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/ms
>> gid/influxdb/2cf65661-465d-4fbe-9ce3-23d8db0b93fe%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Sean Beckett
> Director of Support and Professional Services
> InfluxDB
>



-- 
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/CALGqCvNWZOF4pDCO-iaWCbMWd6v3CrM0QSL7j5DiZ0HvpCxcCA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Re: are there any logs

[Sean Beckett]

To comply with systemd convention, InfluxDB no longer redirects to
/var/log/influxdb/influxd.log
on systemd OSes.

See https://docs.influxdata.com/influxdb/v1.0/administration/logs/#systemd
for more.

On Fri, Sep 9, 2016 at 4:35 AM,  wrote:

> On Friday, November 8, 2013 at 4:51:57 AM UTC-8, stefand...@gmail.com
> wrote:
> > are there any logs for influxdb? where would errors be printed?
>
> As of Influx v1.0.0, I can't find any logs in /var/log/influxdb, or in
> /opt/.
>
> `service influxdb status` shows the service is dead, but no indication as
> to why.
>
> I had to run `/usr/bin/influxd -config /etc/influxdb/influxdb.conf` to see
> the error on STDERR.
>
> --
> 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/2cf65661-465d-4fbe-9ce3-23d8db0b93fe%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/CALGqCvONOtLtj3x3U9QbbUAX16naxMqDm-TipM1%2BAjgprpioNA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Constantly some CPU load on 0.9

[Sean Beckett]

Even if there is no external write or query load, InfluxDB is writing
statistics about itself back to itself. Any configured continuous queries
will also require resources. In addition, there are housekeeping chores
related to Raft and file compaction that can cause a low steady-state level
of CPU usage.



On Fri, Sep 9, 2016 at 1:46 AM, Teemu Kanstrén  wrote:

> Hello,
>
>  We have a server running InfluxDB v0.9 and "top" is showing the
> "influxdb" process always has some CPU load typically between 5-10%. If I
> understand top output correctly, this is just for a single core so not a
> huge load. But still would be nice to know what might be causing this.
> There are no active queries and monitoring port 8086 shows no traffic. Some
> connections on that port seem to be alive but no data is passed.
>
>  Is there some background process the database on the database that can
> cause the CPU load?
>
>  Updating to a newer version is a possibility but before that I would like
> to understand if this is due to some general architectural feature of
> InfluxDB or maybe something on our end.
>
> Cheers,
> -Teemu
>
> --
> 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/08be5561-697c-496e-a51d-9e4b4a5c9aa5%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/CALGqCvNgzbXS23QsusJT0o7uifzeQ%2Bj3w9gxqnko59EDB2o4LQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Re: kapacitor: panic: runtime error: invalid memory address or nil pointer dereference

[nathaniel]

Can you create an issue 
at https://github.com/influxdata/kapacitor/issues/new and include the new 
stack trace using version 1.0? Thanks

On Friday, September 9, 2016 at 3:52:56 AM UTC-6, Jun Zhang wrote:
>
>
> @nathanielc  , I have upgraded to v1.0.0, 
> but still panic!
>
> On Wednesday, September 7, 2016 at 6:27:41 AM UTC+8, nath...@influxdb.com 
> wrote:
>>
>> This issue has been fixed in the latest version. 
>> https://github.com/influxdata/kapacitor/pull/510 
>> 
>>
>> On Tuesday, September 6, 2016 at 9:52:26 AM UTC-6, Jun Zhang wrote:
>>>
>>> kapacitor RPM info:
>>>
>>> Name : kapacitor
>>> Arch : x86_64
>>> Version : 0.13.1
>>> Release : 1
>>> Size : 41 M
>>> Repo : installed
>>> From repo : /kapacitor-0.13.1.x86_64
>>> Summary : Time series data processing engine
>>> URL : github.com/influxdata/kapacitor
>>> License : MIT
>>> Description : Time series data processing engine
>>>
>>>
>>> TICKscript
>>>
>>> var ping_statistic = stream
>>> |from()
>>> .database('netbench')
>>> .retentionPolicy('default')
>>> .measurement('ping_statistic')
>>> .groupBy('hostName', 'isp', 'province')
>>> |window()
>>> .period(1m)
>>> .every(1m)
>>>
>>> var avgLoss = ping_statistic
>>> |last('avgLoss')
>>> .as('avgLoss')
>>>
>>> avgLoss
>>> |alert()
>>> .crit(lambda: "avgLoss" > 5)
>>> .log('/tmp/alerts_loss.log')
>>>
>>> kapacitor log
>>>
>>> [httpd] 2016/09/06 23:38:04 I! 10.160.109.152 - - [06/Sep/2016:23:38:04 
>>> +0800] GET /kapacitor/v1/tasks/alert_netbench HTTP/1.1 200 5974 - 
>>> curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.21 Basic ECC 
>>> zlib/1.2.3 libidn/1.18 libssh2/1.4.2 e7153ecb-7447-11e6-8014- 
>>> 6.812757ms
>>> [alert_netbench:last3] 2016/09/06 23:39:03 E! failed to aggregate batch: 
>>> field avgLoss missing from point cannot aggregate
>>>
>>> panic message:
>>>
>>> panic: runtime error: invalid memory address or nil pointer dereference
>>> [signal 0xb code=0x1 addr=0x0 pc=0x5f5375]
>>>
>>> goroutine 184 [running]:
>>> panic(0xca0ec0, 0xc820010100)
>>> /usr/local/go/src/runtime/panic.go:481 +0x3e6
>>>
>>> github.com/influxdata/kapacitor/vendor/github.com/influxdata/influxdb/influxql.(
>>>
>>> *FloatFuncReducer).Emit(0xc8202d5490, 0x0, 0x0, 
>>> 0x0)/root/go/src/github.com/influxdata/kapacitor/vendor/github.com/influxdata/influxdb/influxql/functions.gen.go:68
>>>  
>>> 
>>>  
>>> +0xa5github.com/influxdata/kapacitor.( 
>>> *floatPointEmitter).EmitPoint(0xc820b40510,
>>>  
>>> 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
>>> /root/go/src/github.com/influxdata/kapacitor/influxql.gen.go:166 +0x78
>>> github.com/influxdata/kapacitor.(
>>>
>>> *InfluxQLNode).emit(0xc8200e5000, 0x7f3596286140, 0xc820b404e0, 0x0, 
>>> 0x0)/root/go/src/github.com/influxdata/kapacitor/influxql.go:185 
>>>  
>>> +0x90github.com/influxdata/kapacitor.( 
>>> *InfluxQLNode).runBatchInfluxQL(0xc8200e5000,
>>>  
>>> 0x0, 0x0)
>>> /root/go/src/github.com/influxdata/kapacitor/influxql.go:162 +0x62c
>>> github.com/influxdata/kapacitor.(
>>>
>>> *InfluxQLNode).runInfluxQLs(0xc8200e5000, 0x0, 0x0, 0x0, 0x0, 
>>> 0x0)/root/go/src/github.com/influxdata/kapacitor/influxql.go:42 
>>>  
>>> +0x83github.com/influxdata/kapacitor.( 
>>> *InfluxQLNode).(
>>> github.com/influxdata/kapacitor.runInfluxQLs)-fm(0x0, 0x0, 0x0, 0x0, 
>>> 0x0)
>>> /root/go/src/github.com/influxdata/kapacitor/influxql.go:33 +0x4c
>>> github.com/influxdata/kapacitor.(
>>>
>>> *node).start.func1(0xc8200e5000, 0x0, 0x0, 
>>> 0x0)/root/go/src/github.com/influxdata/kapacitor/node.go:128 
>>>  +0x7fcreated by 
>>> github.com/influxdata/kapacitor.( 
>>> *node).start
>>> /root/go/src/github.com/influxdata/kapacitor/node.go:129 +0x53
>>>
>>

-- 
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 

[influxdb] Re: write failed for shard 35: max series per database exceeded:

[picaudmathieu]

Yes, it's more than possible but we also a huge source of information with many 
assets (hundred of switchs with hundred of port, collect each 3 minutes on many 
country/dc/entity.

Thanks for the release not, I have set it in the conf. It's working now.

-- 
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/0faeb38b-fe97-4ea4-88e7-b2d397a977c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Re: write failed for shard 35: max series per database exceeded:

[picaudmathieu]

Do you know how to change this option ?

-- 
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/a9db97fd-8f08-4510-833f-62621308dae4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Re: write failed for shard 35: max series per database exceeded:

[picaudmathieu]

My concern is that I have reached the limit in one week only. 

-- 
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/d18b14ff-b353-4754-bb8e-4ef211c06505%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Re: write failed for shard 35: max series per database exceeded:

[picaudmathieu]

Hello,

Yes 

-- 
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/66adce3e-b329-46db-97df-79276aca1a63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Re: write failed for shard 35: max series per database exceeded:

['Larry Walker' via InfluxDB]

Running the 1.0 GA?  There is a config option to increase the max series.



On Friday, September 9, 2016 at 10:02:42 AM UTC-4, picaud...@gmail.com 
wrote:
>
> Hello,
>
> I'am not able any more to write data in my database because it seems that 
> I have reached the number of series
>
> Sep 09 15:54:46  influxd[30433]: [write] 2016/09/09 15:54:46 write 
> failed for shard 35: max series per database exceeded: 
>
> Here are some information :
>
> Data : nagios,tag1=xxx value=XXX,exectime=XX timestamp
>
> show retention policies on nagios
> namedurationshardGroupDuration  replicaNdefault
> default 24h0m0s 1h0m0s  1   true
> 2Y  17472h0m0s  24h0m0s 1   false
> 1Y  8736h0m0s   24h0m0s 1   false
> 6M  5208h0m0s   12h0m0s 1   false
> 3M  2688h0m0s   12h0m0s 1   false
> 1M  840h0m0s12h0m0s 1   false
> 2w  336h0m0s6h0m0s  1   false
> 1w  168h0m0s3h0m0s  1   false
>
>
>  influx -database 'nagios' -format 'csv' -execute 'SHOW SERIES' | wc -l
> 1000100
>
>
> Hardware : 8 CPU / 32GB
>
> Usage : 
>
> %Cpu(s):  1.9 us,  0.1 sy,  0.0 ni, 97.6 id,  0.3 wa,  0.0 hi,  0.0 si, 
>  0.0 st
> KiB Mem : 32782200 total, 25015696 free,  4116368 used,  3650136 buff/cache
> KiB Swap:  8388604 total,  8388604 free,0 used. 26743180 avail Mem
>
>   PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
> 30433 influxdb  20   0 8474504 4.212g 699284 S   6.2 13.5   6:55.68 influxd
> 1 root  20   0   41756   4192   2368 S   0.0  0.0   0:04.30 systemd
>
> FS have enough space
>
> Is there a way to increase this number ?
>
>

-- 
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/a130fd2d-b689-4c64-b675-2c7e939d153b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] write failed for shard 35: max series per database exceeded:

[picaudmathieu]

Hello,

I'am not able any more to write data in my database because it seems that I 
have reached the number of series

Sep 09 15:54:46  influxd[30433]: [write] 2016/09/09 15:54:46 write 
failed for shard 35: max series per database exceeded: 

Here are some information :

Data : nagios,tag1=xxx value=XXX,exectime=XX timestamp

show retention policies on nagios
namedurationshardGroupDuration  replicaNdefault
default 24h0m0s 1h0m0s  1   true
2Y  17472h0m0s  24h0m0s 1   false
1Y  8736h0m0s   24h0m0s 1   false
6M  5208h0m0s   12h0m0s 1   false
3M  2688h0m0s   12h0m0s 1   false
1M  840h0m0s12h0m0s 1   false
2w  336h0m0s6h0m0s  1   false
1w  168h0m0s3h0m0s  1   false


 influx -database 'nagios' -format 'csv' -execute 'SHOW SERIES' | wc -l
1000100


Hardware : 8 CPU / 32GB

Usage : 

%Cpu(s):  1.9 us,  0.1 sy,  0.0 ni, 97.6 id,  0.3 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem : 32782200 total, 25015696 free,  4116368 used,  3650136 buff/cache
KiB Swap:  8388604 total,  8388604 free,0 used. 26743180 avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
30433 influxdb  20   0 8474504 4.212g 699284 S   6.2 13.5   6:55.68 influxd
1 root  20   0   41756   4192   2368 S   0.0  0.0   0:04.30 systemd

FS have enough space

Is there a way to increase this number ?

-- 
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/4b86d6c9-a772-4eca-a386-92ce16784d8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] time difference between first and last entry in windowed stream

[e . poeze]

I'm trying to get the time difference between the first and the last item 
within a window of 10 minutes using kapacitor. E.g.

var vids = stream
|from()
.measurement('control')
.groupBy('vid')


|window()
.period(10m)
.every(1m)


var mins = vids
|min('ping')
.as('minping')


var first = vids
|first('ping')


var last = vids
|last('ping')


It seems that first and last indeed contain the value of 'ping' of the 
first resp. last time point in the window. 

My question is: is it possible to get the time difference between these two 
points. 

(too) simply said:  last.time - first.time

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/6ac8e824-11f6-43d5-bea6-3db8045a672b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Re: are there any logs

[ddascalescu]

On Friday, November 8, 2013 at 4:51:57 AM UTC-8, stefand...@gmail.com wrote:
> are there any logs for influxdb? where would errors be printed?

As of Influx v1.0.0, I can't find any logs in /var/log/influxdb, or in /opt/.

`service influxdb status` shows the service is dead, but no indication as to 
why.

I had to run `/usr/bin/influxd -config /etc/influxdb/influxdb.conf` to see the 
error on STDERR.

-- 
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/2cf65661-465d-4fbe-9ce3-23d8db0b93fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Re: kapacitor: panic: runtime error: invalid memory address or nil pointer dereference

[Jun Zhang]

@nathanielc  , I have upgraded to v1.0.0, 
but still panic!

On Wednesday, September 7, 2016 at 6:27:41 AM UTC+8, nath...@influxdb.com 
wrote:
>
> This issue has been fixed in the latest version. 
> https://github.com/influxdata/kapacitor/pull/510 
> 
>
> On Tuesday, September 6, 2016 at 9:52:26 AM UTC-6, Jun Zhang wrote:
>>
>> kapacitor RPM info:
>>
>> Name : kapacitor
>> Arch : x86_64
>> Version : 0.13.1
>> Release : 1
>> Size : 41 M
>> Repo : installed
>> From repo : /kapacitor-0.13.1.x86_64
>> Summary : Time series data processing engine
>> URL : github.com/influxdata/kapacitor
>> License : MIT
>> Description : Time series data processing engine
>>
>>
>> TICKscript
>>
>> var ping_statistic = stream
>> |from()
>> .database('netbench')
>> .retentionPolicy('default')
>> .measurement('ping_statistic')
>> .groupBy('hostName', 'isp', 'province')
>> |window()
>> .period(1m)
>> .every(1m)
>>
>> var avgLoss = ping_statistic
>> |last('avgLoss')
>> .as('avgLoss')
>>
>> avgLoss
>> |alert()
>> .crit(lambda: "avgLoss" > 5)
>> .log('/tmp/alerts_loss.log')
>>
>> kapacitor log
>>
>> [httpd] 2016/09/06 23:38:04 I! 10.160.109.152 - - [06/Sep/2016:23:38:04 
>> +0800] GET /kapacitor/v1/tasks/alert_netbench HTTP/1.1 200 5974 - 
>> curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.21 Basic ECC 
>> zlib/1.2.3 libidn/1.18 libssh2/1.4.2 e7153ecb-7447-11e6-8014- 
>> 6.812757ms
>> [alert_netbench:last3] 2016/09/06 23:39:03 E! failed to aggregate batch: 
>> field avgLoss missing from point cannot aggregate
>>
>> panic message:
>>
>> panic: runtime error: invalid memory address or nil pointer dereference
>> [signal 0xb code=0x1 addr=0x0 pc=0x5f5375]
>>
>> goroutine 184 [running]:
>> panic(0xca0ec0, 0xc820010100)
>> /usr/local/go/src/runtime/panic.go:481 +0x3e6
>>
>> github.com/influxdata/kapacitor/vendor/github.com/influxdata/influxdb/influxql.(
>>
>> *FloatFuncReducer).Emit(0xc8202d5490, 0x0, 0x0, 
>> 0x0)/root/go/src/github.com/influxdata/kapacitor/vendor/github.com/influxdata/influxdb/influxql/functions.gen.go:68
>>  
>> 
>>  
>> +0xa5github.com/influxdata/kapacitor.( 
>> *floatPointEmitter).EmitPoint(0xc820b40510,
>>  
>> 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
>> /root/go/src/github.com/influxdata/kapacitor/influxql.gen.go:166 +0x78
>> github.com/influxdata/kapacitor.(
>>
>> *InfluxQLNode).emit(0xc8200e5000, 0x7f3596286140, 0xc820b404e0, 0x0, 
>> 0x0)/root/go/src/github.com/influxdata/kapacitor/influxql.go:185 
>>  
>> +0x90github.com/influxdata/kapacitor.( 
>> *InfluxQLNode).runBatchInfluxQL(0xc8200e5000,
>>  
>> 0x0, 0x0)
>> /root/go/src/github.com/influxdata/kapacitor/influxql.go:162 +0x62c
>> github.com/influxdata/kapacitor.(
>>
>> *InfluxQLNode).runInfluxQLs(0xc8200e5000, 0x0, 0x0, 0x0, 0x0, 
>> 0x0)/root/go/src/github.com/influxdata/kapacitor/influxql.go:42 
>>  
>> +0x83github.com/influxdata/kapacitor.( 
>> *InfluxQLNode).(
>> github.com/influxdata/kapacitor.runInfluxQLs)-fm(0x0, 0x0, 0x0, 0x0, 0x0)
>> /root/go/src/github.com/influxdata/kapacitor/influxql.go:33 +0x4c
>> github.com/influxdata/kapacitor.(
>>
>> *node).start.func1(0xc8200e5000, 0x0, 0x0, 
>> 0x0)/root/go/src/github.com/influxdata/kapacitor/node.go:128 
>>  +0x7fcreated by 
>> github.com/influxdata/kapacitor.( 
>> *node).start
>> /root/go/src/github.com/influxdata/kapacitor/node.go:129 +0x53
>>
>

-- 
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/d02810b3-ee31-49c4-8e96-088a81a5c64e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Multiple SNMP input plugins for collecting different data for different hosts

[Matt Baker]

Hi,

I was after some guidance about having multiple SNMP input plugins.   The 
reason is that I have lots of different types of machines that I would like 
to collect different OIDs for.

I figured maybe the best way was to have separate .conf files under 
telegraf.d but it while they seemed to load the config they didn't run.  So 
as a test I put the config back into the main telegraf.conf file and found 
the same situation.

Config file:

[[inputs.snmp]]

  interval = "10s"

  agents = [ "192.168.0.1:161", "192.168.0.2:161" ]

  timeout = "5s"

  version = 2

  community = "public"

  max_repetitions = 50


  name = "test"

  [[inputs.snmp.field]]

name = "hostname"

oid = ".1.3.6.1.2.1.1.5.0" # sysName

is_tag = true


[[inputs.snmp]]

  interval = "10s"

  agents = [ "192.168.0.3:161" ]

  timeout = "5s"

  version = 2

  community = "public"

  max_repetitions = 50


  name = "test"

  [[inputs.snmp.field]]

name = "other"

oid = ".1.3.6.1.2.1.1.5.0"

is_tag = true



The result in the log file looks like:


* Plugin: snmp, Collection 1

* Internal: 10s

> cpu,agent_host=(all the stats for the 
first [[inputs.snmp]] entry work okay)


* Plugin: snmp, Collection 1

* Internal: 10s



the log then stops. As if the 2nd [[inputs.snmp]] is loaded but not run. No 
stats are collected for these hosts.



Is there a correct way to do different collections for different hosts or a 
better way to achieve 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/e0af1a5a-6fe9-49c4-8c9f-a718513e3489%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[influxdb] Constantly some CPU load on 0.9

[Teemu Kanstrén]

Hello,

 We have a server running InfluxDB v0.9 and "top" is showing the "influxdb" 
process always has some CPU load typically between 5-10%. If I understand 
top output correctly, this is just for a single core so not a huge load. 
But still would be nice to know what might be causing this. There are no 
active queries and monitoring port 8086 shows no traffic. Some connections 
on that port seem to be alive but no data is passed. 

 Is there some background process the database on the database that can 
cause the CPU load? 

 Updating to a newer version is a possibility but before that I would like 
to understand if this is due to some general architectural feature of 
InfluxDB or maybe something on our end.

Cheers,
-Teemu

-- 
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/08be5561-697c-496e-a51d-9e4b4a5c9aa5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.