Project Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Checkmk 5% 38,755 276,040 1,711,821 38,754 13 4 0

Overview

Language code en_US
Aliased language codes us, enu
Text direction Left to right
Number of speakers 319,333,440
Plural: Default plural 3 translations
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10
Plural formula n != 1

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 40,953 321,802 1,998,968
Approved 0% 0 0% 0 0% 0
Waiting for review 5% 2,198 14% 45,762 14% 287,147
Translated 5% 2,198 14% 45,762 14% 287,147
Needs editing 1% 1 1% 5 1% 25
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 13 1% 137 1% 840
Strings with suggestions 1% 4 1% 37 1% 213
Untranslated strings 94% 38,754 85% 276,035 85% 1,711,796
Last 12 months Previous

Activity in last 12 months

0 changes 65,779 changes 0 changes 1,466 changes 17,996 changes 1,410 changes 83 changes 496 changes 438 changes 718 changes 111 changes 1,205 changes 300 changes 887 changes 817 changes 465 changes 740 changes 393 changes 1,577 changes 518 changes 1,451 changes 614 changes 3,585 changes 849 changes
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

321 k
Hosted words
40,953
Hosted strings
5%
Translated
3
Contributors
and previous 30 days

Trends of last 30 days

+1%
Hosted words
+100%
+1%
Hosted strings
+100%
+1%
Translated
+5%
—
Contributors
+100%
User avatar None

Resource update

Checkmk / dev — English (United States)

The "en_US.po" file was changed. 23 hours ago
User avatar None

Committed changes

Checkmk / dev — English (United States)

Committed changes yesterday
User avatar None

Committed changes

Checkmk / stable — English (United States)

Committed changes yesterday
User avatar silke.paintner

Translation changed

Checkmk / dev — English (United States)

