Forskjell mellom versjoner av «Prosjekt Velkomstskjerm»

Fra Bitraf
Hopp til navigering Hopp til søk
(→‎2023: restarted telegraf)
(→‎2024: mada a holder and hung up the infoskjerm pi a bit better)
 
(9 mellomliggende revisjoner av samme bruker vises ikke)
Linje 177: Linje 177:
  
 
== Vedlikehold ==
 
== Vedlikehold ==
 +
 +
=== 2024 ===
 +
; 2024-10-17 : also 3D printed a holder (of sorts) for the infoskjerm pi, so it doesn't hang by the cables anymore. [[Bruker:Tingo|Tingo]] ([[Brukerdiskusjon:Tingo|diskusjon]]) 17. okt. 2024 kl. 19:53 (CEST)
 +
: the <code>infoskjerm.local</code> Pi had fallen down (literally) so that neither the HDMI / DVI cable nor the power cable was connected. Connected everything, and the pi booted right up and shows the grafana URL again. [[Bruker:Tingo|Tingo]] ([[Brukerdiskusjon:Tingo|diskusjon]]) 17. okt. 2024 kl. 18:23 (CEST)
  
 
=== 2023 ===
 
=== 2023 ===
 +
; 2023-03-25 : no data in grafana, so I restarted telegraf via <code>sudo systemctl restart telegraf</code>. [[Bruker:Tingo|Tingo]] ([[Brukerdiskusjon:Tingo|diskusjon]]) 25. mar. 2023 kl. 18:51 (CET)
 +
 +
; 2023-03-12 : set up a new microSD card for the infoskjerm.local pi, based on RaspiOS Lite, using the Raspberry Pi Imager to configure hostname, ssh access and user. Then I used ansible like so <code>ansible-playbook infoscreen.yml -l infoskjerm --user pi -k</code> (the --user and -k are only needed the first time, after that you can use <code>ansible-playbook infoscreen.yml -l infoskjerm</code>). [[Bruker:Tingo|Tingo]] ([[Brukerdiskusjon:Tingo|diskusjon]]) 12. mar. 2023 kl. 15:57 (CET)
 +
; 2023-03-12 : no data in grafana, so I restarted telegraf via <code>sudo systemctl restart telegraf</code>. [[Bruker:Tingo|Tingo]] ([[Brukerdiskusjon:Tingo|diskusjon]]) 12. mar. 2023 kl. 15:39 (CET)
 +
 +
; 2023-02-23 : restarted the sensor in the 3D printer-room andf now I get data into grafana. [[Bruker:Tingo|Tingo]] ([[Brukerdiskusjon:Tingo|diskusjon]]) 23. feb. 2023 kl. 22:37 (CET)
 +
 +
; 2023-02-23 : checked data on mqtt-server, it has and "spits out" data. But there is no data in Influxdb
 +
<pre>
 +
tingo@iot2:~$ influx
 +
Connected to http://localhost:8086 version 1.5.3
 +
InfluxDB shell version: 1.5.3
 +
> use  mqtt_bitraf ;
 +
Using database mqtt_bitraf
 +
> select * from mqtt_consumer where topic="/public/smutcave/humidity"
 +
> select * from mqtt_consumer where topic="/public/smutcave/temperature"
 +
> select * from mqtt_consumer where topic=bitraf/currentsensor/shopbot
 +
> select * from mqtt_consumer where topic=bitraf/humidity/1
 +
> select * from mqtt_consumer where topic=bitraf/humidity/2/value
 +
> select * from mqtt_consumer where topic=bitraf/temperature/1
 +
> select * from mqtt_consumer where topic=bitraf/temperature/2/value
 +
> select * from mqtt_consumer where topic=bitraf/temperature/3/value
 +
</pre>
 +
 
; 2023-02-23 : restarted telegraf via <code>sudo systemctl restart telegraf</code>. [[Bruker:Tingo|Tingo]] ([[Brukerdiskusjon:Tingo|diskusjon]]) 23. feb. 2023 kl. 20:14 (CET)
 
; 2023-02-23 : restarted telegraf via <code>sudo systemctl restart telegraf</code>. [[Bruker:Tingo|Tingo]] ([[Brukerdiskusjon:Tingo|diskusjon]]) 23. feb. 2023 kl. 20:14 (CET)
  
 
=== 2022 ===
 
=== 2022 ===
−
; 2022-11-27 : configured up a ndew microSD card for the infoskjerm.local pi, based on RaspiOS Lite, using the Raspberry Pi Imager to configure hostname, ssh access and user. Then I used ansible like so
+
; 2022-11-27 : configured up a new microSD card for the infoskjerm.local pi, based on RaspiOS Lite, using the Raspberry Pi Imager to configure hostname, ssh access and user. Then I used ansible like so
 
<code>ansible-playbook infoscreen.yml -l infoskjerm --user pi -k</code> (the --user and -k are only needed the first time, after that you can use <code>ansible-playbook infoscreen.yml -l infoskjerm</code>).
 
<code>ansible-playbook infoscreen.yml -l infoskjerm --user pi -k</code> (the --user and -k are only needed the first time, after that you can use <code>ansible-playbook infoscreen.yml -l infoskjerm</code>).
 
