link to Grafana

This commit is contained in:
simonox 2023-02-23 17:13:02 +01:00
parent 5a274c0b6b
commit c6d2aff289
4 changed files with 24 additions and 69 deletions

View File

@ -0,0 +1,2 @@
# Grafana

View File

@ -307,8 +307,8 @@
"retentionPolicyV18Flux": "",
"org": "Curious Community Labs",
"bucket": "test",
"x": 730,
"y": 480,
"x": 810,
"y": 500,
"wires": []
},
{
@ -326,10 +326,27 @@
"y": 480,
"wires": [
[
"7e53d20583f56487"
"7e53d20583f56487",
"499e0f3651d818db"
]
]
},
{
"id": "499e0f3651d818db",
"type": "debug",
"z": "f6f2187d.f17ca8",
"name": "debug 1",
"active": true,
"tosidebar": true,
"console": false,
"tostatus": false,
"complete": "false",
"statusVal": "",
"statusType": "auto",
"x": 800,
"y": 420,
"wires": []
},
{
"id": "e0977f2582bfaaa6",
"type": "mqtt in",

View File

@ -88,6 +88,8 @@ Then the measurements should be visible in [Influx Data Explorer](http://localho
![Influx Data Explorer](./docs/images/influx-data-explorer.png)
As the data is now stored in Influx, [let's create a dashboard in Grafana](../dashboard/README.md).
# Links
* [IoT Made Easy with Node-RED and InfluxDB](https://www.influxdata.com/blog/iot-easy-node-red-influxdb/)

View File

@ -206,72 +206,6 @@
"url": "http://influxdb:8086",
"rejectUnauthorized": true
},
{
"id": "3cc11d24.ff01a2",
"type": "comment",
"z": "f6f2187d.f17ca8",
"name": "WARNING: please check you have started this container with a volume that is mounted to /data\\n otherwise any flow changes are lost when you redeploy or upgrade the container\\n (e.g. upgrade to a more recent node-red docker image).\\n If you are using named volumes you can ignore this warning.\\n Double click or see info side panel to learn how to start Node-RED in Docker to save your work",
"info": "\nTo start docker with a bind mount volume (-v option), for example:\n\n```\ndocker run -it -p 1880:1880 -v /home/user/node_red_data:/data --name mynodered nodered/node-red\n```\n\nwhere `/home/user/node_red_data` is a directory on your host machine where you want to store your flows.\n\nIf you do not do this then you can experiment and redploy flows, but if you restart or upgrade the container the flows will be disconnected and lost. \n\nThey will still exist in a hidden data volume, which can be recovered using standard docker techniques, but that is much more complex than just starting with a named volume as described above.",
"x": 330,
"y": 100,
"wires": []
},
{
"id": "39aa2ca9.804da4",
"type": "debug",
"z": "f6f2187d.f17ca8",
"name": "",
"active": true,
"tosidebar": true,
"console": false,
"tostatus": false,
"complete": "payload",
"targetType": "msg",
"statusVal": "",
"statusType": "auto",
"x": 670,
"y": 360,
"wires": []
},
{
"id": "262a3923.e7b216",
"type": "influxdb in",
"z": "f6f2187d.f17ca8",
"influxdb": "eeb221fb.ab27f",
"name": "",
"query": "SELECT * from test",
"rawOutput": false,
"precision": "",
"retentionPolicy": "",
"org": "my-org",
"x": 450,
"y": 360,
"wires": [
[
"39aa2ca9.804da4"
]
]
},
{
"id": "803d82f.ff80f8",
"type": "inject",
"z": "f6f2187d.f17ca8",
"name": "",
"repeat": "",
"crontab": "",
"once": false,
"onceDelay": 0.1,
"topic": "",
"payload": "",
"payloadType": "date",
"x": 240,
"y": 360,
"wires": [
[
"262a3923.e7b216"
]
]
},
{
"id": "00a750cdfb54579e",
"type": "mqtt in",