RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Rate limiting does not work. See /CoreOS/rsyslog/Sanity/bz672182-RFE-Provide-rate-limiting-support http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2013/10/5211/521186/1091577/16524460/TESTOUT.log

Version-Release number of selected component (if applicable):
rsyslog-7.4.2-3.el7

How reproducible:
100%

Steps to Reproduce:
1. # cat >>/etc/rsyslog.conf <<EOF
\$SystemLogRateLimitInterval 5
\$SystemLogRateLimitBurst 10
local2.*   /var/log/local2
EOF
2. # service rsyslog restart
3. # (for i in `seq 1 80`; do
            echo "testnumber$i"
            sleep 0.1s
          done) | logger -p local2.error

Actual results:
80 messages logged

Expected results:
20 messages logged

Just a note:

In rsyslog 7.4.2, the messages aren't read from the system log socket. They are read directly from journal and therefore instead of

$SystemLogRateLimit*

you'll have to use

$ImjournalRateLimit*

Please, give this a try and perhaps close this as not-a-bug.

I have fixed the test so for RHEL-7 it uses ImjournalRateLimit and ti work correctly.