Bug 1450627

Summary:	[RFE] Enhance journald to rate-limit in a graceful manner, similar to what rsyslog does
Product:	Red Hat Enterprise Linux 7	Reporter:	Peter Portante <pportant>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-daemons
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	7.5-Alt	CC:	nhosoi, pdwyer, systemd-maint-list
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-15 07:35:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Peter Portante 2017-05-14 04:48:43 UTC

Today, when a given service runs up against its rate-limit boundary, all messages are dropped.

It would be beneficial to allow a two-tier system, where the first tier rate-limits messages at or below a certain priority, dropping those messages below that priority.  Only when the rate-limit hits the second tier would all other messages be dropped.

Additionally, it would be useful to apply a behavior where for stdout/stderr, those byte stream are stalled until the next period instead of having those messages dropped.

Comment 6 RHEL Program Management 2021-01-15 07:35:57 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.