https://www.centrallogging.com/ Recent content on Self-Hosted Centralized Logging Made Easy Hugo -- gohugo.io en-US Thu, 11 Jun 2026 22:44:17 +0000 https://www.centrallogging.com/docs/alerting/ Sun, 01 Dec 2024 09:00:00 -0700 https://www.centrallogging.com/docs/alerting/ Central Logging can monitor your logs and send alerts when specific conditions are met. You define alert rules using SQL or FTS queries, and notifications are delivered through configured notification channels. Alert Rules An alert rule defines what to look for and when to fire. You can create alert rules from the Alerts page or directly from the search page (the query and source are pre-filled). Each alert rule has: https://www.centrallogging.com/docs/configuration/ Sat, 09 Nov 2024 09:00:00 -0700 https://www.centrallogging.com/docs/configuration/ There is currently very little configuration required to use Central Logging. Most configuration is done through the web interface. However, there are a few things that can be configured via environment variables and CLI flags. CLI Flags -v — Display the application version and build date -install — Install Central Logging as a systemd service (requires sudo) -update — Download and install the latest version of the binary Environment Variables PORT — HTTP listen address and port. https://www.centrallogging.com/docs/website-monitoring/ Sat, 05 Oct 2024 09:00:00 -0700 https://www.centrallogging.com/docs/website-monitoring/ Central Logging can monitor your websites and web services for uptime, performance, and content changes. Checks run every minute and alerts are sent through your configured notification channels. Setting Up a Monitor From the Website Monitors page, create a new monitor with: Name — A descriptive name for the monitor URL — The URL to check (HTTP or HTTPS) Keyword — Optional text to search for in the response body Alert When — If a keyword is set, choose to alert when the keyword exists or does not exist in the response Case Sensitive — Whether keyword matching is case-sensitive (default: case-insensitive) What Gets Checked Each check records: https://www.centrallogging.com/blog/introducing-central-logging/ Sun, 21 Jul 2024 09:54:27 -0800 https://www.centrallogging.com/blog/introducing-central-logging/ Central Logging is a new product that I developed out of frustration with the pricing of good SaaS based logging solutions and the complexity of running and maintaining open source solutions. The SaaS solutions start you off with what looks like a generous free tier but it quickly becomes expensive to do basic alerting. They often have a bunch of hidden fees and everything is an add-on. Open source is great and covers pretty much all logging and metrics needs. https://www.centrallogging.com/docs/metrics/ Wed, 27 Mar 2024 09:00:00 -0700 https://www.centrallogging.com/docs/metrics/ Central Logging can track your application, server, or custom metrics. It currently supports Counter and Gauge metrics scraped from the Prometheus metrics text format. Set up a metric source Click Metric Sources and create a new source by specifying the Prometheus URL to scrape with optional basic auth info: Metrics View available metrics from the Metrics page. Central Logging uses the same plotting library as Grafana. You get critical metrics features without the complexity of setting up a Prometheus/Grafana stack. https://www.centrallogging.com/docs/host-monitoring/ Tue, 19 Mar 2024 09:00:00 -0700 https://www.centrallogging.com/docs/host-monitoring/ Central Logging can track the health of your servers. The CL Agent periodically sends system information to Central Logging, and you get alerted if a host stops checking in. How It Works When the CL Agent runs on a server, it sends periodic check-ins to Central Logging with system information. Central Logging tracks when each host was last seen and alerts you if a host goes missing. Host Information Each host check-in reports: https://www.centrallogging.com/guides/sending-journalctl-logs-to-centralized-logging-system/ Thu, 22 Feb 2024 09:54:27 -0800 https://www.centrallogging.com/guides/sending-journalctl-logs-to-centralized-logging-system/ Introduction So you have a Linux system and you want to export your logs to a centralized logging system. There is a good chance your Linux distribution is running systemd which comes with journaltctl. journalctl is a command-line tool provided by systemd, which is the system and service manager for Linux operating systems. It is used to query and display messages from the systemd journal. It allows you to view logs from various components of the system, including the kernel, system services, and applications, all in one place. https://www.centrallogging.com/docs/updating/ Tue, 28 Feb 2023 09:00:00 -0700 https://www.centrallogging.com/docs/updating/ Central Logging is just a single binary. To update you can grab a new copy at: https://www.centrallogging.com/#download unzip it, replace the old binary, and restart the service. Or it can self-update with: Linux ./centrallogging-linux-amd64 -update sudo systemctl restart centrallogging OpenBSD ./centrallogging-openbsd-amd64 -update doas rcctl restart syslogd https://www.centrallogging.com/docs/cl-agent/ Sun, 15 Jan 2023 09:00:00 -0700 https://www.centrallogging.com/docs/cl-agent/ If you run your own servers and want to send all logs from these servers to central logging you can use our central logging agent with binary name clagent. CL agent will periodically send all system logs upstream to your central logging instance. On Linux it exports logs from systemd using the journalctl cli. On OpenBSD it exports logs using syslogd. Download CL Agent clagent-linux-amd64 clagent-linux-arm clagent-openbsd-amd64 Or grab it with wget Click Copy, paste into your shell, and run: https://www.centrallogging.com/docs/cron-monitoring/ Sun, 15 Jan 2023 09:00:00 -0700 https://www.centrallogging.com/docs/cron-monitoring/ Ever setup a cron job that worked so well that you set it up and forgot about it only to find out it stopped working after awhile and you had no idea? Central Logging can alert you when your cron or background jobs fail or stop reporting in, so there are no more silent failures. To monitor any job send an HTTP request with API key and job name. Ex: https://www.centrallogging.com/docs/deploy/ Sun, 15 Jan 2023 09:00:00 -0700 https://www.centrallogging.com/docs/deploy/ Central Logging is just a single binary executable that serves an HTTPS server. It will automatically handle TLS/HTTPS for you using Let’s Encrypt. This makes setting up the service easy. Just copy the file to your server and execute. System Requirements We recommend at least 1GB of ram; however, it will depend on the size of your logs. 1GB of ram works well for 15GB of logs with 15 day retention. https://www.centrallogging.com/docs/introduction/ Sun, 15 Jan 2023 09:00:00 -0700 https://www.centrallogging.com/docs/introduction/ Central Logging is a self-hosted centralized logging and monitoring system that is designed to be low maintenance and easy to deploy. It is distributed as a single binary that serves an HTTPS web interface and API. Who is it for? Central Logging can handle all logging and monitoring tasks required by most small-businesses and projects. We are currently targeting to support retaining less than a few terabytes of logs. There are no hard limits but things may not operate as smooth as they should if you go over several TB. https://www.centrallogging.com/docs/querying-logs/ Sun, 15 Jan 2023 09:00:00 -0700 https://www.centrallogging.com/docs/querying-logs/ There are two major ways to search for logs. You can use SQL syntax or full text search. You can toggle between the two modes from the search page. SQL Here is an example SQL query selecting specific JSON fields: SELECT "timestamp", json_extract(logs.msg, '$.Data.method') AS method, json_extract(logs.msg, '$.Data.request_uri') AS request_uri, json_extract(logs.msg, '$.Data.user_agent') AS user_agent, json_extract(logs.msg, '$.Data.addr') AS addr FROM logs WHERE json_valid(msg) AND request_uri LIKE '%/account%' ORDER BY "timestamp" DESC LIMIT 2001; SQL queries support syntax highlighting and a pretty-print button to format your query. https://www.centrallogging.com/docs/release-notes/ Sun, 15 Jan 2023 09:00:00 -0700 https://www.centrallogging.com/docs/release-notes/ NOTE: Updates are happening daily but these notes are updated once every two weeks. 2026-04-17 Refreshes the home page: shows a welcome/onboarding view with tabbed code samples (curl, Python, Node.js, Go, file upload) and copy-to-clipboard buttons when you haven’t created any sources yet, otherwise shows a dashboard with 24h log volume tiles, top sources by volume, recent alerts, and quick actions 2026-04-16 Refreshes the sources list UI: health indicator dot (fresh/stale/silent), last-log-received timestamp, relative usage bar, name filter box, a friendly empty state, and inline tail/edit/delete actions Refreshes the source edit page UI: grouped sections (settings, transform script, stats, send logs), tabbed ingest examples, stats cards, and a dedicated danger zone for deletion Fixes Transform script editor colors in dark mode Fixes log count and used bytes on the sources list not refreshing when new logs arrive (stats cache now invalidates on create/delete and expires after 30 seconds instead of 15 minutes) Fixes retention days not saving when editing an existing log source 2026-04-15 https://www.centrallogging.com/docs/sending-logs/ Sun, 15 Jan 2023 09:00:00 -0700 https://www.centrallogging.com/docs/sending-logs/ You can send logs through a simple HTTP(s) API or send all server logs with our CL Agent Sending logs through HTTP(s) API Send a single simple log message: curl -X POST http://localhost:8080/api/v1/log/{log-source-token} -d "this is a log entry" Send structured logs in JSON: curl -X POST http://localhost:8080/api/v1/log/{log-source-token} -d '{"level": "error", "msg": "something went wrong"}' Send a bunch of logs from a file: curl -X POST http://localhost:8080/api/v1/ingest_logs/{log-source-token} -d @mylogs.txt This will make a log entry for every line of text sent separated by new line. https://www.centrallogging.com/docs/useful-log-queries/ Sun, 15 Jan 2023 09:00:00 -0700 https://www.centrallogging.com/docs/useful-log-queries/ Log count from various sources select source, count(source) as log_count from logs group by source order by log_count desc; Count of all logs in system select count(*) from logs; Successful SSH Logins select json_extract(logs.msg, '$.MESSAGE') as message, timestamp, source, json_extract(logs.msg, '$.SYSLOG_TIMESTAMP') as ts, json_extract(logs.msg, '$.SYSLOG_IDENTIFIER') as syslog_id from logs where json_valid(msg) and syslog_id='sshd' and message like '%Accepted publickey%' order by timestamp desc; When did I last update my Linux servers? select id, timestamp, source, json_extract(logs. https://www.centrallogging.com/privacy/ Mon, 01 Jan 0001 00:00:00 +0000 https://www.centrallogging.com/privacy/ Last updated: November 1st, 2023 centrallogging.com is operated by Eligian Labs LLC. This Privacy Policy describes how Eligian (the “Site,” “we,” “us,” or “our”) collects, uses, and discloses your personal information when you visit, use our services, or make a purchase from centrallogging.com (the “Site”) or otherwise communicate with us (collectively, the “Services”). For purposes of this Privacy Policy, “you” and “your” means you as the user of the Services, whether you are a customer, website visitor, or another individual whose information we have collected pursuant to this Privacy Policy. https://www.centrallogging.com/terms/ Mon, 01 Jan 0001 00:00:00 +0000 https://www.centrallogging.com/terms/ We’re committed to providing you with the best experience possible. centrallogging.com is operated by Eligian Labs LLC. OVERVIEW This website is operated by Eligian. Throughout the site, the terms “we”, “us” and “our” refer to Eligian. Eligian offers this website, including all information, tools, and services available from this site to you, the user, conditioned upon your acceptance of all terms, conditions, policies, and notices stated here. By visiting our site and/or purchasing something from us, you engage in our “Service” and agree to be bound by the following terms and conditions (“Terms of Service,” “Terms”), including those additional terms and conditions and policies referenced herein and/or available by hyperlink.