Thank you very much :)
On Thursday, 23 February 2017 03:24:17 UTC+8, nath...@influxdb.com wrote:
>
> A straight delete is just fine, the process will be the same.
>
> On Monday, February 13, 2017 at 10:49:22 PM UTC-7, Subba Rao Thirumoorthy
> wrote:
>>
>> Is it advisable to disable a task first b
Thank you for your answer, I looked at the introduction of the
influx-stress(https://github.com/influxdata/influx-stress), influx-stress
is for influxdb stress testing, how to kapacitor stress test? For example,
how many task can be created by kapacitor?
thx.
在 2017年2月23日星期四 UTC+8上午3:06:23，nath
Interestingly enough, when I add the .noRecoveries() property to the alert
node I only get one DOWN alert even though there are 7 servers that are
within the alert range
On Wednesday, February 22, 2017 at 11:10:09 AM UTC-8, nath...@influxdb.com
wrote:
>
> If you want to ignore the OK alerts us
Here are the logs for the triggered alerts:
{"id":"DISK SPACE WARNING","message":"DISK SPACE WARNING
Server:mavericks.hostname.xyz Path: /home USED PERCENT:
85.16991232825805","details":"{\u0026#34;Name\u0026#34;:\u0026#34;disk\u0026#34;,\u0026#34;TaskName\u0026#34;:\u0026#34;disk_alert_warn\u002
Here are the logs from the alerts triggered:
{"id":"DISK SPACE WARNING","message":"DISK SPACE WARNING
Server:mavericks.sd.spawar.navy.mil Path: /home USED PERCENT:
85.16991232825805","details":"{\u0026#34;Name\u0026#34;:\u0026#34;disk\u0026#34;,\u0026#34;TaskName\u0026#34;:\u0026#34;disk_alert_wa
I've got some Kwh meters that will output the numbers of pulses since the last
update and the total number of pulses. I wanted to use the total number of
pulses, the idea being that if Influx, Telegraf or the network was down, the
difference can always be calculated.
To that end I created a co
kap |
'##:::'##'###':'###:'##::':'::'###::'::
kap | ##::'##'## ##::: ## ##:::'## ##:::'##...
##:. ##::... ##..::'## ##: ## ##:
kap | ##:'##'##:. ##:: ## ##::'##:. ##::
##
This behavior is not limited to just slack notifications. If email is
configured it sends out same number of notifications.
I will put the logs together and post.
On Wednesday, February 22, 2017 at 11:33:57 AM UTC-8, nath...@influxdb.com
wrote:
>
> Hmm, I see. Could you put a log node before
Hmm, I see. Could you put a log node before the alert node and share the
logs along with the logs for triggered alerts after startup?
Also this may be a bug with the most recent alerting system. Do you get the
same behavior if you configure slack directly in the TICKscript instead of
via the to
One way would be to add a window node after the derivative to buffer the
data. Something like
// Use this segment to replace the whole deadman section, this is
equivalent but will process batches of 5m at a time.
|stats(10s)
.align()
|derivative('emitted')
.un
A straight delete is just fine, the process will be the same.
On Monday, February 13, 2017 at 10:49:22 PM UTC-7, Subba Rao Thirumoorthy
wrote:
>
> Is it advisable to disable a task first before delete or straight delete
> is fine?
>
--
Remember to include the version number!
---
You received
The problem is probably the window node buffering data. The window will not
emit the current batch of data until the it has received a point the is
more than a minute past the first point in the window. Since the 5xx are
sparse points you will only get alerts after the next 5xx event happens.
Thanks so much for the reply. I do want the recovery alerts, but the
problem is that when I start kapacitor, the task sees *any* server/path in
an up status as a recovery of a *different* server/path's down status. So
if 7 server/paths are in a down status at the time of start-up I get 7 down
a
Sounds like you are looking for something like
this https://github.com/influxdata/kapacitor/issues/643. The feature hasn't
been implemented but if its what you are looking for any input on the issue
will help us prioritize and make sure the implementation meets your needs.
On Friday, February 1
If you want to ignore the OK alerts use the `.noRecoveries` property of the
alert node. This will suppress the OK alerts.
On Friday, February 17, 2017 at 3:33:16 PM UTC-7, Archie Archbold wrote:
>
> Hey all. Pretty new to TICK but I have a problem that I can't wrap my head
> around.
>
> I am mon
Performance data for each task is available via the kapacitor show command.
You can write data to Kapacitor just like InfluxDB so influx-stress and
similar tools all work.
On Tuesday, February 21, 2017 at 2:38:22 AM UTC-7, Xigang Wang wrote:
>
> How to conduct stress testing on kapacitor?
> thx
Hi Scot,
Thank you for the post! This looks like a bug. I'm able to reproduce the
issue on my instance. I've opened an issue on GitHub to alert the team to
this behavior: https://github.com/influxdata/influxdb/issues/8045. Feel
free to comment on that issue if you have any additional informatio
17 matches
Mail list logo
