2. Cacti
3. core
4. Japanese
5. Zen

5003 support.php:797
	English Time the background process started for a Cacti process. The start time may or may not be supported for various plugins.
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/1210 · 121 Needs editing
5005 support.php:803
	English Time the process last registered its status to the status tables.
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/650 · 65 Needs editing
5007 support.php:837
	English No Cacti or Plugin Background Processes Found
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/450 · 45 Needs editing
5013 support.php:919
	English Worst 20 failed/total polls ratio
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/330 · 33 Needs editing
5014 support.php:930
	English Failed/Total polls
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/180 · 18 Needs editing
5054 support.php:1584
	English MySQL/MariaDB Memory Statistics (Source: MySQL Tuner)
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/530 · 53 Needs editing
5056 support.php:1594
	English Reduce MySQL/MariaDB Memory to less than 80% of System Memory. Preserve additional Cache Memory for RRDfiles if the Database is on the same system as the RRDfiles. See Core and Client Totals below for explanation of calculation method.
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/2370 · 237 Needs editing
5058 support.php:1613
	English Reduce Total Core Memory
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/240 · 24 Needs editing
5059 support.php:1623 • support.php:1640 • support.php:1650 • support.php:1660
	English Calculation Formula
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/190 · 19 Needs editing
5060 support.php:1629 • support.php:1634 • support.php:1655
	English Max Connection Memory Possible
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/300 · 30 Needs editing
5061 support.php:1630
	English Reduce Total Client Memory
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/260 · 26 Needs editing
5081 templates_import.php:118
	English The Template Import Succeeded.
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/300 · 30 Needs editing
5085 templates_import.php:216
	English Import Files [ If Files are missing, locate and install before using ]
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/700 · 70 Needs editing
5088 templates_import.php:252
	English Import Templates [ None selected imports all, Check to import selectively ]
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/750 · 75 Needs editing
5093 templates_import.php:333
	English Some CDEF Items will not import due to an export error! Contact Template provider for an updated export.
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/1040 · 104 Needs editing
5233 user_admin.php:2124
	English < 1 Month Ago
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/130 · 13 Needs editing
5234 user_admin.php:2125
	English > 1 Month Ago
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/130 · 13 Needs editing
5289 user_domains.php:389
	English The "Distinguished Name" syntax, applicable for both OpenLDAP and Windows AD configurations, offers flexibility in defining user identity. For OpenLDAP, the format follows this structure: <i>"uid=&lt;username&gt;,ou=people,dc=domain,dc=local"</i>. Windows AD provides an alternative syntax: <i>"&lt;username&gt;@win2kdomain.local"</i>, commonly known as "userPrincipalName (UPN)". In this context, "&lt;username&gt;" represents the specific username provided during the login prompt. This is particularly pertinent when operating in "No Searching" mode, or "Require Group Membership" enabled.
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/5920 · 592 Needs editing
5296 user_domains.php:414
	English This refers to the specific attribute within the LDAP directory that holds the usernames of group members. It is crucial to ensure that the attribute value aligns with the configuration specified in the "Distinguished Name" or that the actual attribute value is searchable using the settings outlined in the "Distinguished Name".
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/3290 · 329 Needs editing
5389 utilities.php:47
	English The Poller Cache Rebuild Operation has been started in background
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/650 · 65 Needs editing