This rule provides a simple way to add files to agent bakery packages without the need to write a bakery plugin.<br><i>Custom files</i> are organized in folders under <tt>{omd_root}/local/share/check_mk/agents/custom</tt>.<br>To add a set of custom files to the agent, please create a subfolder there with a meaningful name of your choice.<br>Added folders will be shown in this rule for activation.<br><br>Since the agent installation paths are customizable by other rules, the file structure below these sets doesn't resemble directly to the agent installation.<br>Instead, the structure is organized in <i>logical paths</i> that map to certain target folders in the final agent installation.<br>Files placed under a <i>logical path</i> will also apply the ownership and permissions based on the agent installation.<br>Ownership and permissions on the Checkmk site's file structure don't matter, with one exception: Executable flags on files will be preserved.<br><br>Overview of <i>logical paths</i> and their targets:<ul><li><tt>lib</tt>: Internal agent files (<tt>MK_LIBDIR</tt> on the host)</li><li><tt>bin</tt>: Executables (<tt>MK_BIN</tt> on the host)</li><li><tt>var</tt>: Runtime data (<tt>MK_VARDIR</tt> on the host)</li><li><tt>config</tt>: Configuration files (<tt>MK_CONFDIR</tt> on the host)</li><li><tt>lib/plugins</tt>: Agent plugins</li><li><tt>lib/local</tt>: Local checks</li></ul><b>Example</b>: Let's say you place the following files:<br><tt>{omd_root}/local/share/check_mk/agents/custom/myset/bin/some_executable</tt><br><tt>{omd_root}/local/share/check_mk/agents/custom/myset/lib/local/my_local_check</tt><br><tt>{omd_root}/local/share/check_mk/agents/custom/myset/some_file</tt><br>and activate <i>myset</i> in this rule.<br>Then, the following files will be deployed to target hosts when not further configuring agent paths:<br><tt>/usr/bin/some_executable</tt><br><tt>/usr/lib/check_mk_agent/local/my_local_check</tt><br><tt>/usr/lib/check_mk_agent/some_file</tt><br>When activating the single directory deployment in the <i>Customize agent package</i> ruleset:<br><tt>/opt/checkmk/agent/default/package/bin/some_executable</tt><br><tt>/opt/checkmk/agent/default/package/local/my_local_check</tt><br><tt>/opt/checkmk/agent/default/package/some_file</tt><br><br><b>Note</b>: When using the windows agent, all logical paths point to the same location - the agent installation dir.
This rule provides a simple way to add files to agent bakery packages without the need to write a bakery plug-in.<br><i>Custom files</i> are organized in folders under <tt>{omd_root}/local/share/check_mk/agents/custom</tt>.<br>To add a set of custom files to the agent, please create a subfolder there with a meaningful name of your choice.<br>Added folders will be shown in this rule for activation.<br><br>Since the agent installation paths are customizable by other rules, the file structure below these sets doesn't resemble directly to the agent installation.<br>Instead, the structure is organized in <i>logical paths</i> that map to certain target folders in the final agent installation.<br>Files placed under a <i>logical path</i> will also apply the ownership and permissions based on the agent installation.<br>Ownership and permissions on the Checkmk site's file structure don't matter, with one exception: Executable flags on files will be preserved.<br><br>Overview of <i>logical paths</i> and their targets:<ul><li><tt>lib</tt>: Internal agent files (<tt>MK_LIBDIR</tt> on the host)</li><li><tt>bin</tt>: Executables (<tt>MK_BIN</tt> on the host)</li><li><tt>var</tt>: Runtime data (<tt>MK_VARDIR</tt> on the host)</li><li><tt>config</tt>: Configuration files (<tt>MK_CONFDIR</tt> on the host)</li><li><tt>lib/plugins</tt>: Agent plug-ins</li><li><tt>lib/local</tt>: Local checks</li></ul><b>Example</b>: Let's say you place the following files:<br><tt>{omd_root}/local/share/check_mk/agents/custom/myset/bin/some_executable</tt><br><tt>{omd_root}/local/share/check_mk/agents/custom/myset/lib/local/my_local_check</tt><br><tt>{omd_root}/local/share/check_mk/agents/custom/myset/some_file</tt><br>and activate <i>myset</i> in this rule.<br>Then, the following files will be deployed to target hosts when not further configuring agent paths:<br><tt>/usr/bin/some_executable</tt><br><tt>/usr/lib/check_mk_agent/local/my_local_check</tt><br><tt>/usr/lib/check_mk_agent/some_file</tt><br>When activating the single directory deployment in the <i>Customize agent package</i> rule set:<br><tt>/opt/checkmk/agent/default/package/bin/some_executable</tt><br><tt>/opt/checkmk/agent/default/package/local/my_local_check</tt><br><tt>/opt/checkmk/agent/default/package/some_file</tt><br><br><b>Note</b>: When using the Windows agent, all logical paths point to the same location - the agent installation dir.
yesterday
User avatar silke.paintner

New translation

Checkmk / dev — English (United States)

Notifications are sent only for event types defined by the 'Notified events for services' ruleset
Notifications are sent only for event types defined by the 'Notified events for services' rule set
yesterday
User avatar silke.paintner

New translation

Checkmk / dev — English (United States)

Notifications are sent only for event types defined by the 'Notified events for hosts' ruleset
Notifications are sent only for event types defined by the 'Notified events for hosts' rule set
yesterday
User avatar silke.paintner

Translation changed

Checkmk / dev — English (United States)

unknown rulesets
Uunknown rule sets
yesterday
User avatar silke.paintner

Translation changed

Checkmk / dev — English (United States)

The livestatus connection to this site is configured not to be encrypted.
The Livestatus connection to this site is configured not to be encrypted.
yesterday
User avatar silke.paintner

Translation changed

Checkmk / stable — English (United States)

The livestatus connection to this site is configured not to be encrypted.
The Livestatus connection to this site is configured not to be encrypted.
yesterday
User avatar None

New strings to translate

Checkmk / stable — English (United States)

2 new strings to translate appeared to the translation. yesterday
Browse all changes for this language