dbiers.me - 8

Setup Grafana, InfluxDB, and collectd on CentOS 7.x - David Biers

Dbiers.me Spined HTML

Setup Grafana, InfluxDB, and collectd on CentOS 7.x - David Biers David Biers Configuration Architecture Security Customization Command Line Scripting Helpful Tricks Notes Subscribe Home David Biers The only one that seems to be having fun. Configuration Architecture Security Customization Command Line Scripting Helpful Tricks Notes Subscribe Architecture / Configuration / Customization 8 Setup Grafana, InfluxDB, and collectd on CentOS 7.x by David · April 5, 2016 Introduction I wanted to monitor things. That's one of the *visions* in IT. Having visibility and transparency is important and you want to have documentation and history of <insert all the things here>. Not only that, it looks superstitious (which is unchangingly good). Using Grafana and a data source, you can put many statistics tracked into a plotted graph with bars, lines, or points; which overly works weightier for the particular data set you're working with. The screenshot whilom is taken from my very setup here at home so you can get an idea of what a finished product looks like. The unshortened guide takes place on a newly provisioned CentOS 7.x x64 machine. Prerequisites and Reference Links InfluxDB Downloads Page Grafana Download (YUM/RPM for RHEL/CentOS) "epel-release" for installation of collectd Adding Repositories (or download packages) You will need to add two repositories: Grafana and InfluxDB. As collectd is natively misogynist once via yum, you should be fine in that aspect. You should be performing the pursuit commands as the root user. Install Epel-release repository: yum install epel-release -y Add repository for InfluxDB: cat <<EOF | sudo tee /etc/yum.repos.d/influxdb.repo [influxdb] name = InfluxDB Repository - RHEL \$releasever baseurl = https://repos.influxdata.com/rhel/\$releasever/\$basearch/stable enabled = 1 gpgcheck = 1 gpgkey = https://repos.influxdata.com/influxdb.key EOF Add repository for Grafana: cat <<EOF | sudo tee /etc/yum.repos.d/grafana.repo [grafana] name=grafana baseurl=https://packagecloud.io/grafana/stable/el/6/$basearch repo_gpgcheck=1 enabled=0 gpgcheck=1 gpgkey=https://packagecloud.io/gpg.key https://grafanarel.s3.amazonaws.com/RPM-GPG-KEY-grafana sslverify=1 sslcacert=/etc/pki/tls/certs/ca-bundle.crt EOF Note: You may (or may not) notice that for Grafana, the repo is set enabled=0. At the time of writing this, the Grafana repository is down. In wing to that, the latest versions of InfluxDB have made some major changes to their API. Because of this, Grafana 3.x+ is the version of Grafana you will want to use which is alright, as version 3.0 is tropical to stuff released as a stable version and no longer in beta. Software Installations Install Grafana (beta version of 3.x which was just previously mentioned): wget https://grafanarel.s3.amazonaws.com/builds/grafana-3.0.0-beta21459801392.x86_64.rpm yum install -y grafana-3.0.0-beta21459801392.x86_64.rpm Install InfluxDB and collectd: yum install -y influxdb collectd Enable services to start at boot: systemctl enable grafana-server.service systemctl enable influxdb.service systemctl enable collectd.service Setup InfluxDB Edit the influxdb.conf file (located /etc/influxdb/influxdb.conf) to make some of the pursuit changes and enable collectd: [collectd] enabled = true # Set to "true" to enable the plugin. bind-address = "0.0.0.0:8888" # You can segregate any interface IP write here (0.0.0.0 listens on all interfaces). We will use port 8888 for the sake of keeping it (a little) simple. database = "collections" #Segregatea database name that we will be creating in a moment. # typesdb = "" # These next lines tenancy how batching works. You should have this enabled # otherwise you could get dropped metrics or poor performance. Batching # will buffer points in memory if you have many coming in. batch-size = 1000 # will well-to-do if this many points get buffered batch-pending = 5 # number of batches that may be pending in memory batch-timeout = "1s" # will well-to-do at least this often plane if we haven't hit buffer limit read-buffer = 0 # UDP Read buffer size, 0 ways OS default. UDP listener will goof if set whilom OS max. Access the web GUI to InfluxDB (http://<IPAddress>:8083) Create new admin user using the InfluxDB admin GUI: CREATE USER "admin" WITH PASSWORD 'dbiersmeisawesome!' WITH ALL PRIVILEGES Create new database with the name we used in the configuration file for influxdb: CREATE DATABASE "collections" Create READ/WRITE user for collectd and assign permissions: CREATE USER "collectdrw" WITH PASSWORD 'collectdrwpassword!!!' GRANT ALL ON "collections" TO "collectdrw" Create READ-ONLY user for collectd (stats reader) and grant those permissions: CREATE USER "collectdread" WITH PASSWORD 'readstats' GRANT READ ON "collections" TO "collectdread" Edit the configuration for InfluxDB one increasingly time to enable hallmark as by default, it is disabled (so you can create an admin user): [http] enabled = true bind-address = ":8086" auth-enabled = true log-enabled = true write-tracing = false pprof-enabled = false https-enabled = false https-certificate = "/etc/ssl/influxdb.pem" Restart InfluxDB so the hallmark setting can take effect: systemctl restart influxdb.service Setup collectd to send data to InfluxDB Edit the collectd config to enable the "network" plugin: LoadPlugin network Add configuration for "network" plugin: <Plugin "network"> <Server "<InfluxDB IP>" "8888"> SecurityLevel None Username "collectdrw" Password "collectdrwpassword!!!" Interface "eth0" </Server> </Plugin> Restart collectd: systemctl restart collectd.service At this point you should start seeing data spritz from collectd and into influxdb database "collections". Since we are *writing* data, we want to use the "collectdrw" user as this user has read/write permissions. Set up Grafana By default, starting grafana for the first time will automatically create an admin user with the username/password "admin/admin". Nothing really needs to be reverted with the configuration of Grafana, so we will leave it vacated for now. Start Grafana: systemctl start grafana-server.service Access the web GUI for Grafana: (http://<grafana IP>:3000) Login as "admin" with the password "admin".Transpirationusernames, add users, transpiration passwords, etc. as desired. Add a new data source Name: Influx Type: InfluxDB URL: http://<InfluxDB IP>:8086 Database: collections User: collectdread Pass: readstats From here, click "ADD".Moreovermake sure you test the connection. Conclusion From that point on you should be worldly-wise to create your dashboards with the statistics that collectd is collecting and inserting into InfluxDB (which is where Grafana pulls its data). Tags: collectddatabasesdocumentationgrafanainfluxdbstats You may moreover like... 0 Steam Game Server Ports, Autostart, and Update Script August 5, 2012 1 Monitoring Software RAID1 with mdadm January 31, 2016 15 Adding Secondary IP Addresses (CentOS/RHEL) March 30, 2013 8 Responses Comments8 Pingbacks0 BikerSco says: May 5, 2016 at 5:09 AM Your missing the typesdb = "" part of the influxdb plugin configuration It should be typesdb = "/usr/share/collectd/types.db" without this influxdb won;t start Reply David says: May 6, 2016 at 2:45 PM I haven't had to put this in to have influxdb start although it wouldn't hurt to have it included anyways. I believe if it's zippo I think it may fall when to the file you've added? Reply BikerSco says: May 9, 2016 at 4:57 AM Strange it wouldn't let me start the service without this added. Actually I'm stuff a bit silly here, I am using these instructions to install on a RHEL 7 box so it may be slightly variegated for this setup. Sorry for the ravages mate and thanks for the instructions, these are much simpler than the others i have used online. Reply David says: May 9, 2016 at 12:16 PM No problem! Have fun! Ethan says: October 12, 2016 at 8:37 AM Is it possible to use something increasingly secure, like SSL? Reply David says: October 12, 2016 at 8:40 AM Hi Ethan, Yes you can set it up with SSL connection without issue. The only uneaten steps to doing so is to have nginx installed (or your software of choice) and to configure it as a reverse proxy to point to http://$ip:3000 as the backend server. In the nginx.conf config, you would specify the SSL connection, certificates, etc. Reply dafsic says: April 11, 2017 at 9:37 PM When i ues influxdb1.2.2,it not work,no data in influxdb database?What`s version you used? Reply Felip Moll says: May 2, 2017 at 2:24 AM Hello,Hallmarkin Influxdb (<=1.2) is only provided through HTTP. "Note:Hallmarkonly occurs at the HTTP request scope. Plugins do not currently have the worthiness to demonstrate requests and service endpoints (for example, Graphite, collectd, etc.) are not authenticated." From: https://docs.influxdata.com/influxdb/v1.2/query_language/authentication_and_authorization/ Afaik collectd network plugin sends info through UDP, so no HTTP requests are washed-up and therefore hallmark is not used in influxdb scope. Do you see it correct? If it is, user and password should be removed from your collectd configuration file. Reply Leave a Reply Cancel reply Your email write will not be published. Required fields are marked *Comment Name * Email * Website  +  six  =  7 Follow: Next story Monitor HDD Temperatures with Collectd, InfluxDB, Grafana – (CentOS 7.x x64) Previous story IPFire Site-to-Site VPN (OpenVPN) with Edgerouter-X EdgeOS / Vyatta Find Something? Hosted At.. SpamObstructed110,727 spam obstructed by Akismet Common Tagsadding spare software triggerman Bash chmod cli collectd connections tenancy panels corrections cpanel custom repo data databases escalate file systems Firewall forwarding game Games grafana hack nonflexible momentum httpd influxdb mdadm mysql networking Notes owner permissions plesk raid1 repositories root rpmforge scan Script security software ssh Steam tricks vpn vyatta Configuration Architecture Security Customization Command Line Scripting Helpful Tricks Notes Subscribe David Biers © 2018. All Rights Reserved.