// blog.index
LogForge field notes
Practical guides for Docker monitoring, remote hosts, alert routing, and the parts of self-hosting that usually hide in the margins.
Monitoring ECS Fargate With LogForge, Without Pretending There Is A Docker Host
Understand why the EC2 host-agent guide does not apply to pure Fargate, and where AWS task log drivers, FireLens, and Managed Instances fit instead.
Read article
Monitoring ECS On EC2 With LogForge, Without Losing The Host Boundary
Run one LogForge agent per ECS EC2 container instance, keep agents outside application task lifecycles, and avoid reusing enrollment identities across hosts.
Read article
Monitoring Plain VPS Docker Hosts With LogForge, Without Growing a Platform Team.
Run one stable LogForge Central, enroll each rented Docker host as a remote agent, and keep provider firewalls focused on Central reachability instead of opening every box.
Read article
Monitoring Kamal Deployments With LogForge, Without Inventing a Tiny Platform Team.
Run one stable LogForge Central, install one remote agent on each Kamal-managed Docker host, and keep the dashboard private while agents phone home over mTLS.
Read article
Monitoring EC2 With LogForge, Without Turning Your Afternoon Into an IAM Side Quest
Run LogForge Central on a machine you control, enroll EC2 Docker hosts as agents, and keep inbound security group rules focused on Central instead of every instance.
Read article