Rs

rsyslog

Azure Observability 1 variation

rsyslog, a central log server that receives syslog from your other machines and files every message under the host and program that sent it.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Variations

This product is available in the build below. Open it for the operating system, cloud and version detail, or read its deployment guide.

ProductCloudOperating systemVersion
rsyslog on Ubuntu 24.04 LTS Azure Ubuntu 24.04 Standard View · Guide

Overview

rsyslog is the syslog daemon that ships as the system logger on most Linux distributions. Configured as a central log server it stops being a purely local tool: it listens for syslog from the rest of your estate over plain UDP and TCP, and over RELP, a transport that acknowledges every message at the application layer so nothing is lost across a restart or a dropped connection. Everything it receives is filed under the host and the program that sent it, one directory per host and one file per program, with the timestamp, the hostname the sender claimed and the address it genuinely came from on every line. Logs that live only on the machine that produced them are the logs you cannot read when that machine is the problem, and they are gone entirely when the instance is replaced, so a collector gives you one place to search, one retention policy, and a copy of the evidence that outlives the box.

Why the cloudimg image

A log receiver on a public network is found and abused quickly, so this image is not shipped open. The plaintext receivers accept traffic only from private networks, in a single commented file you narrow to your own subnet, and both are rate limited. The encrypted receiver demands a client certificate issued by a certificate authority your instance mints for itself on first boot, so nothing cryptographic is baked in and no two deployments share a trust root. The queue is bounded in memory and on disk, rotation and retention are configured rather than left to you, and the image carries a self test that sends a message over each transport from a simulated remote host and checks it landed correctly, then checks that an unauthorised sender and a forged certificate are both refused. Paired deployment guide and 24/7 support.

Common uses

  • Centralise logs from a fleet of Linux servers
  • Collect syslog from switches, firewalls and appliances
  • Retain an audit copy of logs that outlives the instance