sub-faq

rsyslog statistic counter plugin imudp

Plugin – imudp This plugin maintains statistics for each listener and for each worker thread. The listener statistic is named starting with “imudp”, followed followed by the listener IP, a colon and port in parenthesis. For example, the counter for a listener on port 514 (on all IPs) with no set name is called “imudp(*:514)”. […]

rsyslog statistic counter plugin imtcp

Plugin – imtcp This plugin maintains statistics for each listener. The statistic is named after the given input name (or “imtcp” if none is configured), followed by the listener port in parenthesis. For example, the counter for a listener on port 514 with no set name is called “imtcp(514)”. The following properties are maintained for […]

rsyslog statistic counter plugin imptcp

Plugin – imptcp This plugin maintains statistics for each listener. The statistic is named “imtcp” , followed by the bound address, listener port and IP version in parenthesis. For example, the counter for a listener on port 514, bound to all interfaces and listening on IPv6 is called “imptcp(*/514/IPv6)”. The following properties are maintained for […]

rsyslog statistic counter plugin impstats

Plugin – impstats (rsyslog 7.5.3+) The impstats plugin gathers some internal statistics. They have different names depending on the actual statistics. Obviously, they do not relate to the plugin itself but rather to a broader object – most notably the rsyslog process itself. The “resource-usage” counter maintains process statistics. They base on the getrusage() system […]

rsyslog statistic counter plugin omfile

Plugin – omfile (rsyslog 7.3.6+) This plugin maintains statistics for each dynafile cache. Dynafile cache performance is critical for overall system performance, so reviewing these counters on a busy system (especially one experiencing performance problems) is advisable. The statistic is named “dynafile cache”, followed by the template name used for this dynafile action. The following […]

rsyslog statistic counter plugin imrelp

Plugin – imrelp This plugin maintains statistics for each listener. The statistic by default is named “imrelp” , followed by the listener port in parenthesis. For  example, the counter for a listener on port 514 is called “imprelp(514)”. If the input is given a name, that input name is used instead of “imrelp”. This counter […]

rsyslog statistic counter Actions

Actions processed – total number of messages processed by this action. This includes those messages that failed actual execution (so it is a total count of messages ever seen, but not necessarily successfully processed) failed – total number of messages that failed during processing. These are actually lost if they have not been processed by […]

rsyslog statistic counter plugin omelasticsearch

Plugin – omelasticsearch This plugin maintains global statistics, which accumulate all action instances. The statistic is named “omelasticsearch”. Parameters are: submitted – number of messages submitted for processing (with both success and error result) fail.httprequests – the number of times a http request failed. Note that a single http request may be used to submit […]

Changing the settings

Go back to What is imuxsock? Before we can begin testing on how rate limiting works, we should change the default settings. By default, rate limiting will only work, if a process sends more than 200 messages in 5 seconds.To have some influence on the rate limiting we have basically two options: $SystemLogRateLimitInterval [number] $SystemLogRateLimitBurst […]

Scroll to top