Source string Source string

41/10000 · 41
English
Background Timeout and Concurrent Process Settings
Report Generation Timeout
The maximum amount of time Cacti's Reports Generation script can run without generating a timeout error and being killed.
%s Minute
Data Source Statistics Timeout
The maximum amount of time Cacti's Data Source Statistics script can run without generating a timeout error and being killed.
RRDChecker Timeout
The maximum amount of time Cacti's RRDfile Check script can run without generating a timeout error and being killed.
%s Hour
Poller Commands Timeout
The maximum amount of time Cacti's Background Commands script can run without generating a timeout error and being killed. This script will perform tasks such as re-indexing Devices and pruning devices from Remote Data Collectors.
Poller Command Concurrent Processes
The number of concurrent Poller Command processes. The will be at most one concurrent command per host within the Poller Command pool.
1 Process
%d Processes
Maintenance Background Generation Timeout
The maximum amount of time a Cacti's Maintenance script can run without generating a timeout error and being killed.
Spikekill Background Generation Timeout
The maximum amount of time a Cacti's Spikekill script can run without generating a timeout error and being killed.
Data Collector Defaults
These settings are maintained at the Data Collector level. The values here are only defaults used when first creating a Data Collector.
1h count warning threshold
When this count of guarded ratio (below) is reached in one hour, warning will be written to log and email will be send. 0 = disable.
1 hour guarded poller ratio run/max
Define guarded ratio poller run/max time (in percent).
24 hours guarded poller ratio run/max
Define guarded average ratio poller run/max time (in percent). When it is reached, warning will be written to log and email will be send. 0 = disable
Data Collector Processes
The default number of concurrent processes to execute per Data Collector. NOTE: Starting from Cacti 1.2, this setting is maintained in the Data Collector. Moving forward, this value is only a preset for the Data Collector. Using a higher number when using cmd.php will improve performance. Performance improvements in Spine are best resolved with the threads parameter. When using Spine, we recommend a lower number and leveraging threads instead. When using cmd.php, use no more than 2x the number of CPU cores.
Spine Specific Execution Parameters
How would you like Spine output errors logged? The options are: 'Detailed' which is similar to cmd.php logging; 'Summary' which provides the number of output errors per Device; and 'None', which does not provide error counts.
Component Translation Difference to current string
This translation Propagated Read only Cacti/core
The following string has the same context and source.
Propagated Read only Cacti/core (v1.2.x)

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

String information

Flags
read-only
Source string location
include/global_settings.php:1545
String age
3 years ago
Source string age
3 years ago
Translation file
locales/po/cacti.pot, string 2725