-
The chronograf charm is permanently blocked regardless of having related it to influxdb:
```
$ juju status
Model Controller Cloud/Region Versi…
Saviq updated
6 years ago
-
leverage dashboard from Chronograf 1.x as a starting point for this template:
https://github.com/influxdata/chronograf/tree/master/canned
-
Scoped annotations were added by InfluxData to resolve the limitations seen with global annotations: https://github.com/influxdata/chronograf/pull/4119. This work then continued on that same ability…
regel updated
5 years ago
-
# Problem
Hi, I'm using the terraform modules to run a chronograf and a kapacitor server on AWS. I encountered the problem, that terraform apply would remove the target group from the auto scaling gr…
-
We are running a POC to migrate VM running influx version 1 to new and shinny influx version 2.0 on kubernetes. For that purpose, we are running default config of influx on kubernetes which is ing…
-
The loudml docker container seems to connect to influxdb using the settings of the chronograf container, not the ones configured in etc/loudml.yml, and reverting to HTTP in the process.
After getti…
-
Hi Team,
We are using kapacitor-1.5.3-1.x86_64 and chronograf-1.7.14-1.x86_64 and influxdb-1.7.6-1.x86_64.
Kapacitor and Chronograf are running on one server and InfluxDB is running on another s…
-
I was attempting to train my first model when I was surprised to discover that loudml was trying to create a new TSDB called `chronograf`:
```
requests.exceptions.SSLError: HTTPSConnectionPool(hos…
-
Hi all.
When i install Grafana + InfluxDB2 via docker all works fine, but if trying access to InfluxDB2 UI through nginx i see blank page.
**Steps to reproduce:**
docker-compose file:
```
ser…
-
I'm using a setup where Collectd is pushing metrics into InfluxDB with alerts via Kapacitor and Chronograf on top. Influxdb is version 1.2 and Kapacitor and Chronograf is version 1.3. I can successful…