Traefik Log Dashboard

A comprehensive analytics platform for Traefik access logs with three deployment options: a Go-based API agent, a modern Next.js web dashboard, and a beautiful terminal-based CLI.

A comprehensive real-time analytics platform for Traefik reverse proxy logs

MIGRATION GUIDE from V1 to V2: ./docs/MigrationV1toV2.md

Overview

Traefik Log Dashboard is a powerful analytics platform that provides real-time insights into your Traefik reverse proxy traffic. It consists of three components that work together:

Agent - Go-based backend API that parses logs and exposes metrics
Dashboard - Next.js web UI with interactive charts and real-time updates
CLI - Beautiful terminal-based dashboard (optional)

---

---

---

---

---

Architecture

Multi-Agent Architecture

The platform supports a multi-agent architecture where you can deploy multiple agent instances across different Traefik installations and aggregate their data through a single dashboard.

┌─────────────────────────────────────────────────────────────┐
│                     Traefik Instances                       │
│  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐       │
│  │ Traefik #1   │  │ Traefik #2   │  │ Traefik #3   │       │
│  │ (Production) │  │ (Staging)    │  │ (Development)│       │
│  └──────┬───────┘  └──────┬───────┘  └──────┬───────┘       │
│         │ Logs            │ Logs            │ Logs          │
└─────────┼─────────────────┼─────────────────┼───────────────┘
          │                 │                 │
          ▼                 ▼                 ▼
┌─────────────────────────────────────────────────────────────┐
│                    Agent Layer                              │
│  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐       │
│  │ Agent #1     │  │ Agent #2     │  │ Agent #3     │       │
│  │ Port: 5000   │  │ Port: 5001   │  │ Port: 5002   │       │
│  │ • Log Parser │  │ • Log Parser │  │ • Log Parser │       │
│  │ • GeoIP      │  │ • GeoIP      │  │ • GeoIP      │       │
│  │ • Metrics    │  │ • Metrics    │  │ • Metrics    │       │
│  └──────┬───────┘  └──────┬───────┘  └──────┬───────┘       │
└─────────┼─────────────────┼─────────────────┼───────────────┘
          │ REST API        │ REST API        │ REST API
          └─────────────────┴─────────────────┴──────┐
                                                     │
                                                     ▼
                                          ┌─────────────────────┐
                                          │  Dashboard Web UI   │
                                          │                     │
                                          │  • Multi-agent mgmt │
                                          │  • Aggregated views │
                                          │  • Real-time charts │
                                          │  • Geographic maps  │
                                          └─────────────────────┘

Component Breakdown

Agent (Go)

Parses Traefik logs (JSON/CLF format)
Exposes REST API endpoints
Performs GeoIP lookups
Monitors system resources
Supports incremental log reading

Dashboard (Next.js)

Connects to multiple agents
Displays 15+ interactive cards
Real-time data visualization
Demo mode for testing
Responsive design

CLI (Optional)

Terminal-based dashboard
Direct log file reading
Agent API integration
Bubble Tea TUI

Features

Core Features

Real-time Monitoring - Live request tracking with auto-refresh
Comprehensive Metrics - Request rates, response times, status codes, error rates
Geographic Analytics - Request distribution with GeoIP support
Interactive Charts - Chart.js and D3.js powered visualizations
System Monitoring - CPU, memory, and disk usage tracking
Multi-Agent Support - Manage and monitor multiple Traefik instances
Beautiful UI - Modern responsive design with Tailwind CSS 4
Advanced Filtering - Filter logs by status code, time period, and more
Multiple Log Formats - JSON and Common Log Format (CLF) support
Gzip Support - Compressed log file handling
Bearer Token Auth - Secure API access

Quick Start

Using Docker Compose (Recommended)

# Clone the repository
git clone https://github.com/hhftechnology/traefik-log-dashboard.git
cd traefik-log-dashboard

# Create data directories for GeoIP
mkdir -p ./data/geoip
mkdir -p ./data/positions

# Start services
docker-compose up -d

# Access the dashboard
open http://localhost:3000

Docker Compose Configuration

