DEV Community

IndieSquadTools
IndieSquadTools

Posted on

Centralizing logs across servers or background workers often introduces unnecessary operational overhead

#webdev #programming

Centralizing logs across servers or background workers often introduces unnecessary operational overhead. Running dedicated search clusters like Elasticsearch requires significant memory and maintenance, while SaaS logging providers charge monthly rates that scale directly with data volume. For smaller deployments, these options are often disproportionate to the actual problem: finding recent error messages and getting notified when something breaks.

LogFloor is a lightweight, self-hosted log search and alerting tool. Purchased as source code for a $49 one-time fee, it runs entirely on your own infrastructure using SQLite for storage, eliminating managed database costs and recurring subscription fees.

Technical Overview

LogFloor operates around three core functions:

  • HTTP Ingestion: A single HTTP ingest endpoint accepts incoming log payloads from your applications or scripts.
  • Search: An interface allows querying stored logs using keyword filtering and specific time ranges.
  • Alerting: Threshold-based alert rules monitor log occurrences and fire an HTTP request to a user-configured webhook URL when triggered.

Because the underlying datastore is SQLite, all log data resides in a local database file, simplifying backup and operational requirements to standard file-system management.

Example Usage

To send logs to LogFloor, send an HTTP POST request to the ingestion endpoint from your application or a log-forwarding script:

curl -X POST http://localhost:8080/ingest \
  -H "Content-Type: application/json" \
  -d '{
    "timestamp": "2026-03-30T14:22:00Z",
    "level": "ERROR",
    "service": "auth-service",
    "message": "Database connection timeout during user authentication"
  }'
Enter fullscreen mode Exit fullscreen mode

You can then filter logs by selecting a time window and searching for keywords like "connection timeout".

If you want to receive notifications when database errors spike, you can set a threshold alert inside LogFloor. When the count of logs matching your search criteria exceeds your specified threshold within a set time frame, LogFloor executes a POST request to your designated webhook URL.

What It Does Not Do

LogFloor is designed strictly for simple log aggregation and basic alerting. It deliberately omits features found in larger logging infrastructure:

  • No managed cloud offering: You receive the source code and run it yourself; there is no hosted version or managed support.
  • No high-throughput distributed database: SQLite is not designed for massive horizontal scaling or continuous, multi-gigabyte-per-second write rates.
  • No native third-party alert channels: Alerting is strictly limited to sending a payload to a target webhook URL. Integrating with platforms like Slack, PagerDuty, or email requires a receiving endpoint that handles the webhook.
  • No built-in log parsing or transformation pipelines: LogFloor accepts input at its HTTP endpoint; it does not parse unstructured raw text logs, mutate fields, or run agent-based log collection natively. Pre-formatting must be handled before ingestion.

Get it here

Disclosure: I built this and it is a paid product.

Top comments (0)