If mdns is giving you trouble, just localy edit the inventory file, and set the ip address instead of the hostname. '''Note''': to be able to use (Bitraf's) ansible setup, you need to be a superuser in Bitraf's ansible setup. [[Bruker:Tingo|Tingo]] ([[Brukerdiskusjon:Tingo|diskusjon]]) 27. nov. 2022 kl. 19:00 (CET)
 
If mdns is giving you trouble, just localy edit the inventory file, and set the ip address instead of the hostname. '''Note''': to be able to use (Bitraf's) ansible setup, you need to be a superuser in Bitraf's ansible setup. [[Bruker:Tingo|Tingo]] ([[Brukerdiskusjon:Tingo|diskusjon]]) 27. nov. 2022 kl. 19:00 (CET)

Nåværende revisjon fra 17. okt. 2024 kl. 18:54

bilde av skjerm

Skjermen i hjørnet skal vise en velkomstmelding med kul grafikk når folk logger in med checkin.

Infoskjerm-grafana.jpg

Infoskjermen er nå operativ. Den kjører en webside som viser en playlist fra lokal grafana-server. For å redigere grafana-sidene logger du inn på http://iot2.bitraf.no:3000


Teknisk info

Løsningen består av to deler, En Raspberry Pi koblet til TV'en som viser en webside, og en server som står for alt det andre.

Raspberry Pi

navn: infoskjerm.local

Update: the image is a "normal" RaspiOS lite image, and then the ansible playbook infoscreen.yml is used to configure it.

This Pi runs Raspbian, autologins as the pi user (no, not with the default password) and starts the chromium browser pointing to the server. It (ab)uses LXDE's autostart script for this, like so 

pi@infoskjerm:~ $ more /home/pi/.config/lxsession/LXDE-pi/autostart
@lxpanel --profile LXDE-pi
@pcmanfm --desktop --profile LXDE-pi
#@xscreensaver -no-splash
@point-rpi

@chromium-browser --no-startup-window --kiosk

@/usr/bin/chromium-browser --start-maximized --kiosk --disable-infobars --noerrordialogs --app=http://iot2.bitraf.no:3000/playlists/play/1?kiosk


@unclutter
@xset s off
@xset s noblank
@xset -dpms

xscreensaver is commented out, the command unclutter turns off the mouse, then xset turns off screen saver, blanking and DPMS just in case the screen supports that. Not sure why there is two lines to start chromium-browser.

point-rpi 
Locate the mouse pointer over the menu button

Server

navn: iot2.bitraf.no

Serveren kjører Grafana[1] (grafana-server), samt følgende komponenter fra TICK stack

  • Telegraf[2] - agent, datainnsamling
  • Influxdb[3] - database for tids-serie data
  • Kapacitor[4] - prosessering av data

Tjenestene har følgende navn

  • grafana-server.service
  • influxdb.service
  • kapacitor.service
  • telegraf.service

Chronograf[5] er ikke i bruk, siden vi benytter Grafana.

Databaser

Følgende databaser er definert i influxdb 

> show databases
name: databases
name
----
_internal
telegraf
mqtt_bitraf
bitraf-maskiner

I mqtt_bitraf er følgende serier definert 

> show series on mqtt_bitraf
key
---
bitraf_bool,host=iot2,topic=/bitraf/door/2floor/isopen
bitraf_bool,host=iot2,topic=/bitraf/door/3office/isopen
bitraf_bool,host=iot2,topic=/bitraf/door/3workshop/isopen
bitraf_bool,host=iot2,topic=/bitraf/door/4floor/isopen
bitraf_bool,host=iot2,topic=/bitraf/door/frontdoor/isopen
bitraf_int,host=iot2,topic=/bitraf/door/frontdoor/open
bitraf_int,host=iot2,topic=/public/chime/uptime
bitraf_string,host=iot2,topic=public/infoscreen/wtf
mqtt_consumer,host=iot2,topic=/public/smutcave/humidity
mqtt_consumer,host=iot2,topic=/public/smutcave/temperature
mqtt_consumer,host=iot2,topic=bitraf/currentsensor/shopbot
mqtt_consumer,host=iot2,topic=bitraf/humidity/1
mqtt_consumer,host=iot2,topic=bitraf/humidity/2/value
mqtt_consumer,host=iot2,topic=bitraf/temperature/1
mqtt_consumer,host=iot2,topic=bitraf/temperature/2/value
mqtt_consumer,host=iot2,topic=bitraf/temperature/3/value
ping,host=iot2,url=10.13.37.248
ping,host=iot2,url=10.13.37.47
ping,host=iot2,url=boxy3.local
ping,host=iot2,url=boxy4.local
ping,host=iot2,url=http://boxy3.local
ping,host=iot2,url=http://boxy4.local

I bitraf-maskiner er følgende serier definert 

> show series on "bitraf-maskiner"
key
---
nvidia_smi,compute_mode=Default,host=Multimedia-maskin,index=0,name=GeForce\ GTX\ 570,pstate=P0,uuid=GPU-5566aa51-b932-0d56-cc06-b6ae94dc6e5f
nvidia_smi,compute_mode=Default,host=Multimedia-maskin,index=0,name=GeForce\ GTX\ 570,pstate=P12,uuid=GPU-5566aa51-b932-0d56-cc06-b6ae94dc6e5f
nvidia_smi,compute_mode=Default,host=Multimedia-maskin,index=0,name=GeForce\ GTX\ 570,pstate=P8,uuid=GPU-5566aa51-b932-0d56-cc06-b6ae94dc6e5f
win_cpu,host=Multimedia-maskin,instance=0,objectname=Processor
win_cpu,host=Multimedia-maskin,instance=1,objectname=Processor
win_cpu,host=Multimedia-maskin,instance=2,objectname=Processor
win_cpu,host=Multimedia-maskin,instance=3,objectname=Processor
win_cpu,host=Multimedia-maskin,instance=4,objectname=Processor
win_cpu,host=Multimedia-maskin,instance=5,objectname=Processor
win_cpu,host=Multimedia-maskin,instance=_Total,objectname=Processor
win_disk,host=Multimedia-maskin,instance=C:,objectname=LogicalDisk
win_disk,host=Multimedia-maskin,instance=D:,objectname=LogicalDisk
win_disk,host=Multimedia-maskin,instance=E:,objectname=LogicalDisk
win_diskio,host=Multimedia-maskin,instance=0\ C:,objectname=PhysicalDisk
win_diskio,host=Multimedia-maskin,instance=1\ D:,objectname=PhysicalDisk
win_diskio,host=Multimedia-maskin,instance=2\ E:,objectname=PhysicalDisk
win_mem,host=Multimedia-maskin,objectname=Memory
win_net,host=Multimedia-maskin,instance=Realtek\ PCIe\ GBE\ Family\ Controller,objectname=Network\ Interface
win_perf_counters,host=Multimedia-maskin,instance=Realtek\ PCIe\ GBE\ Family\ Controller,objectname=Network\ Interface
win_swap,host=Multimedia-maskin,instance=_Total,objectname=Paging\ File
win_system,host=Multimedia-maskin,objectname=System

Telegraf

Telegraf er konfigurert (via /etc/telegraf/telegraf.conf) til å lese følgende topics fra Bitraf's mqtt server:

format: value, type: float 

   topics = [
     "bitraf/temperature/1",
     "bitraf/humidity/1",
     "bitraf/temperature/2/value",
     "bitraf/humidity/2/value",
     "bitraf/temperature/3/value",
     "bitraf/currentsensor/shopbot",
     "/public/smutcave/temperature",
     "/public/smutcave/humidity",
     "public/printerroom/tvoc",
     "public/printerroom/eco2",
     "public/printerroom/humidity",
     "public/printerroom/temperature",
     "public/lab/pm10",
     "public/lab/pm25",
     "public/laser/eco2",
     "public/laser/humidity",
     "public/laser/pm10",
     "public/laser/pm25",
     "public/laser/temperature",
     "public/laser/tvoc",
   ]

format: value, type: integer 

        "/bitraf/door/frontdoor/open",
	"/public/chime/uptime",

format: value, type: boolean 

        "/bitraf/door/frontdoor/isopen",
        "/bitraf/door/2floor/isopen",
        "/bitraf/door/3workshop/isopen",
        "/bitraf/door/3office/isopen",
        "/bitraf/door/4floor/isopen",

format: json 

		"bitraf/octoprint/blackbot/progress/printing",

format: value, type: string 

		"public/infoscreen/wtf",

den må oppdateres hvis flere ting skal inn. Ser ikke ut som om Telegraf støtter bruk av wildcards i mqtt topics.

Vedlikehold

2024

2024-10-17 
also 3D printed a holder (of sorts) for the infoskjerm pi, so it doesn't hang by the cables anymore. Tingo (diskusjon) 17. okt. 2024 kl. 19:53 (CEST)
the infoskjerm.local Pi had fallen down (literally) so that neither the HDMI / DVI cable nor the power cable was connected. Connected everything, and the pi booted right up and shows the grafana URL again. Tingo (diskusjon) 17. okt. 2024 kl. 18:23 (CEST)

2023

2023-03-25 
no data in grafana, so I restarted telegraf via sudo systemctl restart telegraf. Tingo (diskusjon) 25. mar. 2023 kl. 18:51 (CET)
2023-03-12 
set up a new microSD card for the infoskjerm.local pi, based on RaspiOS Lite, using the Raspberry Pi Imager to configure hostname, ssh access and user. Then I used ansible like so ansible-playbook infoscreen.yml -l infoskjerm --user pi -k (the --user and -k are only needed the first time, after that you can use ansible-playbook infoscreen.yml -l infoskjerm). Tingo (diskusjon) 12. mar. 2023 kl. 15:57 (CET)
2023-03-12 
no data in grafana, so I restarted telegraf via sudo systemctl restart telegraf. Tingo (diskusjon) 12. mar. 2023 kl. 15:39 (CET)
2023-02-23 
restarted the sensor in the 3D printer-room andf now I get data into grafana. Tingo (diskusjon) 23. feb. 2023 kl. 22:37 (CET)
2023-02-23 
checked data on mqtt-server, it has and "spits out" data. But there is no data in Influxdb
tingo@iot2:~$ influx
Connected to http://localhost:8086 version 1.5.3
InfluxDB shell version: 1.5.3
> use  mqtt_bitraf ;
Using database mqtt_bitraf
> select * from mqtt_consumer where topic="/public/smutcave/humidity"
> select * from mqtt_consumer where topic="/public/smutcave/temperature"
> select * from mqtt_consumer where topic=bitraf/currentsensor/shopbot
> select * from mqtt_consumer where topic=bitraf/humidity/1
> select * from mqtt_consumer where topic=bitraf/humidity/2/value
> select * from mqtt_consumer where topic=bitraf/temperature/1
> select * from mqtt_consumer where topic=bitraf/temperature/2/value
> select * from mqtt_consumer where topic=bitraf/temperature/3/value
2023-02-23 
restarted telegraf via sudo systemctl restart telegraf. Tingo (diskusjon) 23. feb. 2023 kl. 20:14 (CET)

2022

2022-11-27 
configured up a new microSD card for the infoskjerm.local pi, based on RaspiOS Lite, using the Raspberry Pi Imager to configure hostname, ssh access and user. Then I used ansible like so

ansible-playbook infoscreen.yml -l infoskjerm --user pi -k (the --user and -k are only needed the first time, after that you can use ansible-playbook infoscreen.yml -l infoskjerm). If mdns is giving you trouble, just localy edit the inventory file, and set the ip address instead of the hostname. Note: to be able to use (Bitraf's) ansible setup, you need to be a superuser in Bitraf's ansible setup. Tingo (diskusjon) 27. nov. 2022 kl. 19:00 (CET)

2022-11-27 
no data in grafana, so I restarted telegraf via sudo systemctl restart telegraf. Tingo (diskusjon) 27. nov. 2022 kl. 16:36 (CET)
2022-10-13 
meldt om at SD-kortet på pi'en (infoskjerme.local) har dødd / er blitt utslitt. Meldt av royk. Tingo (diskusjon) 27. nov. 2022 kl. 16:32 (CET)
2022-02-14 
grafana - downgrade plugin grafana-clock-panel to version 0.1.0, because the new vwersion fails.
tingo@iot2:~$ sudo grafana-cli plugins install grafana-clock-panel 0.1.0
installing grafana-clock-panel @ 0.1.0
from url: https://grafana.com/api/plugins/grafana-clock-panel/versions/0.1.0/download
into: /var/lib/grafana/plugins

Failed downloading. Will retry once.
Failed downloading. Will retry once.

Error: ✗ Corrupt http response from source. Please try again.


NAME:
   Grafana cli plugins install - install <plugin id> <plugin version (optional)>

USAGE:
   Grafana cli plugins install [arguments...]
tingo@iot2:~$ sudo grafana-cli plugins install grafana-clock-panel 0.1.0
installing grafana-clock-panel @ 0.1.0
from url: https://grafana.com/api/plugins/grafana-clock-panel/versions/0.1.0/download
into: /var/lib/grafana/plugins

Failed downloading. Will retry once.
✔ Installed grafana-clock-panel successfully 

Restart grafana after installing plugins . <service grafana-server restart>

and restart grafana via $ sudo systemctl restart grafana-server. That's all. Tingo (diskusjon) 14. feb. 2022 kl. 19:53 (CET)

2022-02-13 
grafana - install a json plugin
tingo@iot2:~$ sudo grafana-cli plugins install grafana-simple-json-datasource
installing grafana-simple-json-datasource @ 1.4.2
from url: https://grafana.com/api/plugins/grafana-simple-json-datasource/versions/1.4.2/download
into: /var/lib/grafana/plugins

✔ Installed grafana-simple-json-datasource successfully 

Restart grafana after installing plugins . <service grafana-server restart>

and restart grafana via $ sudo systemctl restart grafana-server. Tingo (diskusjon) 13. feb. 2022 kl. 15:34 (CET)

2022-02-13 
restarted grafana after updating plugins via $ sudo systemctl restart grafana-server. Tingo (diskusjon) 13. feb. 2022 kl. 14:51 (CET)
2022-02-13 
update a few grafana plugins
tingo@iot2:~$ sudo grafana-cli plugins update grafana-clock-panel
Removing plugin: grafana-clock-panel
installing grafana-clock-panel @ 1.1.2
from url: https://grafana.com/api/plugins/grafana-clock-panel/versions/1.1.2/download
into: /var/lib/grafana/plugins

✔ Installed grafana-clock-panel successfully 

Restart grafana after installing plugins . <service grafana-server restart>

tingo@iot2:~$ sudo grafana-cli plugins update grafana-piechart-panel
Removing plugin: grafana-piechart-panel
installing grafana-piechart-panel @ 1.6.2
from url: https://grafana.com/api/plugins/grafana-piechart-panel/versions/1.6.2/download
into: /var/lib/grafana/plugins

✔ Installed grafana-piechart-panel successfully 

Restart grafana after installing plugins . <service grafana-server restart>

tingo@iot2:~$ sudo grafana-cli plugins update mtanda-google-calendar-datasource
Removing plugin: mtanda-google-calendar-datasource
installing mtanda-google-calendar-datasource @ 1.0.5
from url: https://grafana.com/api/plugins/mtanda-google-calendar-datasource/versions/1.0.5/download
into: /var/lib/grafana/plugins

✔ Installed mtanda-google-calendar-datasource successfully 

Restart grafana after installing plugins . <service grafana-server restart>

Tingo (diskusjon) 13. feb. 2022 kl. 14:48 (CET)

one plugin is stubborn 

tingo@iot2:~$ sudo grafana-cli plugins update jdbranham-diagram-panel
Removing plugin: jdbranham-diagram-panel
installing jdbranham-diagram-panel @ 1.6.2
from url: https://grafana.com/api/plugins/jdbranham-diagram-panel/versions/1.6.2/download
into: /var/lib/grafana/plugins

Failed downloading. Will retry once.
Failed downloading. Will retry once.

Error: ✗ Corrupt http response from source. Please try again.


NAME:
   Grafana cli plugins update - update <plugin id>

USAGE:
   Grafana cli plugins update [arguments...]

tingo@iot2:~$ sudo grafana-cli plugins update jdbranham-diagram-panel

Error: ✗ Could not find dist/plugin.json or plugin.json on  jdbranham-diagram-panel in /var/lib/grafana/plugins

NAME:
   Grafana cli plugins update - update <plugin id>

USAGE:
   Grafana cli plugins update [arguments...]

tingo@iot2:~$ sudo grafana-cli plugins install jdbranham-diagram-panel
installing jdbranham-diagram-panel @ 1.6.2
from url: https://grafana.com/api/plugins/jdbranham-diagram-panel/versions/1.6.2/download
into: /var/lib/grafana/plugins

Failed downloading. Will retry once.
Failed downloading. Will retry once.
✔ Installed jdbranham-diagram-panel successfully 

Restart grafana after installing plugins . <service grafana-server restart>

Finally. Tingo (diskusjon) 13. feb. 2022 kl. 14:48 (CET)

2022-02-13 
checking what grafana plugins are installed first
tingo@iot2:~$ sudo grafana-cli plugins ls
installed plugins:
briangann-gauge-panel @ 0.0.6 
grafana-clock-panel @ 0.1.0 
grafana-piechart-panel @ 1.3.3 
jdbranham-diagram-panel @ 1.4.4 
mtanda-google-calendar-datasource @ 1.0.4 

Restart grafana after installing plugins . <service grafana-server restart>

Tingo (diskusjon) 13. feb. 2022 kl. 14:30 (CET)

checking available plugins
tingo@iot2:~$ sudo grafana-cli plugins list-remote
id: abhisant-druid-datasource version: 0.0.6
id: aceiot-svg-panel version: 0.0.8
id: ae3e-plotly-panel version: 0.2.1
id: agenty-flowcharting-panel version: 0.9.1
id: aidanmountford-html-panel version: 0.0.2
id: akumuli-datasource version: 1.3.12
id: alexanderzobnin-zabbix-app version: 4.0.1
id: alexandra-trackmap-panel version: 1.2.6
id: andig-darksky-datasource version: 1.0.2
id: aquaqanalytics-kdbadaptor-datasource version: 1.0.2
id: ayoungprogrammer-finance-datasource version: 1.0.1
id: belugacdn-app version: 1.2.1
id: bessler-pictureit-panel version: 1.0.1
id: blackmirror1-singlestat-math-panel version: 1.1.8
id: blackmirror1-statusbygroup-panel version: 1.1.2
id: bosun-app version: 0.0.29
id: briangann-datatable-panel version: 1.0.2
id: briangann-gauge-panel version: 0.0.6
id: camptocamp-prometheus-alertmanager-datasource version: 0.0.8
id: citilogics-geoloop-panel version: 1.1.2
id: clarity89-finnhub-datasource version: 0.1.0
id: cloudflare-app version: 0.2.2
id: cloudspout-button-panel version: 7.0.4
id: cognitedata-datasource version: 2.1.0
id: corpglory-progresslist-panel version: 1.0.6
id: dalmatinerdb-datasource version: 1.0.5
id: dalvany-image-panel version: 2.2.0
id: ddurieux-glpi-app version: 1.3.1
id: devicehive-devicehive-datasource version: 2.0.2
id: devopsprodigy-kubegraf-app version: 1.4.2
id: digiapulssi-breadcrumb-panel version: 1.1.7
id: digiapulssi-organisations-panel version: 1.3.1
id: digrich-bubblechart-panel version: 1.2.0
id: dlopes7-appdynamics-datasource version: 1.4.3
id: doitintl-bigquery-datasource version: 1.0.8
id: factry-untimely-panel version: 0.1.1
id: farski-blendstat-panel version: 1.0.3
id: fastweb-openfalcon-datasource version: 1.0.1
id: fatcloud-windrose-panel version: 0.7.1
id: fetzerch-sunandmoon-datasource version: 0.1.6
id: fifemon-graphql-datasource version: 1.1.3
id: flant-statusmap-panel version: 0.3.4
id: foursquare-clouderamanager-datasource version: 0.9.3
id: fzakaria-simple-annotations-datasource version: 1.0.1
id: gnocchixyz-gnocchi-datasource version: 1.7.1
id: goshposh-metaqueries-datasource version: 0.0.5
id: gowee-traceroutemap-panel version: 0.2.3
id: grafana-azure-data-explorer-datasource version: 2.0.5
id: grafana-azure-monitor-datasource version: 0.3.1
id: grafana-clock-panel version: 1.1.2
id: grafana-datadog-datasource version: 1.4.8
id: grafana-discourse-datasource version: 1.0.0
id: grafana-dynatrace-datasource version: 2.0.2
id: grafana-enterprise-logs-app version: 2.3.0
id: grafana-enterprise-traces-app version: 1.0.0
id: grafana-googlesheets-datasource version: 1.0.1
id: grafana-iot-sitewise-datasource version: 0.0.1
id: grafana-kairosdb-datasource version: 3.0.2
id: grafana-metrics-enterprise-app version: 3.3.0
id: grafana-newrelic-datasource version: 1.4.0
id: grafana-oracle-datasource version: 1.1.6
id: grafana-piechart-panel version: 1.6.2
id: grafana-polystat-panel version: 1.2.2
id: grafana-servicenow-datasource version: 1.1.1
id: grafana-simple-json-datasource version: 1.4.2
id: grafana-splunk-datasource version: 1.4.1
id: grafana-strava-datasource version: 1.3.0
id: grafana-synthetic-monitoring-app version: 0.8.13
id: grafana-worldmap-panel version: 0.3.3
id: gretamosa-topology-panel version: 1.0.1
id: gridprotectionalliance-openhistorian-datasource version: 1.0.3
id: gridprotectionalliance-osisoftpi-datasource version: 1.1.1
id: hadesarchitect-cassandra-datasource version: 1.1.4
id: hawkular-datasource version: 1.1.2
id: humio-datasource version: 3.1.1
id: ibm-apm-datasource version: 0.9.1
id: innius-video-panel version: 1.0.1
id: instana-datasource version: 3.1.0
id: jasonlashua-prtg-datasource version: 4.0.4
id: jdbranham-diagram-panel version: 1.6.2
id: jeanbaptistewatenberg-percent-panel version: 1.0.6
id: larona-epict-panel version: 1.2.2
id: linksmart-hds-datasource version: 1.0.2
id: linksmart-sensorthings-datasource version: 1.3.1
id: macropower-analytics-panel version: 1.1.2
id: magnesium-wordcloud-panel version: 1.1.3
id: marcuscalidus-svg-panel version: 0.3.4
id: marcusolsson-dynamictext-panel version: 1.0.1
id: marcusolsson-hourly-heatmap-panel version: 0.6.0
id: marcusolsson-json-datasource version: 0.4.0
id: marcusolsson-static-datasource version: 1.0.1
id: marcusolsson-treemap-panel version: 0.3.0
id: michaeldmoore-annunciator-panel version: 1.0.5
id: michaeldmoore-multistat-panel version: 1.4.1
id: monasca-datasource version: 1.0.1
id: monitoringartist-monitoringart-datasource version: 1.0.1
id: moogsoft-aiops-app version: 8.0.1
id: mtanda-google-calendar-datasource version: 1.0.5
id: mtanda-heatmap-epoch-panel version: 0.1.8
id: mtanda-histogram-panel version: 0.1.7
id: mxswat-separator-panel version: 1.0.1
id: natel-discrete-panel version: 0.1.0
id: natel-influx-admin-panel version: 0.0.6
id: natel-plotly-panel version: 0.0.7
id: natel-usgs-datasource version: 0.0.3
id: neocat-cal-heatmap-panel version: 0.0.4
id: novalabs-annotations-panel version: 0.0.2
id: novatec-sdg-panel version: 2.3.1
id: ntop-ntopng-datasource version: 1.0.1
id: oci-logs-datasource version: 1.1.0
id: oci-metrics-datasource version: 3.0.0
id: opennms-helm-app version: 5.0.2
id: ovh-warp10-datasource version: 2.2.1
id: paytm-kapacitor-datasource version: 0.1.3
id: percona-percona-app version: 1.0.1
id: petrslavotinek-carpetplot-panel version: 0.1.2
id: pierosavi-imageit-panel version: 0.1.3
id: pr0ps-trackmap-panel version: 2.1.0
id: praj-ams-datasource version: 1.2.1
id: pue-solr-datasource version: 1.0.3
id: quasardb-datasource version: 3.8.3
id: rackerlabs-blueflood-datasource version: 0.0.3
id: radensolutions-netxms-datasource version: 1.2.3
id: ryantxu-ajax-panel version: 0.0.7-dev
id: ryantxu-annolist-panel version: 0.0.2
id: satellogic-3d-globe-panel version: 0.1.1
id: savantly-heatmap-panel version: 0.2.1
id: sbueringer-consul-datasource version: 0.1.5
id: scadavis-synoptic-panel version: 1.0.5
id: sidewinder-datasource version: 0.2.1
id: simpod-json-datasource version: 0.2.0
id: skydive-datasource version: 1.2.1
id: smartmakers-trafficlight-panel version: 1.0.1
id: sni-pnp-datasource version: 1.0.8
id: sni-thruk-datasource version: 1.0.6
id: snuids-radar-panel version: 1.4.5
id: snuids-trafficlights-panel version: 1.4.6
id: speakyourcode-button-panel version: 0.2.1
id: spotify-heroic-datasource version: 0.0.2
id: stagemonitor-elasticsearch-app version: 0.83.3
id: udoprog-heroic-datasource version: 0.1.1
id: vertamedia-clickhouse-datasource version: 2.4.2
id: vertica-grafana-datasource version: 0.1.1
id: vonage-status-panel version: 1.0.11
id: voxter-app version: 0.0.2
id: williamvenner-timepickerbuttons-panel version: 2.0.1
id: xginn8-pagerduty-datasource version: 0.2.2
id: yesoreyeram-boomtable-panel version: 1.4.1
id: yesoreyeram-boomtheme-panel version: 0.1.1
id: yeya24-chaosmesh-datasource version: 0.1.2
id: zuburqan-parity-report-panel version: 1.2.2

Restart grafana after installing plugins . <service grafana-server restart>

Tingo (diskusjon) 13. feb. 2022 kl. 14:35 (CET)

2022-02-11
  • Created a new "TV - simplified" dashboard in Grafana and set it as the primary item in the playlist. taz (-) 11. feb. 2022 kl. 22:00 (CET)
  • Added --app flag for chromium-browser in LXDE's autostart script to prevent "Chrome didn't shut down correctly" popup. taz (-) 11. feb. 2022 kl. 20:20 (CET)
2022-01-20 
I added legends to the temperature and humidity graphs in Grafana, so it is easier to see what data the graphs show. Tingo (diskusjon) 20. jan. 2022 kl. 21:18 (CET)

2021

2021-06-30 
no data in temperature and humidity graphs in grafana, so I restated the telegraf service via tingo@iot2:~$ sudo systemctl restart telegraf. Tingo (diskusjon) 30. jun. 2021 kl. 14:15 (CEST)
2021-06-17 
temperature and humidity graphs were empty in grafana, restarting the telegraf service via tingo@iot2:~$ sudo systemctl restart telegraf. Tingo (diskusjon) 17. jun. 2021 kl. 16:19 (CEST)
2021-05-04 
rebooted infoskjerm.local, as it was having trouble displaying the grafana page in Chromium. Hopefully the reboot helps. Tingo (diskusjon) 4. mai 2021 kl. 13:13 (CEST)
2021-02-06 
front door data was not showing in grafana, so I restarted the telegraf service via tingo@iot2:~$ sudo systemctl restart telegraf as usual. Tingo (diskusjon) 6. feb. 2021 kl. 21:36 (CET)

2020

2020-12-30 
no data showing in Grafana, restarted the telegraf service as usual, via tingo@iot2:~$ sudo systemctl restart telegraf. Tingo (diskusjon) 30. des. 2020 kl. 17:15 (CET)
2020-10-27 
front door data was not showing in grafana, so I restarted the telegraf service via tingo@iot2:~$ sudo systemctl restart telegraf as usual. Tingo (diskusjon) 27. okt. 2020 kl. 15:56 (CET)
2020-08-10 
some temperature sensors (Outside, 2nd floor, 4th floor) did not show in grafana, so I restarted the telegraf service (tingo@iot2:~$ sudo systemctl restart telegraf). Didn't seem to help, perhaps the sensors need to be fixed? Tingo (diskusjon) 10. aug. 2020 kl. 14:31 (CEST)
2020-06-19 
the browser wouldn't reconnect to the server (iot2) after it came back online, so I restarted the pi ('shutdown -r now') that fixed it. Tingo (diskusjon) 19. jun. 2020 kl. 12:55 (CEST)
2020-06-18 
environment sensors data was not showing in grafana, so I restarted the telegraf service via tingo@iot2:~$ sudo systemctl restart telegraf as usual. Tingo (diskusjon) 19. jun. 2020 kl. 00:24 (CEST)
2020-06-03 
environment sensors data was not showing in grafana, so I restarted the telegraf service via tingo@iot2:~$ sudo systemctl restart telegraf as usual. Tingo (diskusjon) 3. jun. 2020 kl. 13:11 (CEST)
2020-04-25
front door data was not showing in grafana, so I restarted the telegraf service via tingo@iot2:~$ sudo systemctl restart telegraf as usual. Tingo (diskusjon) 25. apr. 2020 kl. 16:49 (CEST)
2020-02-20
environment sensors data was not showing in grafana again. Restarted the telegraf service via tingo@iot2:~$ sudo systemctl restart telegraf. Tingo (diskusjon) 20. feb. 2020 kl. 19:16 (CET)
2020-02-06
added more sensors to /etc/telegraf/telegraf.conf:
     "public/laser/eco2",
     "public/laser/humidity",
     "public/laser/pm10",
     "public/laser/pm25",
     "public/laser/temperature",
     "public/laser/tvoc",

and reloaded telegraf with sudo systemctl reload telegraf. Tingo (diskusjon) 6. feb. 2020 kl. 09:46 (CET)

2020-01-30 
added more sensors to /etc/telegraf/telegraf.conf:
     "public/printerroom/tvoc",
     "public/printerroom/eco2",
     "public/printerroom/humidity",
     "public/printerroom/temperature",
     "public/lab/pm10",
     "public/lab/pm25",

and reloaded telegraf with sudo systemctl reload telegraf. Tingo (diskusjon) 30. jan. 2020 kl. 20:14 (CET)

2019

2019-11-11 
front door activity was showing "no data points". restarted telegraf service via tingo@iot2:~$ sudo systemctl restart telegraf, it is ok now. Tingo (diskusjon) 14. nov. 2019 kl. 11:27 (CET)
2019-09-05 
front door activity was showing "no data points". restarted telegraf service via tingo@iot2:~$ sudo systemctl restart telegraf, hopefully it will work. Tingo (diskusjon) 5. sep. 2019 kl. 17:58 (CEST)
2019-08-27
environment sensors data was not showing in grafana again. Restarted the telegraf service. Tingo (diskusjon) 27. aug. 2019 kl. 11:39 (CEST)
2019-07-30 
the graphs didn't update on the Pi (update in Grafana was ok). Rebooted the Pi. Tingo (diskusjon) 30. jul. 2019 kl. 09:54 (CEST)
2019-07-26 
the graphs didn't update on the Pi (update in Grafana was ok). Rebooted the Pi. Tingo (diskusjon) 26. jul. 2019 kl. 12:36 (CEST)
2019-07-03 
the graphs didn't update on the Pi (update in Grafana was ok). Rebooted the Pi. Tingo (diskusjon) 3. jul. 2019 kl. 16:29 (CEST)
2019-07-01 
environment sensors data was not showing in grafana again. Restarted the telegraf service. Tingo (diskusjon) 3. jul. 2019 kl. 16:27 (CEST)
2019-06-21 
front door activity was showing "no data points". restarted telegraf service via tingo@iot2:~$ sudo systemctl restart telegraf, but that didn't have any effect. Tingo (diskusjon)
Ok, with patience the data shows up. Tingo (diskusjon) 21. jun. 2019 kl. 13:21 (CEST)
2019-05-09 
environment sensors data was not showing in grafana again. I had to restart the telegraf service via
tingo@iot2:~$ sudo systemctl restart telegraf
in addition, I had to refresh the browser window on the Pi (connected a keyboard and did Ctrl-R). Tingo (diskusjon) 9. mai 2019 kl. 19:48 (CEST)
2019-04-12 
environment sensors data was not showing in grafana again. As usual, a
tingo@iot2:~$ sudo systemctl restart telegraf
fixed the problem. Tingo (diskusjon) 12. apr. 2019 kl. 15:52 (CEST)
2019-01-29 
I also needed to restart the playlist on the welcome screen. Tingo (diskusjon) 29. jan. 2019 kl. 14:39 (CET)
environment sensors data was not showing in grafana again. The telegraf service reported
tingo@iot2:~$ systemctl status telegraf
● telegraf.service - The plugin-driven server agent for reporting metrics into InfluxDB
   Loaded: loaded (/lib/systemd/system/telegraf.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2018-10-12 00:22:04 CEST; 3 months 18 days ago
     Docs: https://github.com/influxdata/telegraf
 Main PID: 448 (telegraf)
    Tasks: 18 (limit: 4915)
   CGroup: /system.slice/telegraf.service
           └─448 /usr/bin/telegraf -config /etc/telegraf/telegraf.conf -config-directory /etc/te

Jan 29 12:44:30 iot2 telegraf[448]: 2019-01-29T11:44:30Z E! Error in plugin [inputs.mqtt_consume
Jan 29 12:44:30 iot2 telegraf[448]: error: pingresp not received, disconnecting
Jan 29 12:44:30 iot2 telegraf[448]: MQTT Client will try to reconnect
Jan 29 12:44:30 iot2 telegraf[448]: 2019-01-29T11:44:30Z I! MQTT Client Connected
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailabl

so I restarted the service via 

tingo@iot2:~$ sudo systemctl restart telegraf

it looks better now 

tingo@iot2:~$ systemctl status telegraf
● telegraf.service - The plugin-driven server agent for reporting metrics into InfluxDB
   Loaded: loaded (/lib/systemd/system/telegraf.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-01-29 14:26:32 CET; 8s ago
     Docs: https://github.com/influxdata/telegraf
 Main PID: 29968 (telegraf)
    Tasks: 14 (limit: 4915)
   CGroup: /system.slice/telegraf.service
           ├─29968 /usr/bin/telegraf -config /etc/telegraf/telegraf.conf -config-directory /etc/
           └─29981 /bin/ping -c 1 -n -s 16 -i 1 -W 1 -w 10 10.13.37.47

Jan 29 14:26:33 iot2 telegraf[29968]: 2019-01-29T13:26:33Z I! Loaded aggregators:
Jan 29 14:26:33 iot2 telegraf[29968]: 2019-01-29T13:26:33Z I! Loaded processors:
Jan 29 14:26:33 iot2 telegraf[29968]: 2019-01-29T13:26:33Z I! Loaded outputs: influxdb
Jan 29 14:26:33 iot2 telegraf[29968]: 2019-01-29T13:26:33Z I! Tags enabled: host=iot2
Jan 29 14:26:33 iot2 telegraf[29968]: 2019-01-29T13:26:33Z I! Agent Config: Interval:10s, Quiet:
Jan 29 14:26:33 iot2 telegraf[29968]: 2019-01-29T13:26:33Z I! MQTT Client Connected
Jan 29 14:26:33 iot2 telegraf[29968]: 2019-01-29T13:26:33Z I! MQTT Client Connected
Jan 29 14:26:33 iot2 telegraf[29968]: 2019-01-29T13:26:33Z I! MQTT Client Connected
Jan 29 14:26:33 iot2 telegraf[29968]: 2019-01-29T13:26:33Z I! MQTT Client Connected
Jan 29 14:26:33 iot2 telegraf[29968]: 2019-01-29T13:26:33Z I! MQTT Client Connected

Maybe telegraf needs to be restarted every time the mqtt server is restarted? Tingo (diskusjon) 29. jan. 2019 kl. 14:32 (CET)

2018

2018-10-12 
grafana-server.service was not enabled on the server, so it didn't start automatically when the server got restarted. Fixed. --Tingo (diskusjon) 12. okt. 2018 kl. 09:16 (UTC)
2018-09-18 
measurement mqtt_consumer i mqtt_bitraf hadde data som ikke var oppdatert, selv om alle de andre i samme database var oppdatert. "Løst" ved å restarte telegraf vha. sudo systemctl restart telegraf. --Tingo (diskusjon) 18. sep. 2018 kl. 14:32 (UTC)

Referanser

  1. ↑ https://grafana.com/grafana Grafana
  2. ↑ https://www.influxdata.com/time-series-platform/telegraf/ Telegraf
  3. ↑ https://www.influxdata.com/time-series-platform/influxdb/ Influxdb
  4. ↑ https://www.influxdata.com/time-series-platform/kapacitor/ Kapacitor
  5. ↑ https://www.influxdata.com/time-series-platform/chronograf/ Chronograf
Hentet fra «https://wiki.bitraf.no/w/index.php?title=Prosjekt_Velkomstskjerm&oldid=10096»