[influxdb] SASL support for Memcached input plugin

Hi folks, I recently secured my Memcached instance using its built-in SASL authentication, but the Telegraf input plugin stopped working. A quick look at the plugin shows that it does not support SASL, and was not written to leverage an existing Memcached client library that does. (I see couchb

Re: [influxdb] Query using Spread

Hello Sean, Thank you for the quick response and I am sorry for the typo. I figured out the solution for that now everything fine, I am getting results what I am expected. Below are the actual records that i have in influxDB 2015-01-01T00:00:00Z 6 2015-01-01T00:15:00Z 11 2015-01

Re: [influxdb] Re: "exec" Telegraf plugin not working (for me?)

As Robert suggested, use the debugging tools in Telegraf to see what it is outputting to InfluxDB. (See -debug ) Do the Telegraf logs indicate any issues with the writes? What about the InfluxDB logs? On Thu, Jun 16, 201

Re: [influxdb] Re: "exec" Telegraf plugin not working (for me?)

Hi Sean, Sorry for my late reply!! Yes, my bad, I had commented these lines related to exec plugin out earlier! However, after ensuring that its enabled, I do not get any output for the following command: show tag keys from exec_mycollector Any suggestions? Cheers! On Thursday, June 16, 201

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

Yes, that worked! Thank you so much! On Fri, Jun 17, 2016 at 5:00 AM, Sean Beckett wrote: > Given that the python statement already includes double-quotes, I suspect > you need to escape the InfluxQL double-quotes. > > Does this work? > > data = client.query("SELECT * FROM bmspoint WHERE time >

[influxdb] Re: "exec" Telegraf plugin not working (for me?)

Try checking the output of /var/log/telegraf/telegraf.log (by default) for errors. Also try running "telegraf -test -config-directory /etc/telegraf/telegraf.d/ -input-filter=exec -debug" (default path assumed) and see if your metrics show up there. It's possible the telegraf user doesn't have p

Re: [influxdb] Re: CQs executing each minute but grouping by 24h sliding

This is also something that can be done using Kapacitor. Here is an example TICKscript to do what you want using a basic mean aggregate operation. batch |query('SELECT mean(usage_user) FROM telegraf."default".cpu') .period(1d) .every(1m) .align() |influxDBOut()

Re: [influxdb] Re: CQs executing each minute but grouping by 24h sliding

Excellent workaround! That's effectively the same as my proposed CLI solution but you've automated it in a more maintainable way. On Thu, Jun 16, 2016 at 3:23 PM, wrote: > Sean - thanks so much for this reply, super helpful! > > For the time being we've gone with an AWS Lambda that fires every m

Re: [influxdb] Multiple DBs

On Thu, Jun 16, 2016 at 2:14 PM, UW wrote: > Hello, we are collecting data from hundreds of clients and each data > collection period lasts several weeks. After three months we would like to > move older data to the archive. > > Questions: > > 1. Since there will be no queries across clients, doe

Re: [influxdb] process line monitoring in factory...

The best way to design a schema is to start with the queries it needs to support. What questions do you want to ask of your data? On Thu, Jun 16, 2016 at 12:03 PM, wrote: > I have requirement to monitor process line monitoring... > > for example > any product in a factory will go through multipl

Re: [influxdb] Re: Unable to change admin user password

As for the upgrade, check out https://docs.influxdata.com/influxdb/v0.10/administration/upgrading/ and https://vimeo.com/156754169 for some getting started context. On Thu, Jun 16, 2016 at 4:06 PM, Sean Beckett wrote: > Glad to hear it! > > I just checked a new install I had lying around and at

Re: [influxdb] Re: Unable to change admin user password

Glad to hear it! I just checked a new install I had lying around and at least in InfluxDB 0.12.2 a bare install has no users. Now I recall the deal. https://docs.influxdata.com/influxdb/v0.13/administration/authentication_and_authorization/#set-up-authentication describes it a bit, but essentially

Re: [influxdb] Re: CQs executing each minute but grouping by 24h sliding

Sean - thanks so much for this reply, super helpful! For the time being we've gone with an AWS Lambda that fires every minute and executes a query with an INTO clause, simulating a CQ. Works pretty well so far! Thanks again, -Avery On Thursday, June 16, 2016 at 4:48:23 PM UTC-4, Sean Beckett

[influxdb] Re: Unable to change admin user password

Cool, thanks for helping me out! This is the first Google Group that has actually been active! -- 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 grou

Re: [influxdb] Re: "exec" Telegraf plugin not working (for me?)

Since the measurement doesn't exist, it seems there's a problem with Telegraf executing the script. Perhaps there's an environment issue? Are you using relative paths in the scripts, for instance? On Thu, Jun 16, 2016 at 11:03 AM, Quick Query <1quickqu...@gmail.com> wrote: > Also, please let me k

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

Given that the python statement already includes double-quotes, I suspect you need to escape the InfluxQL double-quotes. Does this work? data = client.query("SELECT * FROM bmspoint WHERE time > now() - 10m AND \"name\" = 'B10_Area3for2_E_MtrEl17_PwrActv'") On Thu, Jun 16, 2016 at 10:28 AM, Ross

Re: [influxdb] Re: How to query using "SHOW TAG VALUES WITH KEY" instead of SELECT ?

I believe container_id is a field. As such, SHOW TAG VALUES will never display that column. SHOW TAG VALUES shows only the distinct tag values assigned to a given tag key. If you want field data, you must use a SELECT statement. Please review the https://docs.influxdata.com/influxdb/v0.13/query_la

Re: [influxdb] Re: Unable to change admin user password

I believe InfluxDB requires at least one user, but that behavior may have changed since 0.9.3. I would strongly recommend upgrading to at least 0.9.6. There are many bug and stability fixes in that release. Better yet migrate to InfluxDB 0.13 or 1.0b so that you can take full advantage of new feat

Re: [influxdb] How to list all container_image-s on a host ?

Are HOST_NAME1, HOST_NAME2, etc tag keys or tag values? They seem more like tag values to me. Also, please use the CLI for querying and copy/paste of results. The admin UI can have browser issues that obscure or drop query results. On Tue, Jun 14, 2016 at 2:00 PM, Quick Query <1quickqu...@gmail.c

Re: [influxdb] Anyway to write to InfluxDB via Telegraf from an external host?

I don't understand the question. The write endpoint can be accessed via HTTP from any system, including Telegraf running on another machine. Are you asking for a way to replay or fork writes from one InfluxDB to another? If so, please see https://github.com/influxdata/influxdb-relay/blob/master/RE

Re: [influxdb] Re: CQs executing each minute but grouping by 24h sliding

That is correct. RESAMPLE EVERY 1m ... GROUP BY time(24h) means every minute recalculate the data for the 24 hours that start at midnight and include today. What you want, which is to calculate the 24h query every minute for the previous 24h -- NOT the previous calendar day -- is not supported by

Re: [influxdb] standard deviation calculation using "sample" stddev rather that population

Ian, I encourage you to open an issue on the repo to request the population method. I don't think there's any specific reason one was implemented over the other. On Mon, Jun 13, 2016 at 10:59 PM, ian lutz wrote: > Hi All > (again ;)) > > Some d

Re: [influxdb] Query using Spread

Please provide some actual query input and output. Your retyped example has a typo (time before 7 p.m. and later than 11 p.m. of the same day) and I'm not sure what else might be off. On Tue, Jun 14, 2016 at 1:09 AM, wrote: > *Hello Everyone,* > * I am storing data for every 15 m

[influxdb] Multiple DBs

Hello, we are collecting data from hundreds of clients and each data collection period lasts several weeks. After three months we would like to move older data to the archive. Questions: 1. Since there will be no queries across clients, does it make sense to set up a separate DB to encapsulate

[influxdb] Re: Several doubts about AlertNodes and tickscript in kapacitor

With a subtle change (if anyone interested) Seems that "OK" state is fired only once when the alert recovers, according to documentation Events are sent to handlers if the alert is in a state other than 'OK' or > the alert just changed to the 'OK' state from a non 'OK' state (a.k.a. the > aler

[influxdb] Re: Deadman problem - ignores new points

Some basic trouble shooting steps/questions 1. How are you sending data to Kapacitor? Over UDP subcriptions? Is it possible that while InfluxDB has the data it was dropped before it made it to Kapacitor? 2. Can you share the `kapacitor show` output of your task? On Thursday, June 16, 2016 at

[influxdb] process line monitoring in factory...

I have requirement to monitor process line monitoring... for example any product in a factory will go through multiple steps in the factory. sensors will track the product in different stages. what is the best way to store the data influx. Any one in this group used InfluxDb for process line mo

[influxdb] Re: writing annotations to InfluxDB

OK. I traced this to a bit of stupidity (as I expected) on my part and how I was querying the data in Grafana. For those wondering or come upon this thread with myself, the trick was to "SELECT *" and using the column mapping in their annotations interface. The docs on annotations says "If

[influxdb] Re: Several doubts about AlertNodes and tickscript in kapacitor

Ah, yes the lambda expressions as vars was added with the 1.0 beta. Glad its working! On Thursday, June 16, 2016 at 11:29:34 AM UTC-6, Carlos Peñas wrote: > > mmm ok, got it :) > > It seems all ok except for the > > var w = lambda: "usage_idle" < 40 > var c = lambda: "usage_idle" < 20 > > > Ka

[influxdb] Re: Several doubts about AlertNodes and tickscript in kapacitor

mmm ok, got it :) It seems all ok except for the var w = lambda: "usage_idle" < 40 var c = lambda: "usage_idle" < 20 Kapacitor complains as invalid TICKscript: parser: unexpected 9 line 1 char 9 in "var w = lambda: " u". expected: "number","string","duration","identifier","TRUE","FALSE","==

