Re: [influxdb] InfluxDBClientError: 400 in InfluxDB v0.13

[Ross McDonald]

The word "name" is a keyword within InfluxQL, so you have to wrap it in
double-quotes. Do you get the same error if you update the query to the
following (wrapping 'name' in double-quotes)?

> SELECT * FROM bmspoint WHERE time > now() - 10m AND "name" =
'B10_Area3for2_E_MtrEl6_PwrActv'

You can find more information on proper quoting in the InfluxDB
documentation FEI here

.

Thanks,
Ross

On Mon, Jun 13, 2016 at 10:01 PM,  wrote:

> I'm trying to collect data from a particular sensor, so I used the
> following code to retrieve the data.
>
> data = client.query("SELECT * FROM bmspoint WHERE time > now() - 10m AND
> name = 'B10_Area3for2_E_MtrEl6_PwrActv'")
>
>
> Although data does exist for this sensor in this particular time frame, I
> receive the following error.
>
> InfluxDBClientError   Traceback (most recent call last)
>  in ()
>   4 if n.find(request) != -1:
>   5 print ("True")
> > 6 data2 = client.query("SELECT * FROM bmspoint WHERE time >
> now() - 10m AND name = 'B10_Area3for2_E_MtrEl6_PwrActv'")
>   7 print data2
>   8 else:
>
> /Users/3for2/anaconda/lib/python2.7/site-packages/influxdb/_dataframe_client.pyc
> in query(self, query, chunked, database)
>  77
>  78 """
> ---> 79 results = super(DataFrameClient, self).query(query,
> database=database)
>  80 if query.upper().startswith("SELECT"):
>  81 if len(results) > 0:
>
> /Users/3for2/anaconda/lib/python2.7/site-packages/influxdb/client.pyc in
> query(self, query, params, epoch, expected_response_code, database,
> raise_errors)
> 323 params=params,
> 324 data=None,
> --> 325 expected_response_code=expected_response_code
> 326 )
> 327
>
> /Users/3for2/anaconda/lib/python2.7/site-packages/influxdb/client.pyc in
> request(self, url, method, params, data, expected_response_code, headers)
> 246 return response
> 247 else:
> --> 248 raise InfluxDBClientError(response.content,
> response.status_code)
> 249
> 250 def write(self, data, params=None, expected_response_code=204):
>
> InfluxDBClientError: 400: {"error":"error parsing query: found NAME,
> expected identifier, string, number, bool at line 1, char 53"}
>
>
> I did not receive this error when I used other tags. Any advice?
>
> 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/b93de22f-af40-48df-804d-3c570bb01803%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/CAD8sRLD46J39p0jcYYv%3DmSWcRGqWpKqa7H0TuP_twpFn%2BAq-MA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Nanoseconds to Human readable Time Format

[Ross McDonald]

When you are in the `influx` CLI, you can switch the display to
human-readable timestamps by issuing the command:

```
> precision rfc3339
```

Or you can set it before logging into the instance by adding the parameter
`-precision rfc3339` to the CLI option, for example:

```
influx -precision rfc3339
```

Thanks,
Ross

On Tue, Jun 14, 2016 at 11:50 PM, sangkook Noh  wrote:

>
> My Fluxdb Query Result is bellow
> time column formant is nanoseconds
> So I want change the time formant to human readable like next
> How can I change
>
> [root@DBAnode01GH ~]# influx
> > use test
> Using database test
> > select * from cpu;
> name: cpu
> -
> timehostregion  value
> 1465799105917130413 serverA us_west 0.64
>
>
>
> I hopoe
> > select * from cpu;
> name: cpu
> -
> timehostregion  value
> 2016-10-01 12:00:00 serverA us_west 0.64
>
> --
> 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/d6a56784-b636-422e-b5ca-3ddb199e1e91%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/CAD8sRLC%3DaiLUpRq1LjahKqqsvuMaiadCAw6g0vMJ4ODu6Dzq9w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] InfluxDBClientError: 400 in InfluxDB v0.13

[Ross McDonald]

Can you paste the full query and error output? It sounds like there might
be something else off with the query syntax.

Thanks,
Ross

On Tue, Jun 14, 2016 at 8:45 PM, Melissa Flores  wrote:

> When I attempted to use double quotes around 'name' , I received
> "SyntaxError: invalid syntax"
>
> On Tue, Jun 14, 2016 at 10:02 PM, Ross McDonald  wrote:
>
>> The word "name" is a keyword within InfluxQL, so you have to wrap it in
>> double-quotes. Do you get the same error if you update the query to the
>> following (wrapping 'name' in double-quotes)?
>>
>> > SELECT * FROM bmspoint WHERE time > now() - 10m AND "name" =
>> 'B10_Area3for2_E_MtrEl6_PwrActv'
>>
>> You can find more information on proper quoting in the InfluxDB
>> documentation FEI here
>> <https://docs.influxdata.com/influxdb/v0.13/troubleshooting/frequently_encountered_issues/#single-quoting-and-double-quoting-in-queries>
>> .
>>
>> Thanks,
>> Ross
>>
>> On Mon, Jun 13, 2016 at 10:01 PM,  wrote:
>>
>>> I'm trying to collect data from a particular sensor, so I used the
>>> following code to retrieve the data.
>>>
>>> data = client.query("SELECT * FROM bmspoint WHERE time > now() - 10m AND
>>> name = 'B10_Area3for2_E_MtrEl6_PwrActv'")
>>>
>>>
>>> Although data does exist for this sensor in this particular time frame,
>>> I receive the following error.
>>>
>>> InfluxDBClientError   Traceback (most recent call
>>> last)
>>>  in ()
>>>   4 if n.find(request) != -1:
>>>   5 print ("True")
>>> > 6 data2 = client.query("SELECT * FROM bmspoint WHERE time
>>> > now() - 10m AND name = 'B10_Area3for2_E_MtrEl6_PwrActv'")
>>>   7 print data2
>>>   8 else:
>>>
>>> /Users/3for2/anaconda/lib/python2.7/site-packages/influxdb/_dataframe_client.pyc
>>> in query(self, query, chunked, database)
>>>  77
>>>  78 """
>>> ---> 79 results = super(DataFrameClient, self).query(query,
>>> database=database)
>>>  80 if query.upper().startswith("SELECT"):
>>>  81 if len(results) > 0:
>>>
>>> /Users/3for2/anaconda/lib/python2.7/site-packages/influxdb/client.pyc in
>>> query(self, query, params, epoch, expected_response_code, database,
>>> raise_errors)
>>> 323 params=params,
>>> 324 data=None,
>>> --> 325 expected_response_code=expected_response_code
>>> 326 )
>>> 327
>>>
>>> /Users/3for2/anaconda/lib/python2.7/site-packages/influxdb/client.pyc in
>>> request(self, url, method, params, data, expected_response_code, headers)
>>> 246 return response
>>> 247 else:
>>> --> 248 raise InfluxDBClientError(response.content,
>>> response.status_code)
>>> 249
>>> 250 def write(self, data, params=None,
>>> expected_response_code=204):
>>>
>>> InfluxDBClientError: 400: {"error":"error parsing query: found NAME,
>>> expected identifier, string, number, bool at line 1, char 53"}
>>>
>>>
>>> I did not receive this error when I used other tags. Any advice?
>>>
>>> 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/b93de22f-af40-48df-804d-3c570bb01803%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 a topic in the
>> Google Groups "InfluxDB" group.
>> To unsubscribe from this topic, visit
>&g

Re: [influxdb] InfluxDBClientError: 400 in InfluxDB v0.13

[Ross McDonald]

That query doesn't trigger any errors when run from the InfluxDB CLI, so it
might be referring to a Python syntax error. I would also expect to see an
exception if it was an error returned from InfluxDB.

Thanks,
Ross

On Wed, Jun 15, 2016 at 7:44 PM, Melissa Flores  wrote:

> data = client.query("SELECT * FROM bmspoint WHERE time > now() - 10m AND
> "name" = 'B10_Area3for2_E_MtrEl17_PwrActv'")
>
> Output:
>
> File "", line 1
> data = client.query("SELECT * FROM bmspoint WHERE time > now() - 10m AND
> "name" = 'B10_Area3for2_E_MtrEl17_PwrActv'")
> ^ SyntaxError: invalid syntax
>
>
> On Wed, Jun 15, 2016 at 8:39 PM, Ross McDonald  wrote:
>
>> Can you paste the full query and error output? It sounds like there might
>> be something else off with the query syntax.
>>
>> Thanks,
>> Ross
>>
>> On Tue, Jun 14, 2016 at 8:45 PM, Melissa Flores 
>> wrote:
>>
>>> When I attempted to use double quotes around 'name' , I received
>>> "SyntaxError: invalid syntax"
>>>
>>> On Tue, Jun 14, 2016 at 10:02 PM, Ross McDonald 
>>> wrote:
>>>
>>>> The word "name" is a keyword within InfluxQL, so you have to wrap it in
>>>> double-quotes. Do you get the same error if you update the query to the
>>>> following (wrapping 'name' in double-quotes)?
>>>>
>>>> > SELECT * FROM bmspoint WHERE time > now() - 10m AND "name" =
>>>> 'B10_Area3for2_E_MtrEl6_PwrActv'
>>>>
>>>> You can find more information on proper quoting in the InfluxDB
>>>> documentation FEI here
>>>> <https://docs.influxdata.com/influxdb/v0.13/troubleshooting/frequently_encountered_issues/#single-quoting-and-double-quoting-in-queries>
>>>> .
>>>>
>>>> Thanks,
>>>> Ross
>>>>
>>>> On Mon, Jun 13, 2016 at 10:01 PM,  wrote:
>>>>
>>>>> I'm trying to collect data from a particular sensor, so I used the
>>>>> following code to retrieve the data.
>>>>>
>>>>> data = client.query("SELECT * FROM bmspoint WHERE time > now() - 10m
>>>>> AND name = 'B10_Area3for2_E_MtrEl6_PwrActv'")
>>>>>
>>>>>
>>>>> Although data does exist for this sensor in this particular time
>>>>> frame, I receive the following error.
>>>>>
>>>>> InfluxDBClientError   Traceback (most recent call
>>>>> last)
>>>>>  in ()
>>>>>   4 if n.find(request) != -1:
>>>>>   5 print ("True")
>>>>> > 6 data2 = client.query("SELECT * FROM bmspoint WHERE
>>>>> time > now() - 10m AND name = 'B10_Area3for2_E_MtrEl6_PwrActv'")
>>>>>   7 print data2
>>>>>   8 else:
>>>>>
>>>>> /Users/3for2/anaconda/lib/python2.7/site-packages/influxdb/_dataframe_client.pyc
>>>>> in query(self, query, chunked, database)
>>>>>  77
>>>>>  78 """
>>>>> ---> 79 results = super(DataFrameClient, self).query(query,
>>>>> database=database)
>>>>>  80 if query.upper().startswith("SELECT"):
>>>>>  81 if len(results) > 0:
>>>>>
>>>>> /Users/3for2/anaconda/lib/python2.7/site-packages/influxdb/client.pyc
>>>>> in query(self, query, params, epoch, expected_response_code, database,
>>>>> raise_errors)
>>>>> 323 params=params,
>>>>> 324 data=None,
>>>>> --> 325 expected_response_code=expected_response_code
>>>>> 326 )
>>>>> 327
>>>>>
>>>>> /Users/3for2/anaconda/lib/python2.7/site-packages/influxdb/client.pyc
>>>>> in request(self, url, method, params, data, expected_response_code, 
>>>>> headers)
>>>>> 246 return response
>>>>> 247 else:
>>>>> --> 248 raise InfluxDBClientError(response.content,
>>>>> response.status_code)
>>>>> 249
>>>>> 250 def write(self, data, params=None,
>>>>> expected_response_code=204):
>>>>>

Re: [influxdb] Writing UDP data on multiple DBs

[Ross McDonald]

To write to multiple databases, you'll need to add a second UDP listener

to your configuration with a different port and database name.

Thanks,
Ross

On Thu, Jun 23, 2016 at 3:03 AM, Manish Jain  wrote:

> We are using UDP for writing data using line protocol. So far we had only
> one DB, which we configured to have data over udp.
> But there is a requirement when we may need to create multiple DBs, now
> the writing data using line protocol over UDP (unlike over http) does not
> require to mention DB, how can we address 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/CABDqU92JX_Q53LM9YEnOqJ%3DxRnkscBjJJhLrU0FOa%3D7ka1yr%2Bw%40mail.gmail.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/CAD8sRLD_%2BOf11peLu0OuonftjPkgbUdv4BG7-wemew1_NojKhw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Error create exe Windows

[Ross McDonald]

There are experimental 1.0.0-beta2 windows builds available here
,
if you just need to run on Windows.

I've never run into that build error before, though. Do you get the same
error if you run the command below?

```
go install ./cmd/influxd
```

Thanks,
Ross

On Fri, Jun 24, 2016 at 8:19 AM, Jens  wrote:

> When i would like to create an exe of influxdb i receiving this error:
>
> C:\Go\Projects\src\github.com\influxdata\influxdb>go install ./...
> # github.com/influxdata/influxdb/services/httpd
> services\httpd\handler.go:793: invalid operation: token.Claims["exp"]
> (type jwt.Claims does not support indexing)
> services\httpd\handler.go:799: invalid operation: token.Claims["username"]
> (type jwt.Claims does not support indexing)
>
> What is going wrong ?
>
> --
> 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/ae1bc832-b6c8-44d7-9b6b-d06f7e6c91a4%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/CAD8sRLDjWWeGhDHui4o0Xm0Z-S%3Dhifp-DQg1-wWZwGXeAtsfFQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Using IN operator in InfluxQL or Lambda expressions

[Ross McDonald]

I believe the "IN" keyword is only supported with the "SHOW TAG VALUES
"
queries, where you can limit the tag values returned. For example:

> SHOW TAG VALUES FROM "cpu" WITH KEY IN ("region", "host") WHERE "service"
= 'redis'

Will limit the output to display the values of the "region" and "host" tag
keys only where the service is equal to "redis". I'd recommend opening an
issue  against the repo
if you'd like to see support for "IN" in select queries, though.

Thanks,
Ross

On Mon, Jun 27, 2016 at 7:08 AM, Sneha  wrote:

> Hi,
>
> Could you please help us with the syntax on how to use the 'IN' operator
> in lambda expression/InfluxQL?
>
> I've been trying out options like select * from disk where host in
> ('yyy','xxx') but seems like the 'IN' keyword is not recognized. Could you
> please help?
>
> Thanks,
> Sneha
>
> --
> 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/3d8303ed-bff4-4123-a721-4431c1d07a42%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/CAD8sRLBYxKW-4fVEh%2Bhs6GbVJP8ey1AbxY3P4Z_Pt%3Dex9ZCYVw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] python InfluxDBClient.write() ?

[Ross McDonald]

I believe the reasoning is that `client.write()` is more for internal use
within the `client` class, since it does require specifying the correct URL
parameters on every request (which quickly becomes tiresome). I'd recommend
using the `client.write_points()
`
method instead. This will change your gist to:

https://gist.github.com/rossmcdonald/83e64ba61d1ec3e43f05e5568e7350e2

Where `data` is a list of dictionaries/points. This also gives you the
added benefit of automatic batching of writes (the `batch_size` kwarg) and
other useful keyword arguments.

Thanks,
Ross

On Tue, Jun 28, 2016 at 11:45 AM, Anders Wallin  wrote:

> Hi all,
>
> I'm using python to collect measurements and wanted a minimal write()
> function that is easier to use than SeriesHelper.
>
> I came up with something like this:
>
> https://gist.github.com/aewallin/906b5bc5b756c67be14cb9ab7e6e49dc#file-influxdb_write-py-L21
>
> What is puzzling is the required params={'db':dbname} in the
> client.write() call.
> I would have expected the  InfluxDBClient constructor to take host, port,
> database as parameters and then not ask for them again later!?
>
> I notice this was also discussed earlier in 10/2015
>
> https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/influxdb/wrBOjiZApIY/0wlJDfPlCQAJ
>
> converting tag/field data that is already in python dicts to JSON seems
> pointless, so I'd really like a clean and minimal interface for writing
> points from python.
>
> thanks,
> Anders
>
> --
> 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/CAPnVNRWhQntvzJs6qjj%2BcAv%3DAX2p%2BKvZAD6%2B%3Df4BxgAD8jMNBA%40mail.gmail.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/CAD8sRLBzLhQF8ME%3DPpSoFNSayk3dM9QqDEZR2qzDrYU4%2BG%2B1Rg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] batch wont compile (using join)

[Ross McDonald]

I think the problem is that the `==` operator is not valid InfluxQL. Try
updating your queries to use `=` instead of `==`. So the first query should
be:

SELECT 100*mean("value") FROM "metrics"."default"."134" WHERE "measure" =
'impressions' AND "relative" = '0' AND "env" = 'exchange' AND "type" =
'diff_percent'


And so on. The error message:

found =, expected identifier, string, number, bool at line 1, char 71


Is what's returned by InfluxDB (referring to character 71 of the query),
which is why it's a little confusing.

Thanks,
Ross

On Wed, Jul 27, 2016 at 3:49 AM,  wrote:

> didn't help...
>
> On Monday, July 25, 2016 at 7:34:45 PM UTC+3, Sean Beckett wrote:
>>
>> Version numbers should match. You are using Kapacitor 0.2 with InfluxDB
>> 0.13. I would recommend upgrading to Kapacitor 0.13 and see if that
>> addresses the issue.
>>
>> On Mon, Jul 25, 2016 at 8:52 AM,  wrote:
>>
>>> hello,
>>> im using kapacitor v 0.2 beta influxdb v 0.13.0
>>> i got an issue trying to define a new alert using joinNode
>>>
>>> heres my tick:
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *var one = batch|query(''' SELECT 100*mean("value") FROM
>>> "metrics"."default"."134" WHERE "measure" == 'impressions' AND "relative"
>>> == '0' AND "env" == 'exchange' AND "type" == 'diff_percent' ''')
>>> .period(60m).every(30s).groupBy('measure', 'relative',
>>> 'env', 'type', time(10s)).fill(0)|eval(lambda: int("mean"))
>>> .as('mean')var two = batch|query(''' SELECT min("value") FROM
>>> "metrics"."default"."134" WHERE "relative" == '0' AND "source" == 'adk2'
>>> AND "env" == 'exchange' AND "measure" == 'impressions' ''')
>>> .period(60m).every(30s).groupBy('measure', 'relative',
>>> 'env', 'source', time(10s)).fill(0)|eval(lambda:
>>> "min"/"mean").as('bla')one|join(two)  .as('one', 'two')
>>> |eval(lambda: "two"/"one").as('bla')|alert().id('{{
>>> .Name }}@{{ index .Tags "measure" }}').message('{{ .ID }} {{ .Level
>>> }} measure: {{ index .Fields "bla" }} (threshold: below 0)')
>>> .crit(lambda: "bla" > 0)
>>> .log('/adk2/var/kapacitor/alerts.log').slack()
>>> .channel('#alerts-test')*
>>>
>>>
>>>
>>>
>>> and my error when trying to define and enable my tick:
>>>
>>> *enabling task test_tick: found =, expected identifier, string, number,
>>> bool at line 1, char 71*
>>>
>>>
>>> i dont even have char 71 in line 1
>>>
>>> any thoughts?
>>>
>>> --
>>> 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/86887b62-d38a-4ec5-84bb-360b7d185da3%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/35090cd1-7b78-4fad-99ab-c61c114c1771%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/CAD8sRLAZeF_iq1yoRkPaqWwkKWenVbD2%3D0W8qsCYgUpKzTYwrQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Unable to start/restart influxdb service

[Ross McDonald]

With 0.13.0 on RHEL 7, the logs were still being redirected to the
`/var/log/influxdb` directory. Are there any relevant messages in the
`/var/log/influxdb/influxd.log` file?

Thanks,
Ross

On Fri, Jul 29, 2016 at 12:25 PM,  wrote:

> I am running influxdb on a RHLE 7 machine.
> I installed a fresh 0.13.0 version of influxdb.
> After I created databases, users and retention policies, I was able to
> write to the database from a remote client using the HTTP API successfully.
>
> However, when I enabled HTTPS in the config file, I tried restarting the
> service but it failed, giving me errors similar to the following:
>
>
>
> ● influxdb.service - InfluxDB is an open-source, distributed, time series
> database
>Loaded: loaded (/usr/lib/systemd/system/influxdb.service; disabled;
> vendor preset: disabled)
>Active: failed (Result: start-limit) since Fri 2016-07-29 20:57:19 GST;
> 1s ago
>  Docs: https://docs.influxdata.com/influxdb/
>   Process: 53595 ExecStart=/bin/sh -c /usr/bin/influxd -config
> /etc/influxdb/influxdb.conf ${INFLUXD_OPTS} >>${STDOUT} 2>>${STDERR}
> (code=exited, status=1/FAILURE)
>  Main PID: 53595 (code=exited, status=1/FAILURE)
>
> Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: Unit influxdb.service entered
> failed state.
> Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: influxdb.service failed.
> Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: influxdb.service holdoff time
> over, scheduling restart.
> Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: start request repeated too
> quickly for influxdb.service
> Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: Failed to start InfluxDB is an
> open-source, distributed, time series database.
> Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: Unit influxdb.service entered
> failed state.
> Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: influxdb.service failed.
>
>
> I managed to get it to start again by using the command influx (and write
> to database using HTTPS this is why I doubt this is from HTTPS ) , but it
> still causes the service to fail sometimes (when I change something in the
> config file and try to restart service again.)
>
> Now, I can't get the service to work again.
>
> This problem has been bugging me for quite sometime now.
> Tried some usual obvious commands related to systems, but with no use:
>
> systemctl restart influxdb.service
>
> systemctl stop influxdb.service
> systemctl reset-faild influxdb.service
> then
> systemctl start influxdb.service
>
> and
> systemctl disable influxdb.service
>
> NOTHING CHANGES.
>
>
> This is the result of journalctl -xe in case it's of any use (although
> looks similar to the first error):
>
> -- Subject: Unit influxdb.service has begun start-up
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit influxdb.service has begun starting up.
> Jul 29 21:16:56 hrc-cse-perf01 systemd[1]: influxdb.service: main process
> exited, code=exited, status=1/FAILURE
> Jul 29 21:16:56 hrc-cse-perf01 systemd[1]: Unit influxdb.service entered
> failed state.
> Jul 29 21:16:56 hrc-cse-perf01 systemd[1]: influxdb.service failed.
> Jul 29 21:16:57 hrc-cse-perf01 systemd[1]: influxdb.service holdoff time
> over, scheduling restart.
> Jul 29 21:16:57 hrc-cse-perf01 systemd[1]: Cannot add dependency job for
> unit firewalld.service, ignoring: Unit firewalld.service is ma
> Jul 29 21:16:57 hrc-cse-perf01 systemd[1]: start request repeated too
> quickly for influxdb.service
> Jul 29 21:16:57 hrc-cse-perf01 systemd[1]: Failed to start InfluxDB is an
> open-source, distributed, time series database.
> -- Subject: Unit influxdb.service has failed
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit influxdb.service has failed.
> --
> -- The result is failed.
>
> --
> 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/712fa317-99aa-4281-b0b8-82cd6c18645a%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/CAD8sRLDFh_%2BFkP%2B4FCEza

Re: [influxdb] Unable to start/restart influxdb service

[Ross McDonald]

Since it's a permissions issues, you'll need to `chown` the data directory
to restore access:

```
sudo chown -R influxdb:influxdb /var/lib/influxdb
```

You may also want to look into how or why the permissions were changed.

Thanks,
Ross

On Fri, Jul 29, 2016 at 12:35 PM,  wrote:

> Yes, a lot of permission denied errors : (logged in as root BTW)
>
> [run] 2016/07/29 21:33:06 Go version go1.6.2, GOMAXPROCS set to 4
>
> [run] 2016/07/29 21:33:07 Using configuration at:
> /etc/influxdb/influxdb.conf
>
> run: create server: open /var/lib/influxdb/meta/meta.db: permission denied
>
> [run] 2016/07/29 21:33:07 InfluxDB starting, version 0.13.0, branch 0.13,
> commit e57fb88a051ee40fd9277094345fbd47bb4783ce
>
> [run] 2016/07/29 21:33:07 Go version go1.6.2, GOMAXPROCS set to 4
>
> [run] 2016/07/29 21:33:07 Using configuration at:
> /etc/influxdb/influxdb.conf
>
> run: create server: open /var/lib/influxdb/meta/meta.db: permission denied
>
> [run] 2016/07/29 21:33:07 InfluxDB starting, version 0.13.0, branch 0.13,
> commit e57fb88a051ee40fd9277094345fbd47bb4783ce
>
> [run] 2016/07/29 21:33:07 Go version go1.6.2, GOMAXPROCS set to 4
>
> [run] 2016/07/29 21:33:07 Using configuration at:
> /etc/influxdb/influxdb.conf
>
> run: create server: open /var/lib/influxdb/meta/meta.db: permission denied
>
> [run] 2016/07/29 21:33:07 InfluxDB starting, version 0.13.0, branch 0.13,
> commit e57fb88a051ee40fd9277094345fbd47bb4783ce
>
> [run] 2016/07/29 21:33:07 Go version go1.6.2, GOMAXPROCS set to 4
>
> [run] 2016/07/29 21:33:07 Using configuration at:
> /etc/influxdb/influxdb.conf
>
> run: create server: open /var/lib/influxdb/meta/meta.db: permission denied
>
> [run] 2016/07/29 21:33:08 InfluxDB starting, version 0.13.0, branch 0.13,
> commit e57fb88a051ee40fd9277094345fbd47bb4783ce
>
> [run] 2016/07/29 21:33:08 Go version go1.6.2, GOMAXPROCS set to 4
>
> [run] 2016/07/29 21:33:08 Using configuration at:
> /etc/influxdb/influxdb.conf
>
>
>
>
>
>
>
> On Friday, July 29, 2016 at 9:29:37 PM UTC+4, Ross McDonald wrote:
>>
>> With 0.13.0 on RHEL 7, the logs were still being redirected to the
>> `/var/log/influxdb` directory. Are there any relevant messages in the
>> `/var/log/influxdb/influxd.log` file?
>>
>> Thanks,
>> Ross
>>
>> On Fri, Jul 29, 2016 at 12:25 PM,  wrote:
>>
>>> I am running influxdb on a RHLE 7 machine.
>>> I installed a fresh 0.13.0 version of influxdb.
>>> After I created databases, users and retention policies, I was able to
>>> write to the database from a remote client using the HTTP API successfully.
>>>
>>> However, when I enabled HTTPS in the config file, I tried restarting the
>>> service but it failed, giving me errors similar to the following:
>>>
>>>
>>>
>>> ● influxdb.service - InfluxDB is an open-source, distributed, time
>>> series database
>>>Loaded: loaded (/usr/lib/systemd/system/influxdb.service; disabled;
>>> vendor preset: disabled)
>>>Active: failed (Result: start-limit) since Fri 2016-07-29 20:57:19
>>> GST; 1s ago
>>>  Docs: https://docs.influxdata.com/influxdb/
>>>   Process: 53595 ExecStart=/bin/sh -c /usr/bin/influxd -config
>>> /etc/influxdb/influxdb.conf ${INFLUXD_OPTS} >>${STDOUT} 2>>${STDERR}
>>> (code=exited, status=1/FAILURE)
>>>  Main PID: 53595 (code=exited, status=1/FAILURE)
>>>
>>> Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: Unit influxdb.service entered
>>> failed state.
>>> Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: influxdb.service failed.
>>> Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: influxdb.service holdoff time
>>> over, scheduling restart.
>>> Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: start request repeated too
>>> quickly for influxdb.service
>>> Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: Failed to start InfluxDB is
>>> an open-source, distributed, time series database.
>>> Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: Unit influxdb.service entered
>>> failed state.
>>> Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: influxdb.service failed.
>>>
>>>
>>> I managed to get it to start again by using the command influx (and
>>> write to database using HTTPS this is why I doubt this is from HTTPS ) ,
>>> but it still causes the service to fail sometimes (when I change something
>>> in the config file and try to restart service again.)
>>>
>>> Now, I can't get the service to work again.
>>>
>>> This problem has been bugging me for qu

Re: [influxdb] Unable to start/restart influxdb service

[Ross McDonald]

Did you manually start the InfluxDB process using something similar to the
command below?

```
sudo influxd -config /etc/influxdb/influxdb.conf
```

If you ran the above command as root, it could have potentially modified
the permissions on the files. Make sure that you only start the InfluxDB
process via systemctl, and not manually running the `influxd` command.

Thanks,
Ross

On Fri, Jul 29, 2016 at 1:04 PM,  wrote:

>
> Definitely looks like a permissions error !
> I am getting a similar message on the SSL certificate file now:
>
> ```
> run: open server: open service: open /etc/ssl/influxdb.pem: permission
> denied
> ```
>
> But applying  the same chown command on the file causes the service to run
> again.
>
>
>
> I find this annoying and weird.
> How do you suggest I go about finding out why the permissions were changed?
> (I never changed them as root for sure!)
>
> Thanks,
> Ali
>
>
> On Friday, July 29, 2016 at 9:38:53 PM UTC+4, Ross McDonald wrote:
> > Since it's a permissions issues, you'll need to `chown` the data
> directory to restore access:
> >
> >
> > ```
> > sudo chown -R influxdb:influxdb /var/lib/influxdb
> > ```
> >
> >
> > You may also want to look into how or why the permissions were changed.
> >
> >
> > Thanks,
> > Ross
> >
> >
> > On Fri, Jul 29, 2016 at 12:35 PM,   wrote:
> >
> > Yes, a lot of permission denied errors : (logged in as root BTW)
> >
> >
> >
> > [run] 2016/07/29 21:33:06 Go version go1.6.2, GOMAXPROCS set to 4
> >
> > [run] 2016/07/29 21:33:07 Using configuration at:
> /etc/influxdb/influxdb.conf
> >
> > run: create server: open /var/lib/influxdb/meta/meta.db: permission
> denied
> >
> > [run] 2016/07/29 21:33:07 InfluxDB starting, version 0.13.0, branch
> 0.13, commit e57fb88a051ee40fd9277094345fbd47bb4783ce
> >
> > [run] 2016/07/29 21:33:07 Go version go1.6.2, GOMAXPROCS set to 4
> >
> > [run] 2016/07/29 21:33:07 Using configuration at:
> /etc/influxdb/influxdb.conf
> >
> > run: create server: open /var/lib/influxdb/meta/meta.db: permission
> denied
> >
> > [run] 2016/07/29 21:33:07 InfluxDB starting, version 0.13.0, branch
> 0.13, commit e57fb88a051ee40fd9277094345fbd47bb4783ce
> >
> > [run] 2016/07/29 21:33:07 Go version go1.6.2, GOMAXPROCS set to 4
> >
> > [run] 2016/07/29 21:33:07 Using configuration at:
> /etc/influxdb/influxdb.conf
> >
> > run: create server: open /var/lib/influxdb/meta/meta.db: permission
> denied
> >
> > [run] 2016/07/29 21:33:07 InfluxDB starting, version 0.13.0, branch
> 0.13, commit e57fb88a051ee40fd9277094345fbd47bb4783ce
> >
> > [run] 2016/07/29 21:33:07 Go version go1.6.2, GOMAXPROCS set to 4
> >
> > [run] 2016/07/29 21:33:07 Using configuration at:
> /etc/influxdb/influxdb.conf
> >
> > run: create server: open /var/lib/influxdb/meta/meta.db: permission
> denied
> >
> > [run] 2016/07/29 21:33:08 InfluxDB starting, version 0.13.0, branch
> 0.13, commit e57fb88a051ee40fd9277094345fbd47bb4783ce
> >
> > [run] 2016/07/29 21:33:08 Go version go1.6.2, GOMAXPROCS set to 4
> >
> > [run] 2016/07/29 21:33:08 Using configuration at:
> /etc/influxdb/influxdb.conf
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Friday, July 29, 2016 at 9:29:37 PM UTC+4, Ross McDonald wrote:
> >
> > With 0.13.0 on RHEL 7, the logs were still being redirected to the
> `/var/log/influxdb` directory. Are there any relevant messages in the
> `/var/log/influxdb/influxd.log` file?
> >
> >
> > Thanks,
> > Ross
> >
> >
> >
> >
> > On Fri, Jul 29, 2016 at 12:25 PM,   wrote:
> >
> >
> > I am running influxdb on a RHLE 7 machine.
> >
> > I installed a fresh 0.13.0 version of influxdb.
> >
> > After I created databases, users and retention policies, I was able to
> write to the database from a remote client using the HTTP API successfully.
> >
> >
> >
> > However, when I enabled HTTPS in the config file, I tried restarting the
> service but it failed, giving me errors similar to the following:
> >
> >
> >
> >
> >
> >
> >
> > ● influxdb.service - InfluxDB is an open-source, distributed, time
> series database
> >
> >Loaded: loaded (/usr/lib/systemd/system/influxdb.service; disabled;
> vendor preset: disabled)
> >
> >Active: failed (Result: start-limit) since Fri 2016-07-29 20:57:19
> GST; 1s ago
> >
> &g

Re: [influxdb] No data on subscription

[Ross McDonald]

What versions of both InfluxDB and Kapacitor are you running?

And are you sure points are being written to the `ion` database? What does
the output of a `kapacitor show test` look like?

Thanks,
Ross

On Tue, Aug 9, 2016 at 2:15 PM, Kristopher Cieplak 
wrote:

> I cannot seem to get any data from influxdb to kapacitor via the
> subscription.
>
> I have confirmed that I can get data to the kapacitor server, and create a
> bad data over the connection.
>
> ** On influxdb node
> echo foobar | nc -u 10.0.36.176 37661
>
>
> ** On kapacitor node
> [udp:ion.default] 2016/08/09 19:04:47 E! Failed to parse points: unable to
> parse 'foobar': missing fields
>
> So it looks like kapacitor is listening on the correct UDP port, and I can
> communicate to it, i.e no firewall or security rules in the way.
>
> My subscription seems to be correct.
>
> name: ion
> -
> retention_policy name mode destinations
> default kapacitor-a45324cf-927d-4bda-822a-24716624b5ca ANY [udp://
> 10.0.36.176:37661]
>
>
> If I try to record data on the stream it simply hangs and records nothing,
> i.e. 0bytes of data
> ./kapacitor record stream -task test -duration 5s
> ./kapacitor list recordings
> ID  TypeStatusSize  Date
> cb26ee7e-9a55-484c-97ce-e63a3e517ca1stream  running   0 B   09
> Aug 16 19:13 UTC
>
> Any ideas on how I can debug this?  I need to figure out why I do not seem
> to get data streaming from Influxdb to Kapacitor.
>
> 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/e25336bc-10be-4113-8399-d650a950e498%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/CAD8sRLAqu9FovkFHX6S0sAP7YGuL8sY6ujv6wj%3Dc%3DTiZKBWe0A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Re: Kapacitor "invalid field type: string" error

[Ross McDonald]

The error here:

> [cpu_alert:mean3] 2016/08/11 13:34:01 E! invalid field type: 

Is referring to the `|mean('value')` call, which is receiving a null value
for the "value" field. To fix that you'll either need to:

* Remove it, since it doesn't look like you're using it anywhere anyways
(and Telegraf no longer uses "value" as a field to my knowledge)

* Add a `|default().field('value', 0.0)` call before taking the mean of
value so that it defaults to 0 if it is not provided in the stream

I hope that helps!

Thanks,
Ross

On Thu, Aug 11, 2016 at 8:39 AM,  wrote:

> [edge:cpu_alert|mean3->default4] 2016/08/11 13:34:01 D! closing c: 0 e: 0
> [edge:cpu_alert|window2->mean3] 2016/08/11 13:34:01 I! aborting c: 1 e: 1
> [cpu_alert:mean3] 2016/08/11 13:34:01 E! invalid field type: 
> [edge:cpu_alert|default4->eval5] 2016/08/11 13:34:01 D! closing c: 0 e: 0
> [edge:cpu_alert|eval5->alert6] 2016/08/11 13:34:01 D! closing c: 0 e: 0
> [edge:cpu_alert|stream->stream0] 2016/08/11 13:34:01 D! closing c: 129 e:
> 129
> [edge:cpu_alert|stream0->from1] 2016/08/11 13:34:01 D! closing c: 129 e:
> 129
> [edge:cpu_alert|from1->window2] 2016/08/11 13:34:01 D! closing c: 129 e:
> 129
> [edge:cpu_alert|window2->mean3] 2016/08/11 13:34:01 D! closing c: 1 e: 1
> [task_master] 2016/08/11 13:34:01 E! Stopped task: cpu_alert invalid field
> type: 
> [task_store] 2016/08/11 13:34:01 E! task cpu_alert finished with error:
> invalid field type: 
>
>
>
>
> Getting this error , what should I do ??
>
>
> Following is the output of my show task :
>
>
>
>
>  kapacitor show cpu_alert
> ID: cpu_alert
> Error:
> Type: stream
> Status: enabled
> Executing: true
> Created: 11 Aug 16 11:45 UTC
> Modified: 11 Aug 16 13:32 UTC
> LastEnabled: 11 Aug 16 13:32 UTC
> Databases Retention Policies: ["telegraf"."default"]
> TICKscript:
> stream
> |from()
> .measurement('cpu')
> .groupBy('host')
> |window()
> .period(1m)
> .every(1m)
> |mean('value')
> |default()
> .field('usage_user', 0.0)
> .tag('host', '')
> |eval(lambda: 100.0 - "mean")
> .as('used')
> |alert()
> .message('{{ .Level}}: {{ .Name }}/{{ index .Tags "host" }} has
> high cpu usage: {{ index .Fields "usage_user" }}')
> .info(lambda: TRUE)
> .warn(lambda: "usage_user" > 60.0)
> .crit(lambda: "usage_user" > 85.0)
> .log('/tmp/high_cpu.log')
>
>
> DOT:
> digraph cpu_alert {
> graph [throughput="0.00 points/s"];
>
> stream0 [avg_exec_time_ns="0" ];
> stream0 -> from1 [processed="20"];
>
> from1 [avg_exec_time_ns="1.156µs" ];
> from1 -> window2 [processed="20"];
>
> window2 [avg_exec_time_ns="0" ];
> window2 -> mean3 [processed="0"];
>
> mean3 [avg_exec_time_ns="0" ];
> mean3 -> default4 [processed="0"];
>
> default4 [avg_exec_time_ns="0" fields_defaulted="0" tags_defaulted="0" ];
> default4 -> eval5 [processed="0"];
>
> eval5 [avg_exec_time_ns="0" eval_errors="0" ];
> eval5 -> alert6 [processed="0"];
>
> alert6 [alerts_triggered="0" avg_exec_time_ns="0" crits_triggered="0"
> infos_triggered="0" oks_triggered="0" warns_triggered="0" ];
> }
>
> --
> 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/9d919bf7-86e4-41ab-b9c7-0d57605c6f0b%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/CAD8sRLAdyLFUQpqE_92BpSa0Me%3DmGCu9%2BVb-xrAXv%3DYHD-vXfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] TSM exporter and timeline to 1.0

[Ross McDonald]

> Are the nightlies the lead-up to the 1.0 release, or an 1.1 release? I
thought I saw 1.1.0 in the nightly version as I installed it on centos.

The nightlies are always a version above master. Since the 1.0 branch has
been created and diverged from master, the nightlies can be considered what
will be InfluxDB v1.1.

On Tue, Aug 23, 2016 at 4:01 AM, Emiliano Heyns <
emiliano.he...@iris-advies.com> wrote:

> On Friday, August 19, 2016 at 12:05:42 AM UTC+2, Sean Beckett wrote:
>>
>>
>> Practically, yes, you can ignore the config changes for this upgrade.
>> Eventually it is important to purge old config entries and make sure new
>> ones are well-set, but the 1.0 final release would be a good time for that
>> focus.
>>
>
> Are the nightlies the lead-up to the 1.0 release, or an 1.1 release? I
> thought I saw 1.1.0 in the nightly version as I installed it on centos.
>
> --
> 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/5f6b000e-f1cc-4cb4-88f3-8fb88f363a0a%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/CAD8sRLAagR_3P55AgQgD67r%3DX6NjUOVk034oEHHXV2pF%3DQfJ1w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Aggregation across multiple measurements matched with regex?

[Ross McDonald]

Hey Casey,

That is not currently possible within InfluxQL. As you have found out, the
results are still grouped by measurement.

This is halfway-possible using Kapacitor
, where you can create a stream
that collects points from all measurements by not specifying a
`measurement` in the `from` node. For example:

```
stream
|from()
.database('telegraf')
.retentionPolicy('autogen')
```

Will collect all points written to the telegraf database (not grouped by
measurement), which would enable you to aggregate fields across all
measurements. At the moment you cannot restrict the measurements with
regex, so I have gone ahead and created a feature request to support this
in the future here .
Also, if you haven't already done so, I'd recommend you look into using
Kapacitor as continuous query engine
,
which sounds similar to what you're trying to accomplish here.

If you are unable to use Kapacitor, I think modifying your schema will be
your best option.

I hope that helps!

Thanks,
Ross

On Mon, Aug 22, 2016 at 10:42 PM,  wrote:

> Is it possible to perform GROUP BY aggregation across multiple
> measurements, such that they can be selected into a new single measurement?
>
> For example, I'd like to do something like:
>
> SELECT COUNT(value) as h_count, SUM(value) as h_sum, MIN(value) as h_min,
> MAX(value) as h_max INTO hourly FROM /rawdata.*/ GROUP BY time(1h), tag1,
> tag2
>
> The result I'm seeing when I try this leads me to believe the aggregate
> function isn't being applied across all the matched measurements -- just
> within each. Is there a way to aggregate across all of them with InfluxQL?
> If so, how?
>
> If not, I can probably work around this with a different schema, but it
> seems like it'd be a useful thing to be able to do.
>
> Thanks,
> Casey
>
> --
> 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/bfd31c07-f365-43be-9490-6c0552dde624%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/CAD8sRLCH%3D5m5z_nQfas5E6%3Dcb8hmZGZ0fPfN1Xy7cYzCE7aQtQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Unable to upgrade from 1.0.0_beta3 to 1.0.0~rc1 on CentOS 7 (yum)

[Ross McDonald]

Hi Tim,

This was caused by inconsistent naming between the RC and beta versioning
for RPM packages. RPM sees `1.0.0_betaX` as a higher version than
`1.0.0~rcX`, which is why it's not automatically triggering the upgrade. As
a workaround, you can use the `downgrade` option over `install`, making the
command:

```
sudo yum downgrade influxdb-1.0.0~rc1.x86_64.rpm
```

Or, if you are using the repository, just:

```
sudo yum downgrade influxdb
```

We won't be issuing new packages due to the original error (1.0.0_rc1 is
considered higher in version than 1.0.0-1), however this issue will be
resolved from here on out, so this is the only time this workaround will be
needed.

Sorry for the confusion! Let me know if you have any questions or run into
any further issues.

Thanks,
Ross

On Wed, Aug 24, 2016 at 1:20 PM, Tim Wright  wrote:

> I'm presuming that this is yum not understanding that 1.0.0.~rc1 is newer
> than 1.0.0_beta3.
> Here's what happens when I try to upgrade (previous upgrade from
> 0.13->beta and upgrade within beta worked fine):
>
> [timw@ticktest ~]$ sudo yum localupdate influxdb-1.0.0~rc1.x86_64.rpm
> Loaded plugins: fastestmirror
> Examining influxdb-1.0.0~rc1.x86_64.rpm: influxdb-1.0.0~rc1-1.x86_64
> influxdb-1.0.0~rc1.x86_64.rpm: does not update installed package.
> Nothing to do
>
> Any thoughts?
> Any way to work around this?
> Does the RC package need to be renamed and re-rolled?
>
> Thanks,
>
> Tim
>
> --
> 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/d5dd69ce-b833-453a-9cb0-a78d5f4af1d0%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/CAD8sRLDrpsM4LgjUpOWt1AAD2dQ0xExHGCL7MzLcuvwNF8AWew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] kapacitor not working after upgrade and downgrade

[Ross McDonald]

>From the bottom of the `kapacitor show` output:

> stream0 -> from1 [processed="0"];

This means that this task has processed zero points, so it's probably not
receiving any data from InfluxDB. The "recording never returns" issue is
also a symptom of lack of points being received.

What does the output to a `show subscriptions` command look like when run
from the InfluxDB CLI? Also, since you are running in Docker, are you
exposing any ports to the Kapacitor container?

On Tue, Sep 6, 2016 at 5:30 AM,  wrote:

> I investigated a 'bug' in kapacitor and upgraded to 1.0.0-rc2. Kapacitor
> doesn't work anymore. I know this is a vague and useless remark, but I
> don't know how
> to describe it otherwise. The steps I took are:
>
> - made a reinstall of kapacitor 0.13.1 (a docker container with the
> content of /var/lib/kapacitor as an external volume)
> - ran:
> curl -G 'http://localhost:8086/query?db=telegraf' --data-urlencode 'q=SELECT
> count(usage_idle) FROM cpu
> and that responded correctly
> - created a tick script by copying the example in the Getting started
> manual (usage_idle)
> - recorded the stream using command:
>
> kapacitor record stream -task cpu_test -duration 20s
>
>
> However this record command never returns.
>
> The /var/log/kapacitor/kapacitor.log file contains the following lines:
> ...
> [httpd] 2016/09/06 10:24:42 I! ::1 - - [06/Sep/2016:10:24:42 +] GET /
> kapacitor/v1/recordings/3848ad70-dc7e-4b24-afca-d0a0dfe374a0 HTTP/1.1 202
> 209 - KapacitorClient 200e0ce5-741c-11e6-8ab0- 7.848494ms
>
> [httpd] 2016/09/06 10:24:43 I! ::1 - - [06/Sep/2016:10:24:43 +] GET /
> kapacitor/v1/recordings/3848ad70-dc7e-4b24-afca-d0a0dfe374a0 HTTP/1.1 202
> 209 - KapacitorClient 205c8036-741c-11e6-8ab1- 545.448µs
>
> ...
>
>
> And it never stops
>
> The result of the show command is:
> ID: cpu_test
> Error:
> Type: stream
> Status: enabled
> Executing: true
> Created: 06 Sep 16 09:18 UTC
> Modified: 06 Sep 16 09:51 UTC
> LastEnabled: 06 Sep 16 09:51 UTC
> Databases Retention Policies: ["telegraf"."default"]
> TICKscript:
> stream
> // Select just the cpu measurement from our example database.
> |from()
> .measurement('cpu')
> |alert()
> .crit(lambda: "usage_idle" < 70)
> // Whenever we get an alert write it to a file.
> .log('/tmp/alerts.log')
>
>
>
>
> DOT:
> digraph cpu_test {
> graph [throughput="0.00 points/s"];
>
>
> stream0 [avg_exec_time_ns="0" ];
> stream0 -> from1 [processed="0"];
>
>
> from1 [avg_exec_time_ns="0" ];
> from1 -> alert2 [processed="0"];
>
>
> alert2 [alerts_triggered="0" avg_exec_time_ns="0" crits_triggered="0"
> infos_triggered="0" oks_triggered="0" warns_triggered="0" ];
> }
>
>
>
>
> The tickscript doesn't generate alerts too.
>
> I hope someone as an creative idea where to look for a possible solution
> for this problem.
>
> 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/13fa89dd-5d5d-48b6-924b-5b38fca01a59%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/CAD8sRLBHnhr_UMDJyFKgBuHggYA0OHw3vtcCar0PJsaT_NrEhg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Windows installer

[Ross McDonald]

Hi Manish,

There is not currently an installer for InfluxDB, however we do have
experimental Windows builds available. The v1.0.0 build can be found here:

https://dl.influxdata.com/influxdb/releases/influxdb-1.0.0_windows_amd64.zip

Thanks,
Ross

On Fri, Sep 16, 2016 at 11:44 AM, Manish Jain 
wrote:

> All,
>
> I wonder if there is someone who is managing Influxdb installers for
> Windows platform.
>
> Regards,
>
> Manish
>
> --
> 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/CABDqU933CbO9HQ3L3b7KSsXkXOTvei3n7j82_m0u_mJh7vJ%3DWQ%
> 40mail.gmail.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/CAD8sRLAj%2BVgSU1FYerCx-Y-2UN%3DeJ-MJsVPAWUbM%3DpQPeRG38w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Re: Correct ownerships for files on ARM/RPi?

[Ross McDonald]

Ah, so the tarball packages don't have the necessary permissions to run
InfluxDB as a service. What distribution of Linux are you running? Can you
not use the RPM or DEB packages instead?

If not, you'll need to create the following directories with owner:group as
influxdb:
- /var/lib/influxdb
- /etc/influxdb

And you'll want to take the systemd unit file from here

.

Thanks,
Ross

On Thu, Sep 15, 2016 at 4:04 PM, Teppo Kurki  wrote:

> Maybe I'm doing something else wrong?
>
> uname -a
>
> Linux x 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l
> GNU/Linux
>
> wget https://dl.influxdata.com/influxdb/releases/influxdb-1.
> 0.0_linux_armhf.tar.gz
>
> sudo tar xvf influxdb-1.0.0_linux_armhf.tar.gz -C / --strip-components=2
> adduser influxdb
>
> sudo -u influxdb -s
>
> influxd
>
> [run] 2016/09/16 00:01:36 InfluxDB starting, version 1.0.0, branch master,
> commit 37992377a55fbc138b2c01edd4deffed64b53989
>
> [run] 2016/09/16 00:01:36 Go version go1.6.2, GOMAXPROCS set to 4
>
> [run] 2016/09/16 00:01:36 Using configuration at:
> /etc/influxdb/influxdb.conf
>
> run: create server: open /var/lib/influxdb/meta/meta.dbtmp: permission
> denied
>
> On Thu, Sep 15, 2016 at 11:53 PM,  wrote:
>
>> What OS and version are you running on the Pi? What version of InfluxDB?
>> Where did you download the package from?
>>
>> We haven't heard of any other issues with permissions, so I'm not sure
>> what the issue could be.
>>
>> On Thursday, September 15, 2016 at 3:35:15 PM UTC-5, teppo...@gmail.com
>> wrote:
>>>
>>> I started to look into an Ansible script to install InfluxDB on my
>>> Raspberry Pi.
>>>
>>> Download & extract & run as root work, but I would like to use the stock
>>> systemd unit file, where the user is influxdb. All the files in the archive
>>> are root/root owner/group.
>>>
>>> Is there an easier method than trial and error to figure out the correct
>>> ownerships?
>>>
>>>
> --
> 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/CAOyOCEBkFXkfb1XGKroG4KPp2WFOXfOf-kR4xpa%3DSThZ-a3vrA%
> 40mail.gmail.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/CAD8sRLDinj0v1ey-Srn0ygWiVOQzqqzS0X1g4KiJYuE8oYU6og%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Correct ownerships for files on ARM/RPi?

[Ross McDonald]

You can find the v1.0.0 armhf deb package here:

https://dl.influxdata.com/influxdb/releases/influxdb_1.0.0_armhf.deb

Tarballs are provided for any distros that don't support deb/rpm packages,
or for users who want to configure everything themselves.

Thanks,
Ross

On Sat, Sep 17, 2016 at 4:42 AM, Teppo Kurki  wrote:

>
>
> lauantai 17. syyskuuta 2016 Ross McDonald  kirjoitti:
>
>> Ah, so the tarball packages don't have the necessary permissions to run
>> InfluxDB as a service. What distribution of Linux are you running? Can you
>> not use the RPM or DEB packages instead?
>>
>
> Jessie Lite on ARM on Raspberry Pi. I was under the assumption that there
> is no suitable package, or why else provide the ARM tarball?
>
>>
>> If not, you'll need to create the following directories with owner:group
>> as influxdb:
>> - /var/lib/influxdb
>> - /etc/influxdb
>>
>> And you'll want to take the systemd unit file from here
>> <https://github.com/influxdata/influxdb/blob/master/scripts/influxdb.service>
>> .
>>
>
> Yes, as I stated in the first message.
>
>
>>
>> Thanks,
>> Ross
>>
>> On Thu, Sep 15, 2016 at 4:04 PM, Teppo Kurki  wrote:
>>
>>> Maybe I'm doing something else wrong?
>>>
>>> uname -a
>>>
>>> Linux x 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l
>>> GNU/Linux
>>>
>>> wget https://dl.influxdata.com/influxdb/releases/influxdb-1.0.0_l
>>> inux_armhf.tar.gz
>>>
>>> sudo tar xvf influxdb-1.0.0_linux_armhf.tar.gz -C / --strip-components=2
>>> adduser influxdb
>>>
>>> sudo -u influxdb -s
>>>
>>> influxd
>>>
>>> [run] 2016/09/16 00:01:36 InfluxDB starting, version 1.0.0, branch
>>> master, commit 37992377a55fbc138b2c01edd4deffed64b53989
>>>
>>> [run] 2016/09/16 00:01:36 Go version go1.6.2, GOMAXPROCS set to 4
>>>
>>> [run] 2016/09/16 00:01:36 Using configuration at:
>>> /etc/influxdb/influxdb.conf
>>>
>>> run: create server: open /var/lib/influxdb/meta/meta.dbtmp: permission
>>> denied
>>>
>>> On Thu, Sep 15, 2016 at 11:53 PM,  wrote:
>>>
>>>> What OS and version are you running on the Pi? What version of
>>>> InfluxDB? Where did you download the package from?
>>>>
>>>> We haven't heard of any other issues with permissions, so I'm not sure
>>>> what the issue could be.
>>>>
>>>> On Thursday, September 15, 2016 at 3:35:15 PM UTC-5, teppo...@gmail.com
>>>> wrote:
>>>>>
>>>>> I started to look into an Ansible script to install InfluxDB on my
>>>>> Raspberry Pi.
>>>>>
>>>>> Download & extract & run as root work, but I would like to use the
>>>>> stock systemd unit file, where the user is influxdb. All the files in the
>>>>> archive are root/root owner/group.
>>>>>
>>>>> Is there an easier method than trial and error to figure out the
>>>>> correct ownerships?
>>>>>
>>>>>
>>> --
>>> 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/CAOyOCEBkFXkfb1XGKroG4KPp2WFOXfOf-kR4xpa%3DSThZ
>>> -a3vrA%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/influxdb/CAOyOCEBkFXkfb1XGKroG4KPp2WFOXfOf-kR4xpa%3DSThZ-a3vrA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> 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 a topic in the
>> Google Groups "InfluxDB" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/influxdb/Q268o4sMevk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> influxdb+unsubscr...@googlegroups.co

Re: [influxdb] bug

[Ross McDonald]

I'm not aware of a way to check for null values in a lambda, however you
can default

the field to a nonsense value (-1, for example) to get the same effect. For
example, changing your script to:

```
var data = stream
|from()
.database('telegraf')
.retentionPolicy('telegraf_01')
.measurement('mysql')
.groupBy('host')
|window()
.period(10s)
.every(10s)
|default()
.field('slave_Slave_SQL_Running', -1)
```

Where 'slave_Slave_SQL_Running' is defaulted to the -1 integer value if it
is not present in the stream. Once defaulted, a -1 value essentially means
it was null, allowing you to check for any value that is != 1 or < 1 to
signal failure.

I hope that helps!

Thanks,
Ross

On Mon, Sep 19, 2016 at 9:35 PM, 'so...@aliyun.com' via InfluxDB <
influxdb@googlegroups.com> wrote:

> I want to monitor the slave status of the MySQL ,when the state is normal,
> the value is 1, but not in normal state for null, I want to know the value
> of null, how can I judge through the script:
> [image: image]
> 
>
> The following is my script:
>
> var crit_threshold = 1
> var data = stream
> |from()
> .database('telegraf')
> .retentionPolicy('telegraf_01')
> .measurement('mysql')
> .groupBy('host')
> |window()
> .period(10s)
> .every(10s)
> data
> |alert()
> .id('{{ index .Tags "host"}} | {{ index .Tags "slave_Slave_SQL_Running"}}')
> .message('{{ .ID }} is {{ .Level }} value:{{ index .Fields
> "slave_Slave_SQL_Running" }}')
> .crit(lambda: "slave_Slave_SQL_Running" != 1)
> .stateChangesOnly()
> .log('/tmp/alert.log')
>
> Please help me.
>
> telegraf+kapacitor+infuxDB
>
> --
> so...@aliyun.com
>
> --
> 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/201609201035106520980%40aliyun.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/CAD8sRLDndojEAdbMvMttYWQRyo38oc2wZJs6UA3ggcXcDJmfrA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] missing deb packages for InfluxDB 0.13

[Ross McDonald]

All versions are kept on the dl.influxdata.com archive now (I've updated my
comment on that Github issue to reflect the switch, sorry about that), so
the link you're looking for is here:

https://dl.influxdata.com/influxdb/releases/influxdb_0.13.0_amd64.deb

We will also be updating the Debian repository to include older releases in
the near future.

Thanks,
Ross

On Mon, Sep 26, 2016 at 6:51 AM,  wrote:

> Hi,
>
> while trying to replicate our Production to Dev, I realized that I'm not
> able to install 0.13 version anymore !
>
> Stable repo contains only 1.0.0.
> https://repos.influxdata.com/ubuntu/pool/stable/i/influxdb/
>
> Older packages on S3 end with 0.12.2 version
> https://s3.amazonaws.com/influxdb/
>
> Related to this ticket
> https://github.com/influxdata/influxdb/issues/5913
>
> Is there any _other_ archive where we can find Debian/Ubuntu packages for
> 0.13.0 version ?
>
> Regards,
>
> Brano Zarnovican
>
> --
> 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/dfc7271b-b404-4961-acec-b485bd2083e1%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/CAD8sRLCrN%3DGokc3J9FPirVsGzWbEmELc%3DjC4Z7j8s3dXkFKJ4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] [Kapacitor] How to control the calculated precision of float values.

[Ross McDonald]

Is this just for display purposes (using it in a message), or do you want
to store the value like that? You can use `printf` in a template for
changing the precision, for example:

```
|alert()
.message('Percentage value is {{ index .Fields "value" | printf "%0.2f"
}}%')
```

I'm not sure if there's a way to store the value that way, though.

On Mon, Sep 26, 2016 at 10:35 PM, guotao Yao  wrote:

> Hi all,
>
> The next are statements of tick script, I want to get a percentage value.
>
> ```
> |eval(lambda: float(100) * ("system.value" / "total.value"))
> .as('value')
> ```
>
> Result value:
> 6.363635503165
>
> I want to get a value like this: 6.36.
>
> In other words, I need to control the precision of the float value.
>
> What should I do?
>
> 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/2a3d1590-fc14-4842-a1e1-b569c2925bec%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/CAD8sRLDREnS2Oh_ET5%3DuQo8eDnryP5gs0-VhCkSgD-vfCuF_Og%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] InfluxDB 0.13 download

[Ross McDonald]

You should use the 0.13.0 Debian package here
 if
installing on Ubuntu.

On Mon, Oct 3, 2016 at 2:32 AM,  wrote:

> Can you show me how to install influxdb-0.13.0_linux_amd64.tar.gz on
> Ubuntu server?
> I don't know how to install a tar.gz then service influxdb start as
> guideline.
>
> On Wednesday, September 28, 2016 at 10:09:05 PM UTC+7, Sean Beckett wrote:
> > https://dl.influxdata.com/ has an XML manifest of all prior releases,
> just search for the version and package you need.
> >
> >
> >
> > On Tue, Sep 27, 2016 at 8:51 PM,   wrote:
> > Hi all,
> >
> > Does anyone know where to download InfluxDB 0.13 in both using on
> Windows and Ubuntu?
> >
> >
> >
> > --
> >
> > 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/3052cef8-49ec-424a-876d-80e1a02912ae%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/5904b67d-adce-4190-ad45-8b9276d05cdb%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/CAD8sRLBnqi%2BNRxZpqFNQDoCYHgFr%2Bk5eRtaqVwFQ9GRgEqGeYA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Installing Influxdb from Source

[Ross McDonald]

I've never seen those errors before, but did you run a `gdm restore` before
building? Also what commit/tag are you building from?

On Sun, Oct 2, 2016 at 11:58 PM, kbg  wrote:

> I followed steps in this link to install influxdb from Source. (
> https://github.com/influxdata/influxdb/blob/master/CONTRIBUTING.md)
>
>
> when i got to this step,
>
> ---
> go clean ./...
> go install ./...
> 
>
> I encountered these errors.
>
> 
> 
> # github.com/influxdata/influxdb/tsdb
> tsdb/shard.go:150: s.logger.SetOutput undefined (type *log.Logger has no
> field or method SetOutput)
> tsdb/store.go:67: s.Logger.SetOutput undefined (type *log.Logger has no
> field or method SetOutput)
> 
> 
>
>
> How can i fix these error messages??
>
> --
> 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/50b6a79b-ce02-4ca8-81a5-92e417bc154b%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/CAD8sRLCnJqq0r0WR3xRCtiyh0JgU4DUVU2UCTWRFyXOATk2FRg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Re: Download influxdb for 32 bit machine

[Ross McDonald]

The RPM link:
https://dl.influxdata.com/influxdb/releases/influxdb-1.0.2.i386.rpm

Is correct. The repository also has 32-bit packages under the i386
architecture  heading. If you
follow the instructions here for configuring the yum repository:

https://docs.influxdata.com/influxdb/v1.0/introduction/installation/

It should automatically work. Let me know if you run into any issues,
though.

Thanks,
Ross

On Tue, Oct 18, 2016 at 7:00 AM, Michael Reed  wrote:

> Still looking for i686 package that will run on Centos.
>
> Older versions are available.  For instance, see
> https://docs.influxdata.com/influxdb/v0.8/introduction/installation/ for
> https://s3.amazonaws.com/influxdb/influxdb-0.8.8-1.i686.rpm.
>
>
> Randomly, I tried this url, and it appears to be available.
> https://dl.influxdata.com/influxdb/releases/influxdb-1.0.2.i386.rpm
> Would this be correct?
>
> https://dl.influxdata.com/influxdb/releases/influxdb-1.0.2_linux_i386.tar.gz 
> is also available, but is a binary and not available with yum.
>
>
>
>
> On Monday, October 17, 2016 at 5:27:16 PM UTC-7, Michael Reed wrote:
>>
>> Have a virtual server with 32 bit processor (i686)
>>
>> My windows 86_64 PC only gives me the link for
>> https://dl.influxdata.com/influxdb/releases/influxdb-1.0.2.x86_64.rpm.
>>
>> Where do I find the correct software?
>>
>> Thanks
>>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/96cb74af-b943-4dc7-a4ff-3d788259cf5d%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLAnoBMabrrY2iKzkwysumuTf4Rkjhnn0q%2B0u%3DR0Sa%3Drrg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Re: help with Kapacitor disk alert query

[Ross McDonald]

You can see examples for using `.stateChangesOnly()` in the documentation
here:

https://docs.influxdata.com/kapacitor/v1.0/nodes/alert_node/#statechangesonly

On Wed, Nov 2, 2016 at 10:21 AM,  wrote:

> Would it be possible for you to illustrate this via example? I am a bit
> new to kapacitor and i'm not sure exactly how to use .stateChangesOnly . I
> literally grabbed this from github on influxdata.
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/e055be2b-fc95-4b6b-b2ad-fae05c7e6522%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLDz1k_7kQ%3DujSayG0xmcdN-W_FZbndSj%2BenamhbdxkaEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] streaming multiple measurement through kapacitor at once

[Ross McDonald]

Using a blank measurement in a stream enables the node to receive points
for all measurements in the target database and retention policy. For
example:

```
|from().measurement('')
```

Will receive points from all measurements.

Thanks,
Ross

On Sun, Nov 6, 2016 at 10:54 PM, Sai Birada  wrote:

> I read through kapacitor documentation and i found that if we have to
> stream through multiple measurements we should have multiple FromNodes and
> Join them later. But I have numerous measurements and I could stream all
> these measurements by giving a regex for measurements in a batch task. Is
> there a way to use a regex to select all measurements of a database at once
> instead of picking each measurement and joining it in stream task? , If not
> is there a way to filter through where in a batch task?.
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/6ea59e39-c85b-4406-b090-96a663d4ff12%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLABU2Wi_%3DwtrAXkXQmcMVaCseZgq8nHjURQvvSZfRjZMA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] How to monitor disk usage

[Ross McDonald]

You can see the approximate size of the InfluxDB data directory by running
the following query against the `_internal` databases `shard` measurement:

```
select sum(diskBytes) / 1024 / 1024 /1024 from _internal."monitor"."shard"
where time > now() - 10s
```

The result will be in gigabytes. You can also see the size per database by
adding a `group by "database"`:

```
select sum(diskBytes) / 1024 / 1024 /1024 from _internal."monitor"."shard"
where time > now() - 10s group by "database"
```

On Fri, Nov 18, 2016 at 5:59 AM,  wrote:

> I would like to check disk usage percentage on a server during a load tes.
> Is there any way to capture disk usage metric in influxdb?
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/8812fbce-a17f-4168-aa72-c319a0b31bc6%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLCCav3fozAcm%2B91iimqekAO6Bs%2Bag7skXozySQpTAFMvg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Re: Install 1.1.0 deb package on Ubuntu fails

[Ross McDonald]

​Was this an upgrade of InfluxDB? The `/var/lib/influxdb/meta/raft.db` file
was removed with the 0.13 release, so it shouldn't be present in a 1.1.0
installation. Upgrading from pre-1.0 versions typically require extra steps
that are documented here
.

Also is this a fresh Ubuntu 16.04 installation, or was it upgraded from a
previous version of Ubuntu?

On Tue, Nov 29, 2016 at 10:49 AM,  wrote:

> Followup:
> for unknonw reasons I had to delete the file
>
> /var/lib/influxdb/meta/raft.db
>
> then
>
> sudo service influxdb start
>
> worked as expected.
> Looks like some script inside the DEB is not correct.
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/20b21e2c-a9a3-4d0d-8d0a-55239e528aa5%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLB6LDLLg2_msCF16i%3Do5vsp3OaZ5wBGiBctZ7Z-JHHeHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Can't start as service on FreeBSD jail FreeNAS

[Ross McDonald]

Are you using a custom init script, or the one from the repository? If it's
custom, could you provide it?

It also looks like the linker flags weren't set properly when building.
>From the startup message:

```
InfluxDB starting, version unknown, branch unknown, commit unknown
```

What version/commit was your binary built from?

On Thu, Dec 1, 2016 at 9:00 AM, Erik Näsström  wrote:

> Hi everyone
>
> I'm having som strange problems, tried searching and asking in some other
> forums but no solution so far!
>
> I have a FreeNAS server running 24/7 and wanted to run influxdb in a
> FreeBSD jail there to monitor my home assistant, curing chamber etc. with
> some nice graphs.
> Created a FreeBSD jail and followed the instructions in the manual and
> everything seems to work until I run the
>
> sudo service influxd onestart
>
>
> After that I just get a frozen screen with the "logo" until I terminate it
> with ctrl-c
>
> 
>
>
> If I just run *influxd* as a command tough it starts up just fine and I
> can access the web interface etc. but as soon as my terminal window closes
> It stops ofc.
> root@InfluxDB:/ # influxd
>
>  888   .d888 888   888b.  88b.
>888d88P"  888   888  "Y88b 888  "88b
>888888888   888888 888  .88P
>888   8b.  88 888 888  888 888  888 888888 888K.
>888   888 "88b 888888 888  888  Y8bd8P' 888888 888  "Y88b
>888   888  888 888888 888  888   X88K   888888 888888
>888   888  888 888888 Y88b 888 .d8""8b. 888  .d88P 888   d88P
>  888 888  888 888888  "Y8 888  888 888P"  888P"
>
> [run] 2016/12/01 15:52:45 InfluxDB starting, version unknown, branch
> unknown, commit unknown
> [run] 2016/12/01 15:52:45 Go version go1.7.3, GOMAXPROCS set to 4
> [run] 2016/12/01 15:52:45 no configuration provided, using default settings
> [store] 2016/12/01 15:52:45 Using data dir: /root/.influxdb/data
> [filestore] 2016/12/01 15:52:45 /root/.influxdb/data/home_
> assistant/autogen/6/1-1.tsm (#0) opened in 62.692µs
> [cacheloader] 2016/12/01 15:52:45 reading file /root/.influxdb/wal/home_
> assistant/autogen/6/_5.wal, size 0
> [shard] 2016/12/01 15:52:45 /root/.influxdb/data/home_assistant/autogen/6
> database index loaded in 445.72µs
> [store] 2016/12/01 15:52:45 /root/.influxdb/data/home_assistant/autogen/6
> opened in 1.008893ms
> [cacheloader] 2016/12/01 15:52:45 reading file
> /root/.influxdb/wal/_internal/monitor/9/_1.wal, size 4683137
> [filestore] 2016/12/01 15:52:45 /root/.influxdb/data/_
> internal/monitor/7/1-1.tsm (#0) opened in 284.13µs
> [cacheloader] 2016/12/01 15:52:45 reading file
> /root/.influxdb/wal/_internal/monitor/7/_3.wal, size 0
> [shard] 2016/12/01 15:52:45 /root/.influxdb/data/_internal/monitor/7
> database index loaded in 609.656µs
> [store] 2016/12/01 15:52:45 /root/.influxdb/data/_internal/monitor/7
> opened in 33.345368ms
> [filestore] 2016/12/01 15:52:45 /root/.influxdb/data/_
> internal/monitor/2/1-1.tsm (#0) opened in 8.266029ms
> [cacheloader] 2016/12/01 15:52:45 reading file
> /root/.influxdb/wal/_internal/monitor/2/_00010.wal, size 0
> [shard] 2016/12/01 15:52:45 /root/.influxdb/data/_internal/monitor/2
> database index loaded in 288.802µs
> [store] 2016/12/01 15:52:45 /root/.influxdb/data/_internal/monitor/2
> opened in 40.736365ms
> [filestore] 2016/12/01 15:52:46 /root/.influxdb/data/_
> internal/monitor/5/1-1.tsm (#0) opened in 11.463897ms
> [cacheloader] 2016/12/01 15:52:46 reading file
> /root/.influxdb/wal/_internal/monitor/5/_5.wal, size 0
> [shard] 2016/12/01 15:52:46 /root/.influxdb/data/_internal/monitor/5
> database index loaded in 418.476µs
> [store] 2016/12/01 15:52:46 /root/.influxdb/data/_internal/monitor/5
> opened in 12.352209ms
> [filestore] 2016/12/01 15:52:46 /root/.influxdb/data/_
> internal/monitor/1/1-1.tsm (#0) opened in 11.999839ms
> [cacheloader] 2016/12/01 15:52:46 reading file
> /root/.influxdb/wal/_internal/monitor/1/_00010.wal, size 0
> [shard] 2016/12/01 15:52:46 /root/.influxdb/data/_internal/monitor/1
> database index loaded in 153.833µs
> [store] 2016/12/01 15:52:46 /root/.influxdb/data/_internal/monitor/1
> opened in 12.485811ms
> [filestore] 2016/12/01 15:52:46 /root/.influxdb/data/home_
> assistant/autogen/3/3-2.tsm (#0) opened in 78.184409ms
> [cacheloader] 2016/12/01 15:52:46 reading file /root/.influxdb/wal/home_
> assistant/autogen/3/_00010.wal, size 0
> [shard] 2016/12/01 15:52:46 /root/.influxdb/data/home_assistant/autogen/3
> database index loaded in 438.502µs
> [store] 2016/12/01 15:52:46 /root/.influxdb/data/home_assistant/autogen/3
> opened in 79.00244ms
> [filestore] 2016/12/01 15:52:46 /root/.influxdb/data/_
> internal/monitor/4/1-1.tsm (#0) opened in 47.801502ms
> [cacheloader] 2016/12/01 15:52

Re: [influxdb] influxdb-1.1.0-1.x86_64 admin UI not listening on port 8083

[Ross McDonald]

> Any reason to deprecate admin ui in influxdb-1.1.0-1.x86_64?

This has been discussed in more detail here:

https://groups.google.com/forum/#!topic/influxdb/1jhjX8kQF6M/discussion

> I did set enabled = true in [admin] in influxdb.conf. I am still not able
to get to the admin ui using http://influxdbserverip:8083

Did you make sure to uncomment the `[admin]` section name? The
configuration should look similar to:

```
[admin]
enabled = true
```

On Wed, Nov 30, 2016 at 8:46 AM, Kaushal Shriyan 
wrote:

> Hi,
>
> I am running influxdb-1.1.0-1.x86_64 on CentOS Linux release 7.2.1511
> (Core).
>
> #cat /etc/redhat-release
> *CentOS Linux release 7.2.1511 (Core)*
> #rpm -qa | grep influxdb
> *influxdb-1.1.0-1.x86_64*
> #ps aux | grep influx
> influxdb  1165  0.1  0.1 376860 15908 ?Ssl  16:34   0:14
> /usr/bin/influxd -config /etc/influxdb/influxdb.conf
> root 29295  0.0  0.0 112648   976 pts/0S+   20:14   0:00 grep
> --color=auto influx
> #netstat -anp | grep 8086
> tcp6   0  0 :::8086 :::*LISTEN
>  1165/influxd
> #netstat -anp | grep 8083
> #
>
> I have couple of questions
>
>- Any reason to deprecate admin ui in influxdb-1.1.0-1.x86_64?
>- I did set enabled = true in [admin] in influxdb.conf. I am still not
>able to get to the admin ui using http://influxdbserverip:8083
>
> Any help will be highly appreciable. Please let me know if you need any
> additional details to debug the admin UI issue.
>
> Thanks in Advance.
>
> Regards,
>
> Kaushal
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/6257d8af-e7d0-45ec-85ab-7b4481fa4061%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLBcVOSJP4Qjexiy4-c7r1B%2Bq6bnA%3DLG%3DkrKokCzTvVhzw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] influxdb python tutorial not working

[Ross McDonald]

There is no precision specified on the writes, so they are defaulting to
nanosecond. The retention policy is also being set here

for 3 days so the writes are getting dropped as they're being written,
since the timestamps are very far in the past (in nanosecond land).

To fix it, you'll want to set the timestamp precision to "s" (seconds) here

:

```
client.write_points(series, retention_policy=retention_policy,
time_precision="s")
```


On Thu, Dec 1, 2016 at 2:38 PM,  wrote:

> Hi,
>
> I am new to influxdb.
>
> I have influxdb server version 1.0.1 running.
>
> I am using influxdb-python (influxdb-3.0.0) and trying the tutorial
>
> https://github.com/influxdata/influxdb-python/blob/master/
> examples/tutorial_server_data.py
>
> I get
>
> $ python tutorial_server_data.py
> Create database: tutorial
> Create a retention policy
> Write points #: 4320
> ResultSet({})
> Result: ResultSet({})
>
>
> i.e. I cannot read back any of the inserted values. I even relaxed the
> query to show all.
>
> Also when I do
>
> query = 'SHOW DATABASES'
> result = myclient.query(query)
> result
>
> I can see 'tutorial' in the output. So I am able to talk to my influxdb
> server
>
> But
> query = 'SHOW MEASUREMENTS'
> result = myclient.query(query)
> result
>
> give nothing.
>
> I assume I am missing something trivial.
>
> Can someone help?
>
> Thanks,
> Vikas
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/ac0d5500-8707-41d9-8ed8-8fca8c9e446b%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLDQFkhse-1YB_tYwOuqrsCageGZFx5gL10-Kfa6-v2FYw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Issues with Enterprise Replication

[Ross McDonald]

Hi Alan,

Can you open an issue with supp...@influxdb.com? That doesn't sound like
the expected behavior, and may be a symptom of an issue with the rebalance.

Thanks,
Ross

On Fri, Dec 2, 2016 at 8:13 AM,  wrote:

> Hi,
>
> Just downloaded the trial of the Enterprise version and am having some
> issues getting the replication working.
>
> I followed the procedure here
>
> http://docs.influxdata.com/enterprise/v1.1/guides/migration/
>
> to migrate data in from an OSS test cluster and everything want fine until
> the rebalance. Only the most recent (i.e. open shard) was replicated to the
> second node the others were not. Running "show shards" confirms that only
> the latest shard is owned by both nodes.
>
> Is this expected behavior?
>
> Thanks,
>
> Alan
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/8cb8cffd-d909-475d-924b-d1f1239db567%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLCo524%3Ds2zU6uuY2dTtCQjdL%2Bj7AO8ZhO5-4n-oMt_Pgg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] influxdb python tutorial not working

[Ross McDonald]

What if you set the RP to infinite? You'll want to change the "3d" to "inf":

```
client.create_retention_policy(retention_policy, 'inf', 3, default=True)
```

On Thu, Dec 1, 2016 at 5:42 PM,  wrote:

> On Thursday, December 1, 2016 at 2:13:39 PM UTC-8, Ross McDonald wrote:
> > There is no precision specified on the writes, so they are defaulting to
> nanosecond. The retention policy is also being set here for 3 days so the
> writes are getting dropped as they're being written, since the timestamps
> are very far in the past (in nanosecond land).
> >
> > To fix it, you'll want to set the timestamp precision to "s" (seconds)
> here:
> >
> > ```
> > client.write_points(series, retention_policy=retention_policy,
> time_precision="s")
> > ```
> >
> >
> >
> >
> > On Thu, Dec 1, 2016 at 2:38 PM,   wrote:
> > Hi,
> >
> >
> >
> > I am new to influxdb.
> >
> >
> >
> > I have influxdb server version 1.0.1 running.
> >
> >
> >
> > I am using influxdb-python (influxdb-3.0.0) and trying the tutorial
> >
> >
> >
> > https://github.com/influxdata/influxdb-python/blob/master/
> examples/tutorial_server_data.py
> >
> >
> >
> > I get
> >
> >
> >
> > $ python tutorial_server_data.py
> >
> > Create database: tutorial
> >
> > Create a retention policy
> >
> > Write points #: 4320
> >
> > ResultSet({})
> >
> > Result: ResultSet({})
> >
> >
> >
> >
> >
> > i.e. I cannot read back any of the inserted values. I even relaxed the
> query to show all.
> >
> >
> >
> > Also when I do
> >
> >
> >
> > query = 'SHOW DATABASES'
> >
> > result = myclient.query(query)
> >
> > result
> >
> >
> >
> > I can see 'tutorial' in the output. So I am able to talk to my influxdb
> server
> >
> >
> >
> > But
> >
> > query = 'SHOW MEASUREMENTS'
> >
> > result = myclient.query(query)
> >
> > result
> >
> >
> >
> > give nothing.
> >
> >
> >
> > I assume I am missing something trivial.
> >
> >
> >
> > Can someone help?
> >
> >
> >
> > Thanks,
> >
> > Vikas
> >
> >
> >
> > --
> >
> > Remember to include the version number!
> >
> > ---
> >
> > You received this message because you are subscribed to the Google
> Groups "InfluxData" 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/ac0d5500-8707-41d9-8ed8-8fca8c9e446b%40googlegroups.com.
> >
> > For more options, visit https://groups.google.com/d/optout.
>
> Thanks.
> I have it.
>
>
> print("Create a retention policy")
> retention_policy = 'server_data'
> client.create_retention_policy(retention_policy, '3d', 3,
> default=True)
>
> print("Write points #: {0}".format(total_records))
> client.write_points(series, time_precision='s',
> retention_policy=retention_policy)
>
> time.sleep(1)
>
> #query = "SELECT MEAN(value) FROM {} WHERE time > now() - 10d GROUP BY
> time(500m)".format(metric)
> query = "SELECT MEAN(value) FROM {}".format(metric)
> result = client.query(query, database=DBNAME)
> print(result)
> print("Result: {0}".format(result))
>
> The result is still empty.
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/f197875b-2820-490b-90b2-51b3d2e16a9c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLCkf5DV092H5%3DPs8LPMu%3DjrmL3%3DyQZtX%3D6Nd0onACm0Ew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Run telegraf inside docker, how to collect net, processors input in the host?

[Ross McDonald]

You will need to expose the necessary dirs/files/sockets to the Telegraf
container so that it can collect stats from the host machine. Here is what
I was able to find:

```
docker run \
  -v /sys:/rootfs/sys:ro \
  -v /proc:/rootfs/proc:ro \
  -v /var/run/docker.sock:/var/run/docker.sock:ro \
  -v /var/run/utmp:/var/run/utmp:ro \
  telegraf
```

Though the exact files may depend on your OS, distribution, and/or version.

On Thu, Dec 1, 2016 at 7:36 AM, jiaqing.chen 
wrote:

> *description*
>
> Now telegraf is running inside docker.I set input config to collect net,
> processor measurements, but the net and processors measurements collected
> is the docker container’s measurements which run telegraf. In fact, my mind
> is to collect that measurements on the host which the telegraf docker is
> running on.How can I fix it?
>
> *my telegraf input conf*
>
> # Get the number of processes and group them by status
>
> [[inputs.processes]]
>
>   # no configuration
>
>
>
> # Read metrics about swap memory usage
>
> [[inputs.swap]]
>
>   # no configuration
>
>
>
> # Read metrics about system load & uptime
>
> [[inputs.system]]
>
>   # no configuration
>
>
>
> # Read metrics about network interface usage
>
> [[inputs.net]]
>
>   ## By default, telegraf gathers stats from any up interface (excluding
> loopback)
>
>   ## Setting interfaces will tell it to gather these explicit interfaces,
>
>   ## regardless of status.
>
>   ##
>
>   interfaces = ["eth0", "eth1"]
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/tencent_702DA616D5F90137E11AC2C9%40qq.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLAjvs7CrQ-boNGuAA50yy7mxbag9FqurcQabKgFA%2BErcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Continuous Queries for downsampling data

[Ross McDonald]

I don't believe this is currently possible. There is a Github issue open
regarding this problem here
.

On Wed, Dec 7, 2016 at 2:45 PM,  wrote:

> Hi,
>
> I've created the following CQ:
>
> CREATE CONTINUOUS QUERY cq_shortTerm
>  ON my_db BEGIN
>   SELECT mean(*) INTO my_db.shortTerm.:MEASUREMENT FROM
> my_db.realTime./.*/ GROUP BY time(10m), *
> END
>
> The problem is that the CQ changes my "fields" name to something like
> "mean_field", this happens because I'm using a wildcard in the function
> mean.
>
> Is it possible to make the same maintaining the original the field name?
>
> RG
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/02de7cef-8022-4cb8-9f74-a13e074d3606%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLCyRtrufH1KAqrgXVDh3%3DY3JrT7Y6Zq5EpsaUda5%3DO65g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Is it possible to cast a mean value to a integer ?

[Ross McDonald]

It is not currently possible to cast the function (mean) result. You can
cast the field prior to having the function called on it, though. For
example:

```
SELECT mean("value"::integer) AS value FROM "measurement" WHERE "Host" =
'XYZ'
```

Will work, but probably isn't what you want. Kapacitor has the ability to cast
results
,
however it may be overkill if you are not already using it in your stack.
I'd recommend opening a feature request
 if you'd like to see
this functionality added.

On Tue, Dec 6, 2016 at 7:15 AM,  wrote:

> Hi !
>
> Following query does not work ...
>
> SELECT mean("value")::integer AS value FROM "measurement" WHERE "Host" =
> 'XYZ'
>
> The documentation only has following examples:
> SELECT "water_level"::integer FROM "h2o_feet"
>
>
> greets
> claus
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/b349dc4f-d74d-4060-952e-e524b44d6a9e%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLABAH%2Bk514OCF62pnUdusS1E62eg%3DQhH3Hz5ycug5HdLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Fwd: Please answer Kapacitor - Query

[Ross McDonald]

1) You can run a `kapacitor disable ` to stop a running task, or
`kapacitor delete tasks ` to delete it.

2) Please review the documentation here
.

3) Yes, there are many ways to do this. For a 2 hour long duration, I'd
recommend using a batch task. For example (assuming Telegraf data), to
alert if the CPU utilization was over 50 (which is the same as CPU idle
being less than 50) for 2 hours, it would look similar to:

```
batch
|query('SELECT max(usage_idle) FROM "telegraf"."autogen"."cpu"')
  .period(2h) // How far to query back
  .every(2h) // How often to run the query
  .groupBy('host')
|alert()
  .crit(lambda: "max" < 50)
```

There are more examples in the documentation here
.

On Mon, Dec 5, 2016 at 1:11 PM, Nikhil Agrawal 
wrote:

> Hi,
>
> Please reply if you know the solutions.
>
> Query 1: How to stop the running tick script.
>
>
> Query 2: How to customized email alert, Please find attached tick script,
> config file, Current email alert and required email alert format.
>
> Query 3: is it possible to get alert - example if cpu memory > 50 for more
> then 2 hours.
>
>
>
>
>
> --
>
> *Thanks,Nikhil Agrawal | +1 408 505 8443 <%2B1%20408%20505%208443>*
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/CAMtKHpqBy3vSvrZw06zqJp4uCHgLQQ7Kc%2BbMa_9htP7oDpc2tg%
> 40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLD42Odr86%3DgJV8DW64wSg7bFpi2YzRsV2HodMr37B7Hbg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Re: Install 1.1.0 deb package on Ubuntu fails

[Ross McDonald]

It seems like your influxdb unit is masked for some reason. Can you try
unmasking it and then rerunning the installation? You can unmask it with
the command:

```
sudo systemctl unmask influxdb.service
```

On Tue, Dec 13, 2016 at 7:45 AM,  wrote:

> Hi,
> I have a similar problem.
>
> After installing influxdb form the ubuntu repository I wanted to replace
> it by the newest version form influxdb.com.
>
> After uninstalling the old version,  I tried "sudo dpkg -i
> influxdb_1.1.1_amd64.deb". But I get an error:
>
> henp@DESMUCDEV01:~$ sudo dpkg -i influxdb_1.1.1_amd64.deb
> Vormals nicht ausgewähltes Paket influxdb wird gewählt.
> (Lese Datenbank ... 124365 Dateien und Verzeichnisse sind derzeit
> installiert.)
> Vorbereitung zum Entpacken von influxdb_1.1.1_amd64.deb ...
> Entpacken von influxdb (1.1.1-1) ...
> influxdb (1.1.1-1) wird eingerichtet ...
> Failed to execute operation: Unit file is masked
> dpkg: Fehler beim Bearbeiten des Paketes influxdb (--install):
>  Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1
> zurück
> Trigger für man-db (2.7.5-1) werden verarbeitet ...
> Fehler traten auf beim Bearbeiten von:
>  influxdb
>
> What am I doing wrong?
> Any suggestion is welcome.
> Thank you.
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/9c5ced40-a2cc-48a6-aae4-b455a3438ef4%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLCXqsJ7a4ckwLdmhaMK5Wi0qfUqT2tKVfRHWkQJok6-sQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Automatic merge does not seem to work

[Ross McDonald]

Are the fields part of the same series
 (do
they share the same tag keys and values)? If not, they will be displayed on
different lines.

Thanks,
Ross

On Mon, Dec 12, 2016 at 3:35 AM,  wrote:

> Hi,
>
> I have a problem with queries like
>
> select var1,var2 from measure1 where time >= '2015-03-01' Limit 4
>
> where the field var1 was added before the field var2 to the database.
> Influx returns e.g.
>
> measure1
> time var1  var2
> 2015-03-01T00:00:00Z 3908
> 2015-03-01T00:00:00Z   3
> 2015-03-01T00:00:02Z 3794
> 2015-03-01T00:00:02Z   3
>
> but I expected that there is an automatic join on the timestamp and influx
> response looks like
>
> measure1
> time var1  var2
> 2015-03-01T00:00:00Z 3908  3
> 2015-03-01T00:00:02Z 3794  3
>
> If I add another field var3 then the influx partly joins the series
>
> measure1
> time var1  var2  var3
> 2015-03-01T00:00:00Z 3908
> 2015-03-01T00:00:00Z   3 2
> 2015-03-01T00:00:02Z 3794
> 2015-03-01T00:00:02Z   3 1
>
>
> I added the data via the DataFrameClient from the python influx library:
>
> db.write_points(df, 'measure1', batch_size=1000)
>
> where df is a pandas DataFrame containing the column var1.
>
> And for the fields added afterwards:
>
> db.write_points(pd.DataFrame(data={'var2': 3}, index=df.index),
> 'measure1', batch_size=5)
>
> where df is again a pandas DataFrame which results from a influxdb query
> for var1 in measure1.
>
> Am I doing something wrong and is this behavior as expected? Then how is
> it possible to merge the series?
>
> I was using the version 1.0 of influxdb and updated to the current version
> on github a few days ago (same behavior).
>
> Thanks in advance!
>
> Best regards,
> Marc
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/b52ade44-5fed-4184-a604-769aa3bf749e%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLC_uVz-LPHSi4j_AgYePhRje84zCj1dsSmhPBDZrCJm_Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Is there a batch limit on Kapacitor batch process?

[Ross McDonald]

I believe this is due to the default row limit in InfluxDB's HTTP handler,
not Kapacitor. Can you try setting InfluxDB's max-row-limit

(in the HTTP configuration) to 0? For example:

```
[http]
  max-row-limit = 0
```

Thanks,
Ross


On Tue, Dec 13, 2016 at 11:57 AM,  wrote:

> Hi all,
>
> When I run the following TICKscript:
>
> batch
> |query('SELECT mean(UPTIME) as meanUptime FROM
> devices."three_weeks_rp".monitorData')
> .groupBy(*)
> .period(15m)
> .every(15m)
> .align()
> |influxDBOut()
> .database('devices')
> .retentionPolicy('test_rp')
> .measurement('meanMonitorData')
> .precision('s')
>
> It only inserts 1 datapoints on devices.test_rp.meanMonitorData. I
> know I have more than 10 devices (deviceId is a tag) and data has been
> saved for all of them every 5 minutes.
>
> When I run
> kapacitor show 
> I get
>
> 
> DOT:
> digraph batch_downsample_task {
> graph [throughput="0.00 batches/s"];
>
> query1 [avg_exec_time_ns="0s" batches_queried="1"
> points_queried="1" query_errors="0" ];
> query1 -> influxdb_out2 [processed="1"];
>
> influxdb_out2 [avg_exec_time_ns="27.349µs" points_written="1"
> write_errors="0" ];
> }
> ...
>
> Why batches_queries is 1? Is there a configuration for this?
> That value increases by 1, after 45 minutes(batch ran 3 times), value
> is 3
>
> Best regards,
>
> Carlo
>
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/7d3b52c5-a48f-4110-82f6-8cabb0ff1c22%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLD%3D_80Yx5HrEJZFqMZU47Fu0yOSpJvy8fc2HUjKYWgjbw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] [Influxdb] Influxdb Yum Repo Fails

[Ross McDonald]

What distribution and version are you running? It doesn't look like your
yum is substituting the variables properly. The correct URL is:

https://repos.influxdata.com/rhel/7/x86_64/stable/repodata/repomd.xml

Where `$releasever` is substituted for the current CentOS/RHEL release
version (6, 7, etc). As a workaround, you can manually update the URL to
use a hard-coded release version (like the URL above).

Thanks,
Ross

On Tue, Dec 13, 2016 at 6:06 PM, Alan Wilson 
wrote:

> Hi.  When attempting to use the Influxdb yum repo configuration described
> here-> https://docs.influxdata.com/influxdb/v1.1/
> introduction/installation/#installation I get an error that the repo does
> not point to a usable file. Is the yum installation approach a stable
> service or should we check the documentation for updates?
>
> Thanks!
> 
> # yum --installroot=/opt/influxdb install influxdb.x86_64
>
>  One of the configured repositories failed (InfluxDB Repository - RHEL
> $releasever),
>  and yum doesn't have enough cached data to continue.
> ...
> failure: repodata/repomd.xml from influxdb: [Errno 256] No more mirrors to
> try.
> https://repos.influxdata.com/rhel/$releasever/x86_64/stable/
> repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
>
>
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/a18776f6-fb4a-4c87-902f-bf508b9b3c78%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLApBckc-%2BT43ciDTvp%2B9W-JV%2Bvn6SNyb3Bwet3oiztz5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Show retention policies where/like clause supported?

[Ross McDonald]

That is not supported at the moment. Please open a feature request
 if you would like to
see it added.

On Wed, Dec 14, 2016 at 11:05 AM, Jeffery K <
jeffery.k...@sightlinesystems.com> wrote:

> Is there a way to specify a filtering mechanism on the "show retention
> policies on databaseName" query?
> I'm using a java http client to try and check a retention policies
> duration, to make sure it doesn't need to be updated, to a new value.
> Right now, I can get the whole list, and iterate through them looking for
> the specific retention policy I want, but that seems like un-necessary load
> on the DB, network traffic over the network that could benefit from a query
> that i could specify a name condition filter on.
>
> I.E. show retention policies where name /name_I_Want/
>
> hmmm, digging a little deeper, I may have found an answer. this page seems
> to indicate it's not supported. https://docs.influxdata.com/influxdb/v1.1/
> query_language/data_exploration/#regular-expressions-in-queries
> Any chance of getting this added as a new feature request?
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/d5ac1e8f-d5ff-4c5b-a4b4-b32e0f4e0278%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLARtHHtyXesbRYe8ZODt%2BHFOkYazx8O1E6PGpEL%3DbA4iQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] [Influxdb] Influxdb Yum Repo Fails

[Ross McDonald]

Thank you for letting us know about the issue on RHEL 7, I'll file an issue
to get that fixed. Regarding:

> Is the rpm installation relocatable?

I don't believe so. I can create an issue for that as well.

On Wed, Dec 14, 2016 at 5:30 PM, Alan Wilson 
wrote:

> Another question.  Is the rpm installation relocatable?  It seems to place
> all of the files that were formally in /etc in /opt/etc.
>
> Thanks!
>
>
> On Wednesday, December 14, 2016 at 4:42:32 PM UTC-6, Alan Wilson wrote:
>>
>> Thanks.  We ended the url at ../stable and everything worked.  The
>> original baseurl line seems to work ok on Centos 6 but fails on Redhat 7.
>>
>> Thanks
>>
>> On Wednesday, December 14, 2016 at 9:28:55 AM UTC-6, Ross McDonald wrote:
>>>
>>> What distribution and version are you running? It doesn't look like your
>>> yum is substituting the variables properly. The correct URL is:
>>>
>>> https://repos.influxdata.com/rhel/7/x86_64/stable/repodata/repomd.xml
>>>
>>> Where `$releasever` is substituted for the current CentOS/RHEL release
>>> version (6, 7, etc). As a workaround, you can manually update the URL to
>>> use a hard-coded release version (like the URL above).
>>>
>>> Thanks,
>>> Ross
>>>
>>> On Tue, Dec 13, 2016 at 6:06 PM, Alan Wilson 
>>> wrote:
>>>
>>>> Hi.  When attempting to use the Influxdb yum repo configuration
>>>> described here-> https://docs.influxdata.com/influxdb/v1.1/introductio
>>>> n/installation/#installation I get an error that the repo does not
>>>> point to a usable file. Is the yum installation approach a stable service
>>>> or should we check the documentation for updates?
>>>>
>>>> Thanks!
>>>> 
>>>> # yum --installroot=/opt/influxdb install influxdb.x86_64
>>>>
>>>>  One of the configured repositories failed (InfluxDB Repository - RHEL
>>>> $releasever),
>>>>  and yum doesn't have enough cached data to continue.
>>>> ...
>>>> failure: repodata/repomd.xml from influxdb: [Errno 256] No more mirrors
>>>> to try.
>>>> https://repos.influxdata.com/rhel/$releasever/x86_64/stable/
>>>> repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
>>>>
>>>>
>>>>
>>>> --
>>>> Remember to include the version number!
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "InfluxData" 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/a18776f6-fb4a-4c87-902f-bf508b9b3c78%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/influxdb/a18776f6-fb4a-4c87-902f-bf508b9b3c78%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/1a73221f-a059-42c9-9b33-01acec7a7be8%40googlegroups.com
> <https://groups.google.com/d/msgid/influxdb/1a73221f-a059-42c9-9b33-01acec7a7be8%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLCf3AE15KKU9%2BoGNfeT2jC3uokwZGtsEyEmD4bKH2NjPg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] What can be deleted from /var/influxdb after relocating Meta and Data directories

[Ross McDonald]

Hi Alan,

The InfluxDB process uses only what's in the configuration, so assuming all
of your configuration has been migrated to use `/opt/influxdb`, then
everything under `/var/lib/influxdb` can be removed. I would recommend
double checking that the InfluxDB process is using the correct directories,
though (and maybe keep a local backup of `/var/lib/influxdb` around for a
little while, just to be safe).

Thanks,
Ross

On Thu, Dec 22, 2016 at 1:19 PM, Alan Wilson 
wrote:

> Hi.  The installation defaults the meta and data files to
> /var/lib/influxdb.  By the operations policy here, the /var filesystem is
> small and belongs to the admin/operations teams.  We started influxdb and
> the meta and data files were built in the default locations. After
> installation we set the meta, wal, and data directories to sit under
> /opt/influxdb and our files were created there.
>
> Which parts of the original installation can be removed?
>
> Thanks!
> Alan
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/c6465fe0-56ce-4c7f-bfc4-094325150c66%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLBsVfgciNKPSgUa6G-p7yWk2%3DG5BGtypD2NBshmYDiQsw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Kapacitor Java Library

[Ross McDonald]

I don't believe we have any official plans at the moment, however the API
is documented in detail here

if you would like to start your own.

Thanks,
Ross

On Mon, Dec 19, 2016 at 11:19 AM,  wrote:

> Is there any plan to provide Java Library to create task and templates and
> get alerts in the Java Enterprise application context
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/feb99811-eefb-46d7-87d5-a846dbb88643%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLBnrQg49yzR4aNxxKFHo28jBFxgTgBjEanbiPmADYuQjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Kapacitor index.Tags on "com.docker.swarm.service.name"

[Ross McDonald]

Does this not work?

{{ index .Tags "com.docker.swarm.service.name" }}

There is a space between 'index' and '.Tags'. The brackets need to be
together. And it looks like there is a typo with 'sswarm' (should be
'swarm').

On Fri, Dec 30, 2016 at 11:12 PM, Aditya C.S  wrote:

> How to write custom message with tag value of "
> com.docker.swarm.service.name"?. Below is my script. However, tag value
> is displayed as null in the alert. I even tried this way ".message('{{
> .Level}}: { {index.Tags "[[com.docker.sswarm.service.name]]" }} has high
> cpu usage: {{ index .Fields "cpu_usage" }}')".
>
>  batch
> |query('''
>  select sum(usage_percent) as cpu_usage from
> "telegraf"."default"."service_cpu_usage" where "
> com.docker.swarm.service.name"='jenkins' order by time desc
> ''')
>.period(15m)
>.every(1m)
>.groupBy(time(10s), 'com.docker.swarm.service.name')
>
> |alert()
> .message('{{ .Level}}: { {index.Tags "com.docker.sswarm.service.
> name" }} has high cpu usage: {{ index .Fields "cpu_usage" }}')
> .crit(lambda: "cpu_usage" > 80)
> .log('/opt/kap/container_cpu_alerts.log')
> .exec('/opt/kap/container_cpu_alert.py')
>
>
> Thanks,
> Aditya C S
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/309d9300-4191-41d7-b727-8ef81ea8da12%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLBFFX_2ADqdNrotROu-kyFpieiXrqh8v9yi97V0dPk1Vg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Kapacitor index.Tags on "com.docker.swarm.service.name"

[Ross McDonald]

In that case I would recommend adding a `log()` node to your script to
examine the data before it hits the alert. For example, updating your
script to look similar to:

...
|log()
|alert()
.message('{{ .Level}}: {{ index .Tags "com.docker.swarm.service.name"
}} has high cpu usage: {{ index .Fields "cpu_usage" }}')
...

This will dump all of the data in the stream to the Kapacitor log file. Can
you provide a few samples from the output when the alert is triggered?

On Sat, Dec 31, 2016 at 2:11 PM, Aditya C.S  wrote:

> Sorry for the typo.  I have tried {{ index .Tags "
> com.docker.swarm.service.name" }}.
> It's not working.
>
> Thanks,
> Aditya C S
>
> On Sat 31 Dec, 2016, 11:25 PM Ross McDonald,  wrote:
>
> Does this not work?
>
> {{ index .Tags "com.docker.swarm.service.name" }}
>
> There is a space between 'index' and '.Tags'. The brackets need to be
> together. And it looks like there is a typo with 'sswarm' (should be
> 'swarm').
>
> On Fri, Dec 30, 2016 at 11:12 PM, Aditya C.S  wrote:
>
> How to write custom message with tag value of "
> com.docker.swarm.service.name"?. Below is my script. However, tag value
> is displayed as null in the alert. I even tried this way ".message('{{
> .Level}}: { {index.Tags "[[com.docker.sswarm.service.name]]" }} has high
> cpu usage: {{ index .Fields "cpu_usage" }}')".
>
>  batch
> |query('''
>  select sum(usage_percent) as cpu_usage from
> "telegraf"."default"."service_cpu_usage" where "
> com.docker.swarm.service.name"='jenkins' order by time desc
> ''')
>.period(15m)
>.every(1m)
>.groupBy(time(10s), 'com.docker.swarm.service.name')
>
> |alert()
> .message('{{ .Level}}: { {index.Tags "com.docker.sswarm.service.
> name" }} has high cpu usage: {{ index .Fields "cpu_usage" }}')
> .crit(lambda: "cpu_usage" > 80)
> .log('/opt/kap/container_cpu_alerts.log')
> .exec('/opt/kap/container_cpu_alert.py')
>
>
> Thanks,
> Aditya C S
>
> --
> Remember to include the version number!
> ---
>
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/309d9300-4191-41d7-b727-8ef81ea8da12%40googlegroups.com
> <https://groups.google.com/d/msgid/influxdb/309d9300-4191-41d7-b727-8ef81ea8da12%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "InfluxData" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/influxdb/KEy900H4vtE/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAD8sRLBFFX_2ADqdNrotROu-kyFpieiXrqh8v9yi97V0dPk1Vg%
> 40mail.gmail.com
> <https://groups.google.com/d/msgid/influxdb/CAD8sRLBFFX_2ADqdNrotROu-kyFpieiXrqh8v9yi97V0dPk1Vg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/CAFEGz4maC9HDMYwnO0m2LN2KQKRNO98ZJfFfHnwt-sSW5VgRkg%40mail.
> gmail.com
> <https://groups.google.com/d/msgid/influxdb/CAFEGz4maC9HDMYwnO0m2LN2KQKRNO98ZJfFfHnwt-sSW5VgRkg%40mail.gmail.com?utm_medium=email&utm_s

Re: [influxdb] Conditional Update

[Ross McDonald]

Regarding the question:

> Is there a way to only allow the insert of the estimated value in case
there is no actual measurement already in place?

Not currently. The only way to do this would be to query for the data first
to see if there is a gap.

On Wed, Jan 4, 2017 at 10:18 AM, 'Sebastian Voss' via InfluxData <
influxdb@googlegroups.com> wrote:

> I'm want to write a data stream of temperature reading to InfluxDB
> (timestamp, weather station and temperature value). Normally the data is
> reported every 10 minutes. But sometimes there are data gaps and therefore
> I implemented a scheduled process to fill those gaps. It runs every hour,
> calculates an estimated values and fills the missing points in InfluxDB
> (adding an "estimated=true" field). At the same time the weather station is
> sometimes sending missing data points later on. In case this happens while
> my gap filling process is running it can happen that actual values are
> overridden by estimated values.
>
> Is there a way to only allow the insert of the estimated value in case
> there is no actual measurement already in place?
>
> My current assumption is that I have to write the estimated flag to a tag
> (instead of field) to essentially create different series. The drawback if
> that my client code needs to filter out estimated values in they co-exist
> with actual measurement for the same timestamp.
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/0f42bacd-fd61-43e9-9a7d-ab9f73cd61ee%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLB46iYnv%2Bc9PVokkHAO4WOwt%3DyYx0MKu8hYqzAB7tqGAg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Is there a batch limit on Kapacitor batch process?

[Ross McDonald]

Sorry for the delay! Just to make sure, did you restart the InfluxDB
service once the configuration change was made? If so, what version of
InfluxDB are you running?

When running tests on my local instance (running v1.1.0), I'm able to query
for more than 10,000 points at a time, so it's strange that you are still
seeing that cap.


On Thu, Dec 15, 2016 at 11:38 AM,  wrote:

> On Tuesday, December 13, 2016 at 3:49:39 PM UTC-5, Ross McDonald wrote:
> > I believe this is due to the default row limit in InfluxDB's HTTP
> handler, not Kapacitor. Can you try setting InfluxDB's max-row-limit (in
> the HTTP configuration) to 0? For example:
> >
> > ```
> >
> > [http]
> >
> >   max-row-limit = 0
> > ```
> >
> >
> > Thanks,
> >
> > Ross
> >
> >
> >
> >
> >
> > On Tue, Dec 13, 2016 at 11:57 AM,   wrote:
> > Hi all,
> >
> >
> >
> > When I run the following TICKscript:
> >
> >
> >
> > batch
> >
> > |query('SELECT mean(UPTIME) as meanUptime FROM
> devices."three_weeks_rp".monitorData')
> >
> > .groupBy(*)
> >
> > .period(15m)
> >
> > .every(15m)
> >
> > .align()
> >
> > |influxDBOut()
> >
> > .database('devices')
> >
> > .retentionPolicy('test_rp')
> >
> > .measurement('meanMonitorData')
> >
> > .precision('s')
> >
> >
> >
> > It only inserts 1 datapoints on devices.test_rp.meanMonitorData. I
> know I have more than 10 devices (deviceId is a tag) and data has been
> saved for all of them every 5 minutes.
> >
> >
> >
> > When I run
> >
> > kapacitor show 
> >
> > I get
> >
> >
> >
> > 
> >
> > DOT:
> >
> > digraph batch_downsample_task {
> >
> > graph [throughput="0.00 batches/s"];
> >
> >
> >
> > query1 [avg_exec_time_ns="0s" batches_queried="1"
> points_queried="1" query_errors="0" ];
> >
> > query1 -> influxdb_out2 [processed="1"];
> >
> >
> >
> > influxdb_out2 [avg_exec_time_ns="27.349µs" points_written="1"
> write_errors="0" ];
> >
> > }
> >
> > ...
> >
> >
> >
> > Why batches_queries is 1? Is there a configuration for this?
> >
> > That value increases by 1, after 45 minutes(batch ran 3 times),
> value is 3
> >
> >
> >
> > Best regards,
> >
> >
> >
> > Carlo
> >
> >
> >
> >
> >
> > --
> >
> > Remember to include the version number!
> >
> > ---
> >
> > You received this message because you are subscribed to the Google
> Groups "InfluxData" 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/7d3b52c5-a48f-4110-82f6-8cabb0ff1c22%40googlegroups.com.
> >
> > For more options, visit https://groups.google.com/d/optout.
>
> Hi Ross,
>
> Sorry for late reply.
> I changed the max-row-limit to 0 (even though documentation does not say
> that a zero value means no limit), but still I process 1, see results
> after executing kapacitor show :
>
> query1 [avg_exec_time_ns="0s" batches_queried="1"
> points_queried="1" query_errors="0" ];
> query1 -> influxdb_out2 [processed="1"];
>
> influxdb_out2 [avg_exec_time_ns="103.297µs" points_written="1"
> write_errors="0" ];
>
> I even changed the max-row-limit to 20 to see if something changes but
> it is still the same.
>
> Is there anything else I need to do? Also after changing max-row-limit to
> zero and executing a query (using the java client) that must return 20
> items it returns 1.
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/c465726d-0317-4f1a-9f6b-5c6580a51883%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLCBqjHWRHqp2ud7DV6dUTxu4Zy9sknNufosg840oVdj9A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] kapacitor -- node|last() function

[Ross McDonald]

​If the task stops executing, there should be an error stating why it was
stopped next to the `Error:` heading in the `kapacitor show` output.

Can you share the output to the output of `kapacitor show` for your task?
Is there anything in the Kapacitor service logs for your task that look
like an error?

On Mon, Jan 9, 2017 at 12:45 AM,  wrote:

> Hi,
>
> I have the following :
> Kapacitor,  v1.1.1
> InfluxDB, v 1.1.1
> Telegraf, v1.1.2
>
>
> I am having a little bit of trouble with the |last() function. (Or maybe
> my understanding of it)
> My TICK script gets loaded into Kapacitor with out any error.
> After some time the "kapacitor show tasks" command lists the task as
> "Executing:false".
> I guess this is when the task has its first match on the incoming data
> stream.
>
> I have this in my TICK script :
> 
> var window = 1m
> var every = 1m
>
> var data = stream
> |from()
> .measurement('system')
> .groupBy('host')
> |window()
> .period(window)
> .every(every)
> |last('uptime')
> .as('last_uptime')
> 
>
> "system" is my measurement in InfluxDB.
> "host" is a tag value in InfluxDB.
> "uptime" is a field("integer") in InflxuDB.
>
> I use the following to mach :
> 
> var crit = lambda: "last_uptime" < 300
> var critReset = lambda: "last_uptime" >= 300
> 
>
> If I remove the "|Last()" function than the TICK scrip stays enabled, but
> gives the wrong outcome.
> IE; I get alerts for all points when "uptime" is from 0 to 300.
> I just want to match on the last value.
>
> Thanks for your help
> Brendan
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/1f8c74ac-fa94-4286-9720-5b230d320722%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLCYqrJM6AjCK8fNetc3yhsCWtQmwyTFRp5U-gNtG_zhTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] kapacitor -- node|last() function

[Ross McDonald]

You're most likely seeing  values there because Telegraf is not
sending the uptime field with every point to the 'system' measurement.
There are a couple of different ways to handle this issue:

* You can use a `|default()
<https://docs.influxdata.com/kapacitor/v1.1/nodes/default_node/>` node to
default the value to something if it is not present. This won't quite work
with uptime, though, since there isn't a "default" value for a system's
uptime.

* You can convert your task to use batch
<https://docs.influxdata.com/kapacitor/v1.1/nodes/batch_node/> instead of
stream, which will be equivalent to running the query on the InfluxDB CLI.
This would make your task look more like this:

```
var data = batch
|query('SELECT last("uptime") as last_uptime FROM system')
.period(window)
.every(every)
.groupBy('host')
```

For this issue in particular I would recommend using a batch task.

On Mon, Jan 9, 2017 at 7:54 PM,  wrote:

> Hi Ross,
>
> Thanks for the reply.
> I do see the error in the `kapacitor show`, I must of missed it the first
> time! Here is the message :
> "Error: last3: invalid influxql func last with field uptime: invalid field
> type: "
>
> I don't get why that is  ?
>
> The influxdb query "select last(uptime) from system" returns correctly.
> If I run "SHOW FIELD KEYS on systems", I see that the "uptime" field is an
> "integer"
>
> Thanks
>
> On Tuesday, January 10, 2017 at 4:20:29 AM UTC+8, Ross McDonald wrote:
>>
>> ​If the task stops executing, there should be an error stating why it was
>> stopped next to the `Error:` heading in the `kapacitor show` output.
>>
>> Can you share the output to the output of `kapacitor show` for your task?
>> Is there anything in the Kapacitor service logs for your task that look
>> like an error?
>>
>> On Mon, Jan 9, 2017 at 12:45 AM,  wrote:
>>
>>> Hi,
>>>
>>> I have the following :
>>> Kapacitor,  v1.1.1
>>> InfluxDB, v 1.1.1
>>> Telegraf, v1.1.2
>>>
>>>
>>> I am having a little bit of trouble with the |last() function. (Or maybe
>>> my understanding of it)
>>> My TICK script gets loaded into Kapacitor with out any error.
>>> After some time the "kapacitor show tasks" command lists the task as
>>> "Executing:false".
>>> I guess this is when the task has its first match on the incoming data
>>> stream.
>>>
>>> I have this in my TICK script :
>>> 
>>> var window = 1m
>>> var every = 1m
>>>
>>> var data = stream
>>> |from()
>>> .measurement('system')
>>> .groupBy('host')
>>> |window()
>>> .period(window)
>>> .every(every)
>>> |last('uptime')
>>> .as('last_uptime')
>>> 
>>>
>>> "system" is my measurement in InfluxDB.
>>> "host" is a tag value in InfluxDB.
>>> "uptime" is a field("integer") in InflxuDB.
>>>
>>> I use the following to mach :
>>> 
>>> var crit = lambda: "last_uptime" < 300
>>> var critReset = lambda: "last_uptime" >= 300
>>> 
>>>
>>> If I remove the "|Last()" function than the TICK scrip stays enabled,
>>> but gives the wrong outcome.
>>> IE; I get alerts for all points when "uptime" is from 0 to 300.
>>> I just want to match on the last value.
>>>
>>> Thanks for your help
>>> Brendan
>>>
>>> --
>>> Remember to include the version number!
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "InfluxData" 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/1f8c74ac-fa94-4286-9720-5b230d320722%40googlegroups.com
>>> <https://groups.google.com/d/msgid/influxdb/1f8c74ac-fa94-4286-9720-5b230d320722%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.c

Re: [influxdb] New, numbered tags created after using a renamed/migrated measurement

[Ross McDonald]

​If you don't use a `GROUP BY *` at the end of a `SELECT ... INTO ...`
query, then any tags are automatically converted to fields. You're most
likely seeing the new tags with numbers due to there already being a field
by the same name. This is mentioned in the documentation here

.

You'll want to update your query to look more like:

```

select * into pgdata2 from pgdata1 group by *
```

To carry the tags over correctly.

On Wed, Jan 11, 2017 at 5:53 AM,  wrote:

> Hi!
>
> I'm using Telegraf's postgresql_extensible input to store values into
> Influxdb, and I found that after renaming/migrating the measurement by this
> influxdb command:
>
> "select * into pgdata2 from pgdata1"
>
> and later inserting the new data (same tags) into the new measurement
> 'pgdata2' there will be some new tags, for example host becomes host_1, db
> becomes db_1, but the actual value tag stays the same.
>
> If I migrate again into pgdata3, then there will be host_1_1, db_1_1. So
> now I have three similar tags: host, host_1, host_1_1. (New data goes into
> the last one.)
>
> I checked Telegraf with tcpdump and I saw that Telegraf was sending the
> correct names.
>
> Is this behavior a bug or I just don't know something?
>
> Regards,
> Krisztián
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/19f673d5-3469-4bc5-b2d4-c90f026002ca%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLCBK5SjUgoGDjNVO7AbOz%3D%2BTx_wNUJ%3DYpZ_sGx87VpoAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Re: Influx DB queries are slow

[Ross McDonald]

A `select *` query without a time boundary will currently result in poor
performance. Please see the issue here
 for more information.

On Thu, Jan 12, 2017 at 3:34 AM,  wrote:

> On Wednesday, January 11, 2017 at 2:46:14 PM UTC+5:30,
> abhatt...@opentable.com wrote:
> > I have an InfluxDB instance running in a linux vm (8 gb of ram and  4
> cores).
> >
> > I am writing data to it over http from a message queue.
> >
> > My data structure written into influx looks like the following :
> >
> >
> > {
> > "measurement": "test",
> > "tags": {
> > "field1": integer, [range 0 - 50k]
> > "field2": integer, [range 1-10]
> > "field3": integer, [0/1]
> > "field4": integer,[0/1]
> > },
> >
> > "fields": {
> >"field1": integer[0-],
> > "field2":integer[0-],
> > "field3":integer[0-20]
> > }
> > }
> >
> > When i query this series :
> >
> > a) select * from test order by time desc limit 1 - it takes around 5-6
> seconds to return
> > b) select * from test where time > [some recent timestamp] - it returns
> in less than a second
> >
> > I have approximately 600k rows in my series.
> >
> > Is this some sort of a tuning problem?
> > Is it happening because of writing through the HTTP api into Influx very
> frequently (at the rate of 5-6 writes/sec) ?
> > Is this related to the fact that each item in the series is storing a
> lot of data?
> >
> > Thanks for any pointers you guys can provide.
>
> There was maybe a slight change in perf after the upgrade but still query
> time > 4s. Anything else that you think might be going wrong here?
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/8972f46c-f27e-4f2c-91fd-b7dbe558ce33%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLCpgx5L0XHj4JD%2BFjD7sAJqOgigGg6AkmQyJBNpMwB-hg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Telegraf as write buffer proxy for InfluxDB causes time unit mismatch

[Ross McDonald]

Could you provide your Telegraf configuration? Also what version of
Telegraf are you using?

On Fri, Jan 13, 2017 at 9:20 AM, Niels van Klaveren <
niels.vanklave...@gmail.com> wrote:

> When metrics are sent to Telegraf's http-input plugin and from there sent
> to InfluxDB, the nanosecond timestamps are truncated by removing the last 9
> 0's. This means all timestamps in InfluxDB end up in the far past instead
> of the correct time.
>
> The same values sent straight to InfluxDB are correct.
>
> I could not find any Telegraf configuration that could be used for this,
> and throws doubts on the feasibility of InfluxDB for our use case, where
> direct UDP output is not an option due to the source being out of our
> control, and HTTP isn't performant enough due to the high amount of fsync's.
>
> Is there anything I overlooked in fixing this ?
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/8ba704d9-64ae-46d7-be2f-7cca9fc5a35d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLCDE1SgT%3DmYgsxdeSpfw_3UUuedRBM6k7t7f6nkP4rHuA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] with Arista TAC -- needing help with telgraf and InfluxDB web toolset

[Ross McDonald]

Hi Joe,

Would you be able to open a support ticket with any questions you may have?
You can open a ticket by sending an email to supp...@influxdb.com.

Thanks,
Ross

On Fri, Feb 3, 2017 at 4:05 PM, 'Joe Dewberry' via InfluxData <
influxdb@googlegroups.com> wrote:

> Hello,
>
> Joe Dewberry with Arista TAC.  I'm trying to help a customer get his
> telegraf sorted out on an Arista switch.
>
> I have some questions and need help.
>
> Anyone available?
>
> Joe Dewberry
> Arista TAC
> 408.547.8083
>
> --
> Remember to include the version number!
> --- You received this message because you are subscribed to the Google
> Groups "InfluxData" 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/20170203220520.GA5787%40arista.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLCanFhDMnp-AWipEERtDn8VqFgskPdyaVC9LswhCcAj0Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Re: InfluxDB Raspberry Pi installation?

[Ross McDonald]

You can find the v1.2.0 Debian package compatible with ARM-based
distributions here:

https://dl.influxdata.com/influxdb/releases/influxdb_1.2.0_armhf.deb

On Wed, Feb 15, 2017 at 2:45 PM,  wrote:

>
> I want to install version 1.2. How can i do it?
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/0aa56979-6d6e-4956-997c-56ed3c35208f%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLAKxbuzu9yEc-85nmJyRJWjq6NNWD6RvrmQjJ3pRY0_VA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] Kapacitor alerts do not log the tags and fields

[Ross McDonald]

Can you share the tick script that was used to generate the alert?

On Mon, Feb 27, 2017 at 6:44 AM,  wrote:

> Hi,
>
> I am pushing alerts on kapacitor on certain logic. But the alerts that get
> logged do not have the fields displayed, instead it shows "\u003cno
> value\u003e". Could you please help me on how to resolve this?
>
>
> {"id":"Kapacitor Alert","message":"IIS Webhits are at level CRITICAL CI
> name is:\u003cno value\u003e","details":"IIS Webhits count is
> anomalous","time":"2017-02-27T11:59:49.790638274Z","
> duration":293930675,"level":"CRITICAL","data":{"
> series":[{"name":"eventflow_IIS","tags":{"eventcount":""},
> "columns":["time","stat"],"values":[["2017-02-27T11:59:49.790638274Z",3.
> 5355339059327378]]}]}}
>
> Thanks,
> Amith
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/17183e1c-8bb4-4c66-8e1e-e1453183385b%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLBYZLy2xLe9DDOUVng%2Bkr%2BawzK6%3DA316QDmPkA%3DKViVAA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [influxdb] InfluxDB keeps on logging for httpd

[Ross McDonald]

​Those are disabled by setting `log-enabled` under the `[http]` section to
false. For reference:

```
[http]
  ...
  log-enabled = false
```

And then restarting the InfluxDB service.

On Wed, Feb 15, 2017 at 3:07 PM,  wrote:

> Hello,
>
> My /var/log/syslog gets spammed with http POST messages. I have disabled
> all possible logging settings in /etc/influxdb/influxdb.conf but they just
> keep on coming.
>
> Anybody knows how to disable this kind of logging?
>
> Here is what is getting logged:
>
> Feb 15 22:04:11 Condor1 influxd[736]: [httpd] ::1 - root
> [15/Feb/2017:22:04:11 +0100] "POST /write?db=home_assistant HTTP/1.1" 204 0
> "-" "python-requests/2.13.0" 4c9a6dcd-f3c2-11e6-8904- 319301
> Feb 15 22:04:12 Condor1 influxd[736]: [httpd] ::1 - root
> [15/Feb/2017:22:04:11 +0100] "POST /write?db=home_assistant HTTP/1.1" 204 0
> "-" "python-requests/2.13.0" 4cbb6ce8-f3c2-11e6-8905- 341562
> Feb 15 22:04:12 Condor1 influxd[736]: [httpd] ::1 - root
> [15/Feb/2017:22:04:11 +0100] "POST /write?db=home_assistant HTTP/1.1" 204 0
> "-" "python-requests/2.13.0" 4cbb8739-f3c2-11e6-8906- 364649
> Feb 15 22:04:12 Condor1 influxd[736]: [httpd] ::1 - root
> [15/Feb/2017:22:04:11 +0100] "POST /write?db=home_assistant HTTP/1.1" 204 0
> "-" "python-requests/2.13.0" 4cbd5d2d-f3c2-11e6-8907- 376806
> Feb 15 22:04:12 Condor1 influxd[736]: [httpd] ::1 - root
> [15/Feb/2017:22:04:11 +0100] "POST /write?db=home_assistant HTTP/1.1" 204 0
> "-" "python-requests/2.13.0" 4cbec95a-f3c2-11e6-8908- 413035
> Feb 15 22:04:23 Condor1 influxd[736]: [httpd] ::1 - root
> [15/Feb/2017:22:04:23 +0100] "POST /write?db=home_assistant HTTP/1.1" 204 0
> "-" "python-requests/2.13.0" 53c1d896-f3c2-11e6-8909- 19403
> Feb 15 22:04:24 Condor1 influxd[736]: [httpd] ::1 - root
> [15/Feb/2017:22:04:24 +0100] "POST /write?db=home_assistant HTTP/1.1" 204 0
> "-" "python-requests/2.13.0" 54125939-f3c2-11e6-890a- 24924
> Feb 15 22:04:29 Condor1 influxd[736]: [httpd] ::1 - root
> [15/Feb/2017:22:04:29 +0100] "POST /write?db=home_assistant HTTP/1.1" 204 0
> "-" "python-requests/2.13.0" 574e2c68-f3c2-11e6-890b- 37141
> Feb 15 22:04:30 Condor1 influxd[736]: [httpd] ::1 - root
> [15/Feb/2017:22:04:30 +0100] "POST /write?db=home_assistant HTTP/1.1" 204 0
> "-" "python-requests/2.13.0" 57f2d6ae-f3c2-11e6-890c- 28901
>
>
> Thanks in advance
>
> --
> Remember to include the version number!
> ---
> You received this message because you are subscribed to the Google Groups
> "InfluxData" 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/d605b307-43cc-4d8d-8bb8-bcdb914e623b%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" 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/CAD8sRLAjGCyXE88VE5eGBm%3DhDV0s8nq2mC1s5a-O0GBbJn1JGg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.