services:
  # Backend Agent - Parses logs and exposes API
  traefik-agent:
    image: hhftechnology/traefik-log-dashboard-agent:latest
    container_name: traefik-log-dashboard-agent
    restart: unless-stopped
    ports:
      - "5000:5000"
    volumes:
      # Mount your Traefik log directory (read-only)
      - /root/config/traefik/logs:/logs:ro
      # Mount GeoIP databases (read-only)
      - ./data/geoip:/geoip:ro
      # Position tracking for incremental reads
      - ./data/positions:/data
    environment:
      # Log file paths
      - TRAEFIK_LOG_DASHBOARD_ACCESS_PATH=/logs/access.log
      - TRAEFIK_LOG_DASHBOARD_ERROR_PATH=/logs/access.log
      
      # Authentication (change this!)
      - TRAEFIK_LOG_DASHBOARD_AUTH_TOKEN=d41d8cd98f00b204e9800998ecf8427e
      
      # Enable system monitoring
      - TRAEFIK_LOG_DASHBOARD_SYSTEM_MONITORING=true
      
      # GeoIP Configuration
      - TRAEFIK_LOG_DASHBOARD_GEOIP_ENABLED=true
      - TRAEFIK_LOG_DASHBOARD_GEOIP_CITY_DB=/geoip/GeoLite2-City.mmdb
      - TRAEFIK_LOG_DASHBOARD_GEOIP_COUNTRY_DB=/geoip/GeoLite2-Country.mmdb
      
      # Log format (json or clf)
      - TRAEFIK_LOG_DASHBOARD_LOG_FORMAT=json
      
      # Server port
      - PORT=5000
    healthcheck:
      test: ["CMD", "wget", "--no-verbose", "--tries=1", "--spider", "http://localhost:5000/api/logs/status"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 10s
    networks:
      - pangolin

  # Frontend Dashboard - Web UI
  traefik-dashboard:
    image: hhftechnology/traefik-log-dashboard:latest
    container_name: traefik-log-dashboard
    restart: unless-stopped
    ports:
      - "3000:3000"
    environment:
      # Agent connection
      - AGENT_API_URL=http://traefik-agent:5000
      - AGENT_API_TOKEN=d41d8cd98f00b204e9800998ecf8427e
      
      # Node environment
      - NODE_ENV=production
      - PORT=3000
    depends_on:
      traefik-agent:
        condition: service_healthy
    healthcheck:
      test: ["CMD", "wget", "--no-verbose", "--tries=1", "--spider", "http://localhost:3000"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 30s
    networks:
      - pangolin

networks:
  pangolin:
    external: true

Multi-Agent Setup

Adding Multiple Agents

The dashboard supports managing multiple agent instances. Here's how to set up a multi-agent environment:

1. Deploy Multiple Agents

Create a docker-compose.multi-agent.yml:

services:
  # Production Agent
  traefik-agent-prod:
    image: hhftechnology/traefik-log-dashboard-agent:latest
    container_name: traefik-agent-prod
    ports:
      - "5000:5000"
    volumes:
      - /var/log/traefik/prod:/logs:ro
      - ./data/geoip:/geoip:ro
      - ./data/positions-prod:/data
    environment:
      - TRAEFIK_LOG_DASHBOARD_ACCESS_PATH=/logs/access.log
      - TRAEFIK_LOG_DASHBOARD_AUTH_TOKEN=prod_token_here
      - TRAEFIK_LOG_DASHBOARD_GEOIP_ENABLED=true
      - TRAEFIK_LOG_DASHBOARD_GEOIP_CITY_DB=/geoip/GeoLite2-City.mmdb

  # Staging Agent
  traefik-agent-staging:
    image: hhftechnology/traefik-log-dashboard-agent:latest
    container_name: traefik-agent-staging
    ports:
      - "5001:5000"
    volumes:
      - /var/log/traefik/staging:/logs:ro
      - ./data/geoip:/geoip:ro
      - ./data/positions-staging:/data
    environment:
      - TRAEFIK_LOG_DASHBOARD_ACCESS_PATH=/logs/access.log
      - TRAEFIK_LOG_DASHBOARD_AUTH_TOKEN=staging_token_here
      - TRAEFIK_LOG_DASHBOARD_GEOIP_ENABLED=true

  # Development Agent
  traefik-agent-dev:
    image: hhftechnology/traefik-log-dashboard-agent:latest
    container_name: traefik-agent-dev
    ports:
      - "5002:5000"
    volumes:
      - /var/log/traefik/dev:/logs:ro
      - ./data/geoip:/geoip:ro
      - ./data/positions-dev:/data
    environment:
      - TRAEFIK_LOG_DASHBOARD_ACCESS_PATH=/logs/access.log
      - TRAEFIK_LOG_DASHBOARD_AUTH_TOKEN=dev_token_here

  # Single Dashboard
  traefik-dashboard:
    image: hhftechnology/traefik-log-dashboard:latest
    container_name: traefik-dashboard
    ports:
      - "3000:3000"
    environment:
      - NODE_ENV=production
    depends_on:
      - traefik-agent-prod
      - traefik-agent-staging
      - traefik-agent-dev

2. Configure Agents in Dashboard

Navigate to Settings → Agents in the dashboard and add your agents:

Click "Add Agent"
Enter agent details:
- Name: Production
- URL: http://traefik-agent-prod:5000
- Token: prod_token_here
Click "Save"
Repeat for staging and development agents

3. Switch Between Agents

Use the agent selector dropdown in the dashboard header to switch between different agent views.

GeoIP Database Setup

GeoIP functionality requires MaxMind GeoLite2 databases. Here's how to set them up:

Step 1: Download GeoLite2 Databases

Sign up for MaxMind account (free):
- Visit: https://dev.maxmind.com/geoip/geolite2-free-geolocation-data
- Create a free account

Download databases:

# Create directory
mkdir -p ./data/geoip

# Download GeoLite2-City (recommended)
# Download GeoLite2-Country (fallback)

Extract databases:

# Extract .tar.gz files
tar -xzf GeoLite2-City.tar.gz
tar -xzf GeoLite2-Country.tar.gz

# Copy .mmdb files to data directory
cp GeoLite2-City_*/GeoLite2-City.mmdb ./data/geoip/
cp GeoLite2-Country_*/GeoLite2-Country.mmdb ./data/geoip/

Step 2: Configure Agent

Update your agent environment variables:

environment:
  # Enable GeoIP
  - TRAEFIK_LOG_DASHBOARD_GEOIP_ENABLED=true
  
  # Database paths (inside container)
  - TRAEFIK_LOG_DASHBOARD_GEOIP_CITY_DB=/geoip/GeoLite2-City.mmdb
  - TRAEFIK_LOG_DASHBOARD_GEOIP_COUNTRY_DB=/geoip/GeoLite2-Country.mmdb

Step 3: Mount Volume

Ensure the GeoIP directory is mounted:

volumes:
  - ./data/geoip:/geoip:ro

Step 4: Verify GeoIP Status

Check if GeoIP is working:

# Check agent logs
docker logs traefik-log-dashboard-agent

# You should see:
# GeoIP: Enabled
# GeoIP: Successfully initialized

GeoIP Features

Once configured, you'll get:

Country-level geolocation for all IP addresses
City-level geolocation (if using City database)
Latitude/Longitude coordinates for mapping
Private IP detection (shows as "Private")
Geographic distribution card showing top countries
Interactive world map with request heatmap

Updating GeoIP Databases

MaxMind updates databases regularly. Update them periodically:

# Download latest versions
# Extract new databases
# Replace old .mmdb files
# Restart agent
docker restart traefik-log-dashboard-agent

Dashboard Cards Explained

The dashboard displays 15+ interactive cards providing comprehensive insights:

1. Request Metrics Card

Click to expand

What it shows:

Total number of requests processed
Requests per second rate
Trend indicator (increase/decrease %)
Sparkline showing request activity

Use cases:

Monitor traffic volume
Identify traffic spikes
Track growth trends

Metrics:

Total Requests: 125,847
Rate: 42.3 req/s
Change: +15.2% ↑

2. Response Time Card

Click to expand

What it shows:

Average response time (mean)
P95 percentile (95% of requests faster than this)
P99 percentile (99% of requests faster than this)
Response time distribution histogram

Use cases:

Identify performance issues
Track backend latency
Set SLA targets

Metrics:

Average: 245ms
P95: 580ms
P99: 1,240ms

3. Status Codes Card

Click to expand

What it shows:

Distribution of HTTP status codes
2xx (Success) - Green
3xx (Redirects) - Blue
4xx (Client Errors) - Yellow
5xx (Server Errors) - Red
Overall error rate percentage

Use cases:

Monitor service health
Identify error patterns
Track success rate

Metrics:

2xx: 98,234 (78.1%)
3xx: 15,432 (12.3%)
4xx: 8,945 (7.1%)
5xx: 3,236 (2.5%)
Error Rate: 9.6%

4. Status Code Distribution Card

Click to expand

What it shows:

Visual pie chart of status code distribution
Percentage breakdown
Color-coded segments

Use cases:

Quick visual health check
Identify anomalies
Report generation

5. Request Timeline Card

Click to expand

What it shows:

Time-series chart of request volume
Request activity over time (last N minutes/hours)
Peak request rate indicator
Interactive chart with hover details

Use cases:

Identify traffic patterns
Spot unusual activity
Capacity planning

Features:

20+ data points
Smooth line chart
Peak/min indicators

6. Top Routes Card

Click to expand

What it shows:

Most frequently requested paths
Request count per route
Average response time per route
HTTP method (GET, POST, etc.)
Percentage of total traffic

Use cases:

Identify popular endpoints
Optimize frequently used routes
Plan caching strategy

Example:

#1 /api/users        15,234 (12.1%)  avg: 145ms  GET
#2 /api/products     12,847 (10.2%)  avg: 234ms  GET
#3 /auth/login        8,456 (6.7%)   avg: 456ms  POST

7. Backend Services Card

Click to expand

What it shows:

List of backend services receiving traffic
Request count per service
Average response time
Error rate per service
Health status (Healthy/Warning/Critical)
Service URL

Health indicators:

🟢 Healthy: Error rate < 5%
🟡 Warning: Error rate 5-10%
🔴 Critical: Error rate > 10%

Use cases:

Monitor backend health
Identify problematic services
Balance traffic distribution

Example:

Service: api-backend
  Requests: 45,234 (36%)
  Avg Time: 234ms
  Error Rate: 2.3% 🟢
  URL: http://backend:8080

8. Routers Card

Click to expand

What it shows:

Traefik routers handling requests
Request count per router
Average response time
Associated service
Traffic distribution bars

Use cases:

Monitor router performance
Identify routing issues
Optimize rule matching

Example:

#1 api-router → api-service
   15,234 requests  avg: 234ms
   [████████████████░░░░] 78%

9. Top Client IPs Card

Click to expand

What it shows:

Most active client IP addresses
Request count per IP
Percentage of total traffic
Geographic location (if GeoIP enabled)

Use cases:

Identify heavy users
Detect potential DDoS
Analyze traffic sources

Example:

#1 192.168.1.100  12,345 (9.8%)  🇺🇸 USA
#2 10.0.0.50       8,234 (6.5%)  🇬🇧 UK
#3 172.16.0.10     5,678 (4.5%)  🇩🇪 Germany

10. Top Request Hosts Card

Click to expand

What it shows:

Most requested hostnames/domains
Request count per host
Percentage breakdown

Use cases:

Multi-tenant monitoring
Virtual host analysis
Traffic segmentation

Example:

#1 api.example.com     45,234 (36%)
#2 www.example.com     32,145 (25.6%)
#3 staging.example.com 15,234 (12.1%)

11. Top Request Addresses Card

Click to expand

What it shows:

Full client addresses (IP:Port)
Request count
Connection patterns

Use cases:

Detailed client analysis
Connection pooling insights
Port usage patterns

12. User Agents Card

Click to expand

What it shows:

Browser/client type distribution
Request count per user agent
Percentage breakdown
Parsed browser names (Chrome, Firefox, Safari, etc.)

Use cases:

Browser compatibility planning
Bot detection
Client analytics

Example:

Chrome:  45,234 (36%)
Firefox: 23,456 (18.7%)
Safari:  18,234 (14.5%)
Bot:     12,345 (9.8%)

13. Geographic Distribution Card

Click to expand

What it shows:

Request distribution by country
Top 10 countries by traffic
Request count and percentage
Country flags

Requirements:

GeoIP database configured

Use cases:

Geographic traffic analysis
CDN planning
Regional performance insights

Example:

🇺🇸 United States  34,567 (27.5%)
🇬🇧 United Kingdom 23,456 (18.6%)
🇩🇪 Germany        15,234 (12.1%)

14. Interactive Geographic Map Card

Click to expand

What it shows:

World map with request heatmap
Color-coded countries by traffic volume
Interactive hover information
Zoom and pan functionality

Requirements:

GeoIP database with coordinates
D3.js visualization

Use cases:

Visual traffic distribution
Presentations and reports
Geographic insights

15. Recent Errors Card

Click to expand

What it shows:

Latest error entries (4xx and 5xx)
Timestamp of error
HTTP method and path
Status code
Router and service involved
Error level (Warning/Error)

Color coding:

🟡 Warning: 4xx errors (client-side)
🔴 Error: 5xx errors (server-side)

Use cases:

Real-time error monitoring
Debugging issues
Alert investigation

Example:

🔴 500 Internal Server Error
   2024-10-15 14:23:45
   POST /api/orders
   Router: api-router → backend-service

16. System Resources Cards (CPU, Memory, Disk)

Click to expand

What it shows:

CPU Card:

Current CPU usage percentage
Number of cores
Health status

Memory Card:

Memory usage percentage
Used / Total memory
Available memory

Disk Card:

Disk usage percentage
Used / Total space
Available space

Health indicators:

🟢 Healthy: < 70%
🟡 Warning: 70-90%
🔴 Critical: > 90%

Requirements:

TRAEFIK_LOG_DASHBOARD_SYSTEM_MONITORING=true

Use cases:

Server health monitoring
Capacity planning
Resource optimization

17. Recent Logs Table

Click to expand

What it shows:

Detailed table of recent log entries
Customizable columns
Sortable fields
Color-coded status codes
Expandable for full details

Default columns:

Timestamp
Method
Path
Status
Duration
Client IP

Optional columns:

Service Name
Router Name
Request Host
User Agent
Origin Duration
Overhead
And more...

Use cases:

Detailed request inspection
Debugging specific requests
Log analysis

Filter Logs & API Usage

The agent exposes REST API endpoints with powerful filtering capabilities.

API Endpoints

1. Get Access Logs

GET /api/logs/access

Query Parameters:

position - Starting position for incremental read (default: 0)
lines - Number of lines to read (default: 1000)
period - Time period filter (e.g., 1h, 24h, 7d)
status - Filter by status code (e.g., 200, 404, 500)

Example:

curl -H "Authorization: Bearer your_token" \
  "http://localhost:5000/api/logs/access?period=1h&lines=500"

Response:

{
  "logs": [...],
  "count": 500,
  "position": 12345
}

2. Get Error Logs (4xx/5xx only)

GET /api/logs/error

Query Parameters:

position - Starting position
lines - Number of lines (default: 100)
period - Time period filter
status - Specific status code filter

Example:

curl -H "Authorization: Bearer your_token" \
  "http://localhost:5000/api/logs/error?status=500&period=24h"

3. Get Status Distribution

GET /api/logs/status

Example:

curl -H "Authorization: Bearer your_token" \
  "http://localhost:5000/api/logs/status"

Response:

{
  "total_requests": 125847,
  "status_2xx": 98234,
  "status_3xx": 15432,
  "status_4xx": 8945,
  "status_5xx": 3236,
  "error_rate": 9.6
}

4. Get System Resources

GET /api/system/resources

Example:

curl -H "Authorization: Bearer your_token" \
  "http://localhost:5000/api/system/resources"

Response:

{
  "cpu": {
    "usage_percent": 45.2,
    "cores": 8
  },
  "memory": {
    "total": 16384,
    "used": 8192,
    "usage_percent": 50.0
  },
  "disk": {
    "total": 500000,
    "used": 250000,
    "usage_percent": 50.0
  }
}

5. Get Log File Sizes

GET /api/system/logs

Example:

curl -H "Authorization: Bearer your_token" \
  "http://localhost:5000/api/system/logs"

Time Period Formats

Supported formats for period parameter:

15m - Last 15 minutes
30m - Last 30 minutes
1h - Last 1 hour
3h - Last 3 hours
6h - Last 6 hours
12h - Last 12 hours
24h - Last 24 hours
7d - Last 7 days
30d - Last 30 days

Status Code Filtering

Filter by specific status codes or ranges:

# Specific status code
?status=404

# Success codes
?status=200

# All 4xx errors
?status=4xx

# All 5xx errors
?status=5xx

# Combine with period
?status=500&period=1h

Incremental Log Reading

The agent tracks reading positions to efficiently handle large log files:

# First request - start from beginning
curl "http://localhost:5000/api/logs/access?lines=1000"
# Response includes: "position": 45678

# Next request - continue from last position
curl "http://localhost:5000/api/logs/access?position=45678&lines=1000"

Position tracking is stored in the /data volume.

Configuration

Agent Environment Variables

# Server Configuration
PORT=5000                                    # Agent listening port

# Log Paths
TRAEFIK_LOG_DASHBOARD_ACCESS_PATH=/logs/access.log   # Access log file
TRAEFIK_LOG_DASHBOARD_ERROR_PATH=/logs/traefik.log   # Error log file

# Log Format
TRAEFIK_LOG_DASHBOARD_LOG_FORMAT=json       # json or clf

# System Monitoring
TRAEFIK_LOG_DASHBOARD_SYSTEM_MONITORING=true # Enable system stats

# Authentication
TRAEFIK_LOG_DASHBOARD_AUTH_TOKEN=your_token  # Bearer token (required)

# GeoIP Configuration
TRAEFIK_LOG_DASHBOARD_GEOIP_ENABLED=true                    # Enable GeoIP
TRAEFIK_LOG_DASHBOARD_GEOIP_CITY_DB=/geoip/GeoLite2-City.mmdb       # City DB path
TRAEFIK_LOG_DASHBOARD_GEOIP_COUNTRY_DB=/geoip/GeoLite2-Country.mmdb # Country DB path

Dashboard Environment Variables

# Agent Connection
AGENT_API_URL=http://traefik-agent:5000      # Agent API endpoint
AGENT_API_TOKEN=your_token                    # Authentication token

# Application
NODE_ENV=production                           # production or development
PORT=3000                                     # Dashboard port

Traefik Configuration

Configure Traefik to output JSON logs:

traefik.yml:

accessLog:
  filePath: "/var/log/traefik/access.log"
  format: json
  fields:
    defaultMode: keep
    headers:
      defaultMode: keep

Or with CLI:

--accesslog=true
--accesslog.filepath=/var/log/traefik/access.log
--accesslog.format=json

Performance

Benchmarks

Component	Metric	Performance
Agent	Log parsing	100,000+ lines/second
	Memory usage	~50MB per 1M entries
	API response time	<50ms average
	CPU usage	<5% during normal operation
Dashboard	Data points	10,000+ smoothly
	Update latency	<10ms UI refresh
	Memory usage	~100MB in browser
CLI	UI refresh	<10ms
	CPU usage	<5%

Optimization Tips

For Large Log Files:

Use incremental reading with position tracking
Enable Gzip compression on log files
Rotate logs frequently
Use the lines parameter to limit response size

For High Traffic:

Increase refresh interval
Deploy multiple agent instances
Use reverse proxy caching
Enable log sampling in Traefik

Memory Management:

Agent uses bounded memory buffers
Position tracking prevents re-reading old logs
Go garbage collection tuned for low latency

Troubleshooting

Common Issues

1. Dashboard Shows "Connection Error"

Symptoms:

Red connection error banner
No data displayed

Solutions:

# Check agent is running
docker ps | grep traefik-agent

# Check agent logs
docker logs traefik-log-dashboard-agent

# Verify agent is accessible
curl http://localhost:5000/api/logs/status

# Check authentication token matches
echo $AGENT_API_TOKEN

2. GeoIP Not Working

Symptoms:

Geographic cards show "No data"
Countries show as empty

Solutions:

# Verify databases exist
ls -lh ./data/geoip/

# Check agent logs for GeoIP errors
docker logs traefik-log-dashboard-agent | grep GeoIP

# Verify environment variables
docker exec traefik-agent env | grep GEOIP

# Test GeoIP lookup
curl -H "Authorization: Bearer token" \
  "http://localhost:5000/api/location/status"

3. No Logs Appearing

Symptoms:

Dashboard shows zero requests
All cards empty

Solutions:

# Verify log file path is correct
docker exec traefik-agent ls -lh /logs/

# Check log file permissions
docker exec traefik-agent cat /logs/access.log

# Verify log format matches configuration
head /path/to/traefik/access.log

# Check Traefik is generating logs
tail -f /path/to/traefik/access.log

4. High Memory Usage

Symptoms:

Agent consuming excessive memory
Dashboard slow or unresponsive

Solutions:

# Reduce lines per request
AGENT_API_URL/api/logs/access?lines=100

# Enable log rotation in Traefik
# Reduce refresh interval in dashboard
# Clear browser cache

# Check for log file issues
du -sh /path/to/traefik/logs/*

5. Authentication Failed

Symptoms:

401 Unauthorized errors
Cannot access API

Solutions:

# Verify token is set
echo $TRAEFIK_LOG_DASHBOARD_AUTH_TOKEN

# Test with curl
curl -H "Authorization: Bearer your_token" \
  http://localhost:5000/api/logs/status

# Check dashboard environment
docker exec traefik-dashboard env | grep TOKEN

# Restart services with correct token
docker-compose restart

Getting Help

If you're still experiencing issues:

Check Logs:
```
docker-compose logs -f
```
Enable Debug Mode:
```
environment:
  - LOG_LEVEL=debug
```
Join Discord:
- https://discord.gg/HDCt9MjyMJ
Open GitHub Issue:
- https://github.com/hhftechnology/traefik-log-dashboard/issues
- Include logs and configuration

Additional Resources

Agent Documentation: ./agent/README.md
Dashboard Documentation: ./dashboard/README.md
CLI Documentation: ./cli/README.md
API Reference: ./docs/API.md
Architecture Guide: ./docs/ARCHITECTURE.md

Contributing

Contributions are welcome! Please read our Contributing Guide.

Fork the repository
Create a feature branch (git checkout -b feature/amazing-feature)
Commit your changes (git commit -m 'Add amazing feature')
Push to the branch (git push origin feature/amazing-feature)
Open a Pull Request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

Traefik - Excellent cloud-native reverse proxy
Next.js - Powerful React framework
Chart.js - Beautiful charts
D3.js - Data visualization library
MaxMind - GeoIP database provider
Bubble Tea - TUI framework

Made with ❤️ for the Traefik community

⭐ Star this repo if you find it helpful!

GitHub • Discord • Issues

Name		Name	Last commit message	Last commit date
Latest commit History 246 Commits
.github/workflows		.github/workflows
agent		agent
cli		cli
dashboard		dashboard
docs		docs
LICENSE		LICENSE
README.md		README.md
docker-compose.yml		docker-compose.yml

License

hhftechnology/traefik-log-dashboard

Folders and files

Latest commit

History

Repository files navigation

Traefik Log Dashboard

Table of Contents

MIGRATION GUIDE from V1 to V2: ./docs/MigrationV1toV2.md

Overview

Architecture

Multi-Agent Architecture

Component Breakdown

Features

Core Features

Quick Start

Using Docker Compose (Recommended)

Docker Compose Configuration

Multi-Agent Setup

Adding Multiple Agents

1. Deploy Multiple Agents

2. Configure Agents in Dashboard

3. Switch Between Agents

GeoIP Database Setup

Step 1: Download GeoLite2 Databases

Step 2: Configure Agent

Step 3: Mount Volume

Step 4: Verify GeoIP Status

GeoIP Features

Updating GeoIP Databases

Dashboard Cards Explained

1. Request Metrics Card

2. Response Time Card

3. Status Codes Card

4. Status Code Distribution Card

5. Request Timeline Card

6. Top Routes Card

7. Backend Services Card

8. Routers Card

9. Top Client IPs Card

10. Top Request Hosts Card

11. Top Request Addresses Card

12. User Agents Card

13. Geographic Distribution Card

14. Interactive Geographic Map Card

15. Recent Errors Card

16. System Resources Cards (CPU, Memory, Disk)

17. Recent Logs Table

Filter Logs & API Usage

API Endpoints

1. Get Access Logs

2. Get Error Logs (4xx/5xx only)

3. Get Status Distribution

4. Get System Resources

5. Get Log File Sizes

Time Period Formats

Status Code Filtering

Incremental Log Reading

Configuration

Agent Environment Variables

Dashboard Environment Variables

Traefik Configuration

Performance

Benchmarks

Optimization Tips

Troubleshooting

Common Issues

1. Dashboard Shows "Connection Error"

2. GeoIP Not Working

3. No Logs Appearing

4. High Memory Usage

5. Authentication Failed

Getting Help

Additional Resources

Contributing

License

Acknowledgments

About

Topics

Resources

Packages