The actual comparison is <= which is why you received the alert. But if
your tolerances are tight enough that <= matters over < then you are
probably too tight on your tolerances.
I would first recommend that you tweak the sigmas value, may increase it to
3.5 or 4. To iterate quickly on for
On Thursday, 27 October 2016 21:46:08 UTC+5:30, nath...@influxdb.com wrote:
> Clarification from Amith:
>
>
>
>
>
>
> Hi Nathaniel,
>
>
> Thanks a lot for your quick reply, what is confusing for me here is how
> morgoth calculated anomalyScore field whose value has turned out to be
>
I am not sure, but that's a wonderful reason to open a feature request on
the repo: https://github.com/influxdata/telegraf/issues/new
On Tue, Nov 8, 2016 at 11:36 AM, Frederic Pellin
wrote:
> OK i understand, maybe it will be interesting to report number of core to
>
OK i understand, maybe it will be interesting to report number of core to
allow conversion on graphes no ? is it schedule on next version ?
Le mar. 8 nov. 2016 à 17:30, Sean Beckett a écrit :
> Most built-in CPU tools report CPU usage per core, so an 8 core machine
> that is
I wrote the identical point you sent and it queries properly for me:
> select elapsedTime, rate, totalSizeInBytes from tasks
name: tasks
---
time elapsedTime rate totalSizeInBytes
1478630013784144006 164514 0.006097560975609756 3380749
I'm using the CLI to submit it via HTTP. Maybe
If you are writing points across a wide time range, change the default
shard duration:
http://docs.influxdata.com/influxdb/v1.0/concepts/schema_and_data_layout/#shard-group-duration-recommendations
Are you overwriting points?
On Tue, Nov 8, 2016 at 12:24 PM, wrote:
On Tuesday, November 8, 2016 at 1:42:55 PM UTC-6, Sean Beckett wrote:
> I wrote the identical point you sent and it queries properly for me:
>
>
>
> > select elapsedTime, rate, totalSizeInBytes from tasks
> name: tasks
> ---
> time elapsedTime rate
Hi,
I have an huge amount of data collected by ORCA and I'm looking to import them
into InfluxDB.
Is someone had already done this?
Any hints will be welcomed.
Thanks
Nicolas
--
Remember to include the version number!
---
You received this message because you are subscribed to the Google
Hi,
On my linux server with 12core, when a process consume one entire cpu,
procstat report 100% instead of reporting 100/12 => 0.8%.
Is there a way to configure procstat to consider number of core when
reporting cpu_usage ?
Thanks.
Fred
--
Remember to include the version number!
---
You