Deploy a Container TIG (Telegraf, InfluxDB and Grafana) Stack

My simplified container based TIG stack is built using docker. The following standalone design supported more than 500+ VM to monitor data.

Versions:

• Docker- Docker version 29.1.3, build f52814d
• Telegraf- Telegraf 1.14.3 (git: HEAD 1b35d6c2)
• Influxdb- 1.6.4
• Grafana- 10.0.3

Here’s the TIG Docker Script-

version: '3.7'

services:
influxdb:
image: influxdb:1.6.4
container_name: influxdb
restart: unless-stopped
ports:
- "8086:8086"
volumes:
- /data/container-data/influxdb:/var/lib/influxdb
networks:
- ig-network

grafana:
image: grafana/grafana:10.0.3
container_name: grafana
restart: unless-stopped
ports:
- "3000:3000"
volumes:
- grafana_data:/var/lib/grafana
depends_on:
- influxdb
environment:
GF_SECURITY_ADMIN_USER: admin
GF_SECURITY_ADMIN_PASSWORD: admin
networks:
- ig-network

volumes:
influxdb_data:
grafana_data:

networks:
ig-network:
driver: bridge

TIG Stag Deployment for client data Matrix Collection

You can follow the below steps and procedure on the client side to push matrix data using the telegraf agent.

**Telegraf Agent**
For Debian/Ubuntu (Debian 10/+ and Ubuntu 20/+

wget https://dl.influxdata.com/telegraf/releases/telegraf_1.14.3-1_amd64.deb

**For RPM Based (CentOS 7/+ or RHEL 7/+**

wget https://dl.influxdata.com/telegraf/releases/telegraf-1.14.3-1.x86_64.rpm

**Post Installation**
1. Check telegraf daemon is running-

systemctl status telegraf

2. Enable telegraf daemon on boot-

systemctl enable telegraf

3. Rename default telegraf.conf file.

mv /etc/telegraf/telagraf.conf /etc/telegraf/telegraf.src

4. Copy the pre-configured telegraf file

cp telegraf.conf /etc/telegraf/

5. Restart telegraf daemon

systemctl restart telegraf

For managability of the stack better, you can also deploy portainer and NGINX proxy manager for a cleaner interface.

Resource-Reference-Files