(Optional) Configuring the Suppression of the Log Processing Rate
Context
During the running of a device, if too many logs with the same log ID are generated, the information center is too busy processing these logs to process logs with other log IDs, which may even affect the running service. The information center monitors the traffic of logs with different log IDs. When the traffic of logs with a specific log ID repeatedly exceeds the threshold during the monitoring period, the information center suppresses the processing rate of these specified logs by processing only the conforming traffic and discarding the non-conforming traffic; when the traffic of logs with the specific log ID falls below the threshold and remains below the threshold for five monitoring periods, the suppression is removed.
Procedure
- Run system-view
The system view is displayed.
- Run info-center rate-limit threshold value [ byinfoid infoID | bymodule-alias modname alias ]
The maximum number of logs with the same log ID that the information center can process every second is set.
By default, the information center processes a maximum of 30 logs with the same log ID in every second. In certain application scenarios, by default, the information center needs to process more than 50 logs with the same log ID in every second. You can set thresholds for logs with different log IDs.
Generally, the default threshold is recommended.
- If the threshold is too low, some logs may be discarded.
- If the threshold is too high, the information center cannot identify the log ID under which too many logs are generated.
- Run info-center rate-limit global-threshold value
The total number of logs that the information center can process each second is set.
- Run info-center rate-limit monitor-period value
The period for the information center to limit the log processing rate is set.
- (Optional) Run info-center rate-limit except { byinfoid infoID | bymodule-alias modname alias }
Cancel the log processing rate limit for logs with the specified ID or module name.
If logs with the specified ID or module name will never be generated in a huge number, you can run this command to cancel the log processing rate limit for the logs. After this command is run, the configured log processing rate limit will not be effective for logs with the specified ID or module name.