Welcome to LogForge
Understand the server, Remote Agents and your accounts.
LogForge · Runs in your infrastructure
What you will set up
LogForge runs in your infrastructure:
- The LogForge server hosts the web application, stores logs and metrics, and manages alerts.
- A Remote Agent runs on a Docker host or Kubernetes cluster. It collects data from your applications and sends it to the server.
- A workload is an application container or a Kubernetes application and its containers. An environment groups systems you operate together.
Configuration and diagnostic output may use older names: Central means the LogForge server; Echo means a Remote Agent. Keep literal unicron commands, filenames and UNICRON_* settings unchanged.
Community includes one local Owner, connected agents, saved logs, container metrics, and alerts. Business adds people, teams, and delegated access. You can activate Business later without replacing local data.
Choose your installation
Both options run on your own infrastructure. On-premises means you host it yourself; it can have internet access or be air-gapped.
| Your network | Guide |
|---|---|
| The server has internet access | Install online |
| The server cannot reach the internet | Install air-gapped |
- Check the requirements and usage reporting before startup.
- Follow your chosen guide to configure addresses, storage, trusted HTTPS, and the local Owner account.
- Connect a Docker host, or a supported Kubernetes cluster.
- Monitor your first workload. Check saved logs and recent metric samples.
- Test notification delivery, then create your first alert.
Check: the web application opens, the Remote Agent is connected, and saved logs and metrics are queryable. Running containers alone do not establish this.
Keep the two accounts separate
| Account | What it does |
|---|---|
| LogForge website account | Purchases and license delivery |
| Local Owner | Operates your LogForge installation |
Website sign-in does not sign you in to your installation. Community needs no activation key. Follow Editions and activation when you need Business features, and People & Access to add people.
If something is missing
Check the time range, application output, and collection state using When data is missing. Preserve existing agents and data while investigating. Use Updates and recovery for version changes.