Grafana + InfluxDB: Difference between revisions

From HELIOS Digital DAQ
Jump to navigation Jump to search
No edit summary
Line 20: Line 20:
To run the monitor program, login to the DAQ (digios1.onenet)
To run the monitor program, login to the DAQ (digios1.onenet)


  Helios_Database Start
  digios1$ Helios_Database Start


To stop the monitor program,  
To stop the monitor program,  


  Helios_Database Stop
  digios1$ Helios_Database Stop


Grafana was also installed in heliosDB.  
Grafana was also installed in heliosDB.  

Revision as of 23:43, May 17, 2019

Introduction

In order to monitor the HELIOS system, for example, the threshold, the tigger rate, the buffer size, etc. We monitor and save those data into a database managed by InfluxDB. The database is further read by Grafana for display.

For more information on InfluxDB and Grafana, see:

InfluxDB documentation

Grafana

Present setting

The data (e.g. trigger Rate, threshold, Buffer ) must be taking in digios1, the DAQ.

Since the DAQ is running on a 32-bit system. the influxDB is unstable.

The database was installed in heliosDB.onenet.

Thus, the data will be push to heliosDB.

To run the monitor program, login to the DAQ (digios1.onenet)

digios1$ Helios_Database Start

To stop the monitor program,

digios1$ Helios_Database Stop

Grafana was also installed in heliosDB.

To run Grafana, from any browser, within onenet, type

http://heliosDB.onenet:3000

Setup InfluxDB

For 64bit-linux, the setup is straight forward.

For example, in Ubuntu-18.x, simply type

sudo apt-get install influxdb

The influxdb contains 2 main programs,

  1. influx, for interactive database operations
  2. influxd, a daemon run in background, for receiving query from port 8086

To run the influxd

sudo service influxdb start