Source string Source string

79/10000 · 79
English
RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) removed from RRD file
RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) adding to RRD file
Website does not have write access to %s, may be unable to create/update RRDs
(Custom)
Failed to open data file, poller may not have run yet
RRA Folder
Root
Unknown RRDtool Error
Attempting to Create Graph from Non-Template
Attempting to Create Graph from Removed Graph Template
Created: %s
ERROR: Whitelist Validation Failed. Check Data Input Method
Graph Not created for %s due to bad data
NOTE: Graph not added for Data Query %s and index %s due to Data Source verification failure
Your Start Date '%s' is before January 1993. Please pick a more recent Start Date.
Your End Date '%s' is before January 1993. Please pick a more recent End Date.
MySQL 5.6+ and MariaDB 10.0+ are great releases, and are very good versions to choose. Make sure you run the very latest release though which fixes a long standing low level networking issue that was causing spine many issues with reliability.
It is STRONGLY recommended that you enable InnoDB in any %s version greater than 5.5.3.
When using Cacti with languages other than English, it is important to use the utf8mb4_unicode_ci collation type as some characters take more than a single byte.
When using Cacti with languages other than English, it is important to use the utf8mb4 character set as some characters take more than a single byte.
It is recommended that you enable InnoDB in any %s version greater than 5.1.
Depending on the number of logins and use of spine data collector, %s will need many connections. The calculation for spine is: total_connections = total_processes * (total_threads + script_servers + 1), then you must leave headroom for user connections, which will change depending on the number of concurrent login accounts.
Keeping the table cache larger means less file open/close operations when using innodb_file_per_table.
With Remote polling capabilities, large amounts of data will be synced from the main server to the remote pollers. Therefore, keep this value at or above 16M.
If using the Cacti Performance Booster and choosing a memory storage engine, you have to be careful to flush your Performance Booster buffer before the system runs out of memory table space. This is done two ways, first reducing the size of your output column to just the right size. This column is in the tables poller_output, and poller_output_boost. The second thing you can do is allocate more memory to memory tables. We have arbitrarily chosen a recommended value of 10%% of system memory, but if you are using SSD disk drives, or have a smaller system, you may ignore this recommendation or choose a different storage engine. You may see the expected consumption of the Performance Booster tables under Console -> System Utilities -> View Boost Status.
When executing subqueries, having a larger temporary table size, keep those temporary tables in memory.
If this number is negative, reduce the innodb_buffer_pool_size until the join_buffer_size turns positive, but allocate approximately from between 25%-50% of memory to the innodb_buffer_pool_size if the database is hosted on the Cacti server, or upto 80% of the systems memory if the database is separate from the Cacti web server. However, try to not go below the default of 262,144. When performing joins, if they are below this size, they will be kept in memory and never written to a temporary file. As this is a per connection memory allocation, care must be taken not to increase it too high. The sum of the join_buffer_size + sort_buffer_size + read_buffer_size + read_rnd_buffer_size + thread_stack + binlog_cache_size + Core MySQL/MariaDB memory should be below 80% if the database is hosted on the Cacti web server and less if you intend to have very large RRDfiles or hundreds of thousands to millions long term.
If this number is negative, reduce the innodb_buffer_pool_size until the sort_buffer_size turns positive, but allocate approximately from between 25%-50% of memory to the innodb_buffer_pool_size if the database is hosted on the Cacti server, or upto 80% of the system memory if the database is separate from the Cacti web server. However, try to not go below the default setting of 2,097,152. A sort buffer performs sorts for some queries using ORDER BY or GROUP BY. Configuring sort_buffer_size decides how much memory will be allocated for sort queries. The sort_buffer_size may need to be adjusted from the default if the workload requires a significant number of sort queries. The sort_buffer_size is defined on a per-session variable. Use the same equation as that of the join_buffer_size to determine the per connection possible memory.
When using InnoDB storage it is important to keep your table spaces separate. This makes managing the tables simpler for long time users of %s. If you are running with this currently off, you can migrate to the per file storage by enabling the feature, and then running an alter statement on all InnoDB tables.
When using innodb_file_per_table, it is important to set the innodb_file_format to Barracuda. This setting will allow longer indexes important for certain Cacti tables.
If your tables have very large indexes, you must operate with the Barracuda innodb_file_format and the innodb_large_prefix equal to 1. Failure to do this may result in plugins that can not properly create tables.

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

String information

Flags
php-format, read-only
Source string location
lib/timespan_settings.php:141
String age
12 days ago
Source string age
12 days ago
Translation file
locales/po/cacti.pot, string 4299