Skip to main content

Overview

This guide walks you through a complete LogFleet deployment:
  1. Cloud Platform - API server and database
  2. Edge Agent - Log collection at edge locations
  3. Dashboard - Visualizing logs and metrics
By the end, you’ll have logs flowing from edge → cloud → dashboard.

Prerequisites

  • Docker and Docker Compose installed
  • curl for API testing
  • 5 minutes of your time

Step 1: Start the Cloud Platform

For this guide, we’ll use the production cloud. If you need to run locally, see Self-Hosted Setup below.

Create Your Account

Save the token from the response:

Create an API Key for Edge Agents

Save the raw_key:
The raw API key is only shown once! Save it securely.

Step 2: Deploy the Edge Agent

The edge agent collects logs at your edge location and connects to the cloud.
This exposes:
  • Port 9880: HTTP JSON log input
  • Port 514: Syslog UDP input

Using Docker Compose

For production deployments with local Loki storage:

Verify Agent Registration

Check that your agent appears in the cloud:
Expected output:

Step 3: Send Test Logs

Send logs to your edge agent:

JSON Format (HTTP)

Multiple Logs (Batch)

Syslog Format (UDP)

Step 4: View Logs in Dashboard

Option A: Web Dashboard

  1. Go to app.logfleet.io
  2. Log in with your credentials
  3. Click on your agent (e.g., “store-001”)
  4. Click Sample Logs to fetch recent logs

Option B: API

Fetch logs via the API:

Option C: Real-Time Streaming

Start a streaming session:
Use a WebSocket client (like wscat) to connect and receive real-time logs.

Step 5: Verify Everything Works

Run this checklist to confirm your setup:

Self-Hosted Setup

To run LogFleet entirely on your own infrastructure:

Clone the Repositories

Start Cloud Platform

This starts:
  • API Server on port 8080
  • PostgreSQL database
  • Loki for log storage

Start Edge Agent

Configure Local URLs

Troubleshooting

Agent Not Connecting

  1. Check API key: Ensure API_KEY is set correctly
  2. Check URL: CLOUD_URL should include protocol (https://)
  3. Check network: Agent needs outbound HTTPS access

No Logs Appearing

  1. Check agent is running: docker ps | grep logfleet
  2. Check logs are being received: docker logs logfleet-agent
  3. Send a test log: curl -X POST http://localhost:9880 -d '{"test": true}'

WebSocket Disconnects

  • Default idle timeout is 5 minutes
  • Increase timeout_seconds when starting stream
  • Check for network interruptions

What’s Next?

Custom Metrics

Extract metrics from your logs

Vector Configuration

Customize log collection

Log Streaming

Real-time log access