Bug 48522 – Make rsyslog message discard threshold configurable via UCR

Bug 48522 - Make rsyslog message discard threshold configurable via UCR


Summary:	Make rsyslog message discard threshold configurable via UCR

Status:	RESOLVED DUPLICATE of bug 48288

Product:	UCS
Classification:	Unclassified
Component:	UCR
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2019-01-23 12:41 CET by Valentin Heidelberger
Modified:	2019-01-23 14:48 CET (History)
CC List:	3 users (show)

See Also:	48508
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	5: Blocking further progress on the daily work
User Pain:	0.057
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2019012221001088, 2018112921000568
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Valentin Heidelberger

2019-01-23 12:41:13 CET

A customer needed to configure a threshold for rsyslog because they log a LOT and their remote log server was not reachable. This resulted in rsyslog taking up over 50% of the RAM and killed processes.
They should be able to this via UCR

Comment 3 Arvid Requate

2019-01-23 14:48:12 CET

As statet at Bug 48288, AFAIK the customer has special includes in /etc/rsyslog.d/*.conf , so we would need to at least know, if our idea of fixing this would help in their situation.

*** This bug has been marked as a duplicate of bug 48288 ***