Uptime monitoring & observability
Monitor checks, alerts & logs in one place. Scheduled health checks for websites, APIs, TCP ports, and game servers, with email alerts when things fail, workspaces for your team, and lightweight log ingestion via API.
Built for operators who self-host. Straightforward monitoring for VPS, homelab, and game communities, without enterprise bloat.
Everything you need to know when infrastructure misbehaves, before users tell you.
HTTP with custom expectations, TCP reachability, Minecraft Server List Ping, RCON, and direct game-server probes, with no third-party game-status APIs.
Run checks every few seconds to hours, trigger on-demand runs, and review per-check history with status, latency, and errors.
Get notified when monitors fail, or fire alerts from CI, cron, and scripts via API, with a full alert call history for auditing.
Statuses: up, down, and incorrect when a service responds but fails your rules. Multiple recipients per failure alert.
Organise checks, monitoring clients, alerts, and log groups. Invite teammates with owner, manager, or read-only roles.
API-triggered alerts for deployments and pipelines. Ingest structured log lines per workspace with scoped API keys.
Game-aware probes and strict HTTP expectations, not just “is the port open?”
| Type | What it does |
|---|---|
| Website / HTTP | Custom status codes, body content, and response rules |
| TCP port | Reachability on a specific port |
| Game server | Direct probes (Steam A2S INFO, TCP fallback) for Valheim, ARK, and similar |
| Minecraft status | Native Server List Ping; optional DNS SRV (_minecraft._tcp) when port is omitted |
| Minecraft RCON | Authenticate and run RCON commands to verify the server is truly responsive |
Wire Lobster Ping into Jenkins, deployment scripts, and your apps. Workspace-scoped keys (lp_live_…) with permission scopes for alerts and logs.
POST /api/alerts/trigger
{
"api_key": "lp_live_...",
"alert_name": "Deployment failure",
"message": "Build 123 failed",
"alert_content": "Optional detail for the email"
}POST /api/logs/ingest
{
"api_key": "lp_live_...",
"log_group_name": "Production application logs",
"message": "User sign-in failed",
"level": "error",
"source": "auth-service"
}
Python package lobster_ping for one-line alert triggers from scripts.
Explore API docs
·
Public health endpoint
Register a monitoring client in the dashboard and assign checks to it. The lightweight
lobster_client agent polls for due work, runs checks locally, and reports results, ideal for private LANs,
homelab, same-region latency, and services behind a firewall.
lp_client_…), separate from API keysRemote monitoring agent
Cloud-scheduled checks and agent-assigned checks work side by side. Pick what fits each target.
Minecraft and dedicated game servers with native protocol probes, not generic HTTP-only tooling or external game-status APIs.
Checks, email alerts, and log ingestion under one workspace instead of three separate products.
Monitor internal services from inside your network with a small agent, not only from the vendor cloud.
VPS, homelab, self-hosted apps: monitoring without a heavy enterprise stack.
DevOps teams who want checks, alert automation, and lightweight logs in one dashboard.
Minecraft and game-server hosts who need probes that speak real game protocols.
lp_live_…) are workspace-scoped with permission scopes (e.g. Alerts, Logs). Client keys (lp_client_…) authenticate the monitoring agent only. They are separate credentials.Create a free account, add your first check, and get email alerts when something breaks.