openSUSE systemd‑journald rate limiting and alert noise

openSUSE systemd‑journald rate limiting suppresses repeated log events that trigger desktop alerts

26.2K reputation · 20 Jan 2025, 04:37 UTC

103.4K views0

The default systemd‑journald settings in openSUSE apply a RateLimitInterval of 30 seconds and a RateLimitBurst of 1000 messages, which can drop log lines that monitoring tools or services such as YaST2‑alert‑mail rely on for state‑change notifications.

Administrators need to decide whether to increase the burst or interval to preserve useful alerts while avoiding excess noise and disk usage from verbose daemons.

What RateLimitBurst value provides a good trade‑off for desktop installations?
How might adjusted limits affect the timeliness of YaST2‑alert‑mail notifications?
Should openSUSE maintain separate default limits for desktop versus server profiles?

3,693 following

Keep exploring this topic

IPv6 Firewall Options Visibility in YaST on OpenSUSE Leap 15.6

OpenSUSE Leap 15.6 YaST firewall shows an IPv6 checkbox even when the kernel lacks IPv6 support. Should YaST hide or disable this option, and what diagnostic feedback is needed when IPv6 rules cannot be applied?

OpenSUSE Leap 15.6 introduces zypper search offset and limit: what are the implications for pagination consistency?

OpenSUSE Leap 15.6 added offset/limit flags to zypper search for bounding and paginating large package datasets. The feature’s experimental nature raises questions about consistency, performance, and future cursor‑based support.

SDL_Init failed: Could not initialize SDL error when initializing video subsystem

How to handle SDL's persistent error string "SDL_Init failed: Could not initialize SDL" so alerting systems avoid duplicate notifications, and what design choices remain unresolved in SDL’s error handling?

RSpec alert throttling to suppress duplicate failure messages

Configure RSpec to limit duplicate alert output and reduce notification noise without writing a custom formatter.

openSUSE systemd‑journald rate limiting suppresses repeated log events that trigger desktop alerts

0 answers

Your perspective belongs here.

0 question comments