ignore/delete post
On Thursday, June 16, 2016 at 9:17:56 PM UTC+3, nath...@influxdb.com wrote:
>
> 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
>
correction: I was using the default config which is HTTP subscriptions,
but now tried also the UDP and I get the same results.
any suggestions?
On Sunday, June 19, 2016 at 11:00:12 AM UTC+3, elad@adk2.com wrote:
>
> Hi,
>
> According to log I'm using UDP subscriptions (default kapacitor confi
Hi,
According to log I'm using UDP subscriptions (default kapacitor config).
Here's are the details of one of the deadman tasks:
=
ID: dead_agg_load
Error:
Template:
Type: stream
Status: disabled
Executng: false
Created: 15 Jun 16 12:53 UTC
Modified: 16 Jun 16 15:09 UTC
Last
Hi,
I'm not using UDP subscriptions, but the default config.
Here's are the details of one of the deadman tasks:
=
ID: dead_agg_load
Error:
Template:
Type: stream
Status: disabled
Executng: false
Created: 15 Jun 16 12:53 UTC
Modified: 16 Jun 16 15:09 UTC
LastEnabled: 16 Jun
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
For reference -
Here's the *DERIVATIVE* example I've configured, but still sending alerts
for existing/new points:
-
stream
|from()
.measurement('delaware:last_completed')
.where(lambda: "name" == 'exchange_hourly')
|stats(1m)
|derivative('emitted')
Hello,
We're trying to setup a *deadman* check for two measurements,
but after long hours and QA to this function - I cannot get rid of the
false-positives it sends.
Could you please take a look at this TICK and let me know what am I doing
wrong?
Here's the TICK file:
stream
|from()
Upgraded to the beta and it works great.
Would you suggest installing this beta on production? OR wait for the
stable release..
Thx,
Elad
On Thursday, June 9, 2016 at 7:33:10 PM UTC+3, nath...@influxdb.com wrote:
>
> Looks like I was wrong that error is fixed in 1.0.0-beta1 and still
> present
