I have been away from InfluxDB for a while, so I might well be wrong
thinking this has changed, but I believe it's new that I can refer to a tag
key in the query.
proc,host=ROB cpu=10,mem=20
proc,host=JOHN cpu=20,mem=10
When I do a "SELECT * FROM proc" we get the columns cpu, mem and host. Whe
I guess what u want is statechangeonly() function. Look for it on influxdb
site...several examples r present.
--
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 rec
I am having issue with telegraf 1.1/1.2. procstat plugin with telegraf running
as as root can post num_fds but as user 'telegraf' it cant? Any known reasons?
--
Remember to include the version number!
---
You received this message because you are subscribed to the Google Groups
"InfluxData"
Is Kapacitor running on the same host as the InfluxDB process? What is the
output of `kapacitor stats ingress`?
On Friday, January 27, 2017 at 11:23:04 AM UTC-7, Sebastián Peralta wrote:
>
> Hello,
> I can't integrate kacitor with influxDB. I have telegraf, influxDB and
> Grafana working OK.
>
Also, I'm not sure if it matters, but each of these separate measurements
(up to around 450 now, goal is 1000) is being written to it's own retention
policy. So, I'm not sure if that factors into increased memory usage on
influxdb.
On Monday, January 30, 2017 at 10:54:09 AM UTC-5, Jeffery K wr
There is scrolling issue on Influx DB when there is long list of DB. Its
difficult to scroll through list if it more than your screen size.Please
find the attached screen shot of screen.
--
Remember to include the version number!
---
You received this message because you are subscribed to the
There is no way to scroll data base list dropdown on top-right if list is more
than your screen size.
--
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
Ok, so changing the batch writing to happen less frequently had a large
positive effect, but it still climbs in memory usage, until it runs out
after 20-25 minutes. This is when testing against the latest, which has
"50% better write performance".
Any thoughts on other tuning parameters, to let
Hey,
I'm trying to show the errors of an application in the past hour. This is
stored in InfluxDB as an incremental counter, so say that at the start of the
hour the value is 5, at the end it's 12, and I want to show 7.
This is easily done with a query like this:
SELECT MAX("Total_#errors") -