The Grafana cloud does not require any kind of installation. The Grafana Cloud can be setup at this link Grafana Cloud
Simply put when you register and setup your account they will create a instance for you. Then you just go to that URL and log in and it will take you into your instance of grafana. I just logged into my account i setup for testing a while back.
Once you got that, all you need to do is setup the database connector to your InfluxDB Cloud account just as you would with the OSS version of Grafana. Then import the dashboards you want.
Click on the INfluxDB item to setup the database connection to your INfluxDB Cloud Account.
You should have all of the needed info saved in the tip sheet i created in the first post if you have been capturing it..
Give the datasource a meaningful Name, and specify the Flux Query language. Then scroll down and fill in the remaining influxdb access info. Put in the ORG you specified when setting up your InfluxDB Cloud account. Then your API Token you collected for the account and then lastly the Bucket as that is where the data is being put. These should also match what you are already using for INfluxDB Logger. Then click on Save & Test and you should get a successful message.
Lastly import the dashboard following the directions provided early in this thread.
One thing to understand is the cloud instance does have some built in dashboards for other things related to the cloud instance so you may not want to delete those incase you ever want to see stats on your cloud instance.
The info in your last post is related to INfluxdb 1.x compatibility and using the legacy method for querying. Most likely not needed unless you already have dashboards that use that method. I you are just going to use the dashboards @jtp10181 has in his thread linked in post 4 those all have Flux versions, so not needed. The post i made describes creating the Grafana Datasource only needs the API Token you already have.
Well , to be honest I'm just going down the instructions in order. I currently have nothing. Im just starting to look at this to see what all I can do with it. I still need to play with it to figure out what all I can do. Off the top of my head I'm thinking the "normal" stuff. CPU load, memory etc.
Is there something special I need to do for multiple hubs? I set two Additional hubs up with the same settings I used on the initial hub, and they don’t seem to be found.
That looks like you have something sending bad data to influxDB Logger.
Go into the InfluxDB Logger app and set it to use a batch size limit of 1.
That will make it process one at a time. I believe it also drops the records if it is bad data. that will get you going. Once past that data I would set it to 250 so you can churn through your backlog.
That didn't seem to drop the back log, but it but does seem to be going down. I even changed the backlog to one and it steadily reduced the backlog events. However, SO FAR those two hubs have not appeared. For poops ad giggles, I went in an made sure each was configured EXACTLY as the one that is reporting is configured. Aall three are now identical (well, except for the device names)
Regarding the backlog / bad data issue, you want to set both the "Batch size limit" and the "Backlog size limit" to 1 in order to clear the bad data. Once the queue is cleared, you can ramp the values back up.
You should be able to identify the bad record(s) by looking at the errors in the log (look for "Failed record was: XXXXX"). When you identify the bad record(s), please post the data so that we can figure out what went wrong.
Hub 1 (the one that is working) Wilson_617:Devices ; (Hub info Device name Hub Information V3_Devices)
Hub 2 (additional hub) Wilson_617:Server ;(Hub Info device name Hub Information V3 _ Server
Hub3 (additional hub) Wilson_617.3: Cloud ;(hub info Device name Hub Information V3_Cloud)