[influxdb] Re: "exec" Telegraf plugin not working (for me?)

Also, please let me know if there is an alternative way to achieve this - being able to send metrics via custom scripts? Cheers! On Thursday, June 16, 2016 at 8:00:59 AM UTC-7, Quick Query wrote: > > Just to add on, as per the InfluxDB documentation >

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

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

[influxdb] Re: "exec" Telegraf plugin not working (for me?)

Just to add on, as per the InfluxDB documentation , - "The collected metrics will be stored as fields under the measurement "exec_mycollector":" But, I am not able to view this when I do a "show measurements"! Cheers! On

[influxdb] "exec" Telegraf plugin not working (for me?)

Hi Everyone. I am trying to use the exec plugin on Telegraf and the script inside just does an "echo date". The Telegraf config is as follows: # Read flattened metrics from one or more commands that output JSON to stdout [[inputs.exec]] # Shell/commands array # Full command line to exec

[influxdb] Re: kapacitor: error while evaluating WHERE expression: no field or tag exists for tcp_inerrs

Nailed it ... On Wednesday, June 15, 2016 at 9:50:18 PM UTC-4, nath...@influxdb.com wrote: > > Do you get the error for all points or just some of them? If its just some > of them that could explain it. While the field key may exist in the data > set its still possible that a single points does

Re: [influxdb] Re: Filtering away/ignoring metrics in telegraf/graphite input

On 2016-06-09 16:39, Robert wrote: There are a few filters you can apply that might be useful here: https://github.com/influxdata/telegraf/blob/master/docs/CONFIGURATION.md#measurement-filtering Ah, that was indeed exactly what I was looking for. Thankyou! Worth to note here is that filterin

[influxdb] Re: Deadman problem - ignores new points

yes? no? maybe? someone? On Wednesday, June 15, 2016 at 6:47:46 PM UTC+3, elad@adk2.com wrote: > > For reference - > Here's the *DERIVATIVE* example I've configured, but still sending alerts > for existing/new points: > - > stream >|from() >.measurement('delaware:l