| blob | 6cc8294fcf686264f1329c9d34513384bf9451be |
1 #!/usr/bin/python
2 # -*- encoding: utf-8; py-indent-offset: 4 -*-
3 # +------------------------------------------------------------------+
4 # | ____ _ _ __ __ _ __ |
5 # | / ___| |__ ___ ___| | __ | \/ | |/ / |
6 # | | | | '_ \ / _ \/ __| |/ / | |\/| | ' / |
7 # | | |___| | | | __/ (__| < | | | | . \ |
8 # | \____|_| |_|\___|\___|_|\_\___|_| |_|_|\_\ |
9 # | |
10 # | Copyright Mathias Kettner 2014 mk@mathias-kettner.de |
11 # +------------------------------------------------------------------+
12 #
13 # This file is part of Check_MK.
14 # The official homepage is at http://mathias-kettner.de/check_mk.
15 #
16 # check_mk is free software; you can redistribute it and/or modify it
17 # under the terms of the GNU General Public License as published by
18 # the Free Software Foundation in version 2. check_mk is distributed
19 # in the hope that it will be useful, but WITHOUT ANY WARRANTY; with-
20 # out even the implied warranty of MERCHANTABILITY or FITNESS FOR A
21 # PARTICULAR PURPOSE. See the GNU General Public License for more de-
22 # tails. You should have received a copy of the GNU General Public
23 # License along with GNU Make; see the file COPYING. If not, write
24 # to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor,
25 # Boston, MA 02110-1301 USA.
27 import re
28 import logging
30 import cmk
43 Dictionary,
44 TextAscii,
45 TextUnicode,
46 DropdownChoice,
47 Tuple,
48 ListOf,
49 Integer,
50 Float,
51 Transform,
52 ListOfStrings,
53 IPNetwork,
54 CascadingDropdown,
55 MonitoringState,
56 RegExpUnicode,
57 IconSelector,
58 PasswordSpec,
59 ListOfTimeRanges,
60 Age,
61 FixedValue,
62 Optional,
63 Alternative,
64 ListChoice,
65 Checkbox,
66 ID,
67 ListOfCAs,
68 LogLevelChoice,
69 Labels,
70 )
73 config_variable_group_registry,
74 ConfigVariableGroup,
75 config_variable_registry,
76 ConfigVariable,
77 ConfigDomainGUI,
78 ConfigDomainCore,
79 ConfigDomainCACertificates,
80 site_neutral_path,
81 rulespec_registry,
82 HostRulespec,
83 ServiceRulespec,
84 BinaryHostRulespec,
85 BinaryServiceRulespec,
86 rulespec_group_registry,
87 RulespecGroup,
88 RulespecSubGroup,
89 PluginCommandLine,
90 UserIconOrAction,
91 SNMPCredentials,
92 IPMIParameters,
93 HostnameTranslation,
94 ServiceDescriptionTranslation,
95 ContactGroupSelection,
96 HostGroupSelection,
97 ServiceGroupSelection,
98 CheckTypeSelection,
99 TimeperiodSelection,
100 HTTPProxyInput,
101 )
108 # .--Global Settings-----------------------------------------------------.
109 # | ____ _ _ _ ____ _ _ _ |
110 # | / ___| | ___ | |__ __ _| | / ___| ___| |_| |_(_)_ __ __ _ ___ |
111 # || | _| |/ _ \| '_ \ / _` | | \___ \ / _ \ __| __| | '_ \ / _` / __| |
112 # || |_| | | (_) | |_) | (_| | | ___) | __/ |_| |_| | | | | (_| \__ \ |
113 # | \____|_|\___/|_.__/ \__,_|_| |____/ \___|\__|\__|_|_| |_|\__, |___/ |
114 # | |___/ |
115 # +----------------------------------------------------------------------+
116 # | Global configuration settings for main.mk and multisite.mk |
117 # '----------------------------------------------------------------------'
132 return ConfigVariableGroupUserInterface
135 return ConfigDomainGUI
145 )
151 return ConfigVariableGroupUserInterface
154 return ConfigDomainGUI
166 return ConfigVariableGroupUserInterface
169 return ConfigDomainGUI
181 optional_keys=[],
182 )
185 elements = []
195 "about compiling BI aggregations. This includes statistics and "
200 ]:
206 )))
208 return elements
214 return ConfigVariableGroupUserInterface
217 return ConfigDomainGUI
227 "are being displayed and various debug information in other places is "
229 )
235 return ConfigVariableGroupUserInterface
238 return ConfigDomainGUI
247 "Is done using the Python module cProfile. When profiling is performed "
249 "file you can get runtime statistics about the last processed page. When "
250 "enabled by request the profiling mode is enabled by providing the HTTP "
254 choices=[
258 ],
259 )
265 return ConfigVariableGroupUserInterface
268 return ConfigDomainGUI
279 )
285 return ConfigVariableGroupUserInterface
288 return ConfigDomainGUI
298 'If a user modifies the selection in a view, these selections are persisted for the currently '
299 'open view. When a view is re-opened a new selection is used. The old one remains on the '
302 )
308 return ConfigVariableGroupUserInterface
311 return ConfigDomainGUI
321 _("This option controls whether error messages from unreachable sites are shown in the output of "
322 "views. Those error messages shall alert you that not all data from all sites has been shown. "
324 )
330 return ConfigVariableGroupUserInterface
333 return ConfigDomainGUI
343 "in a Multisite status view if that view has been configured for sounds. "
344 "From the views shipped in with Multisite all problem views have sounds "
346 )
352 return ConfigVariableGroupUserInterface
355 return ConfigDomainGUI
368 ),
372 "used context buttons and hides the rest. Which buttons are used "
374 )
380 return ConfigVariableGroupUserInterface
383 return ConfigDomainGUI
392 "limit, a warning is being displayed and no further data is being shown. "
395 )
401 return ConfigVariableGroupUserInterface
404 return ConfigDomainGUI
413 "limit, an error message is shown. The normal user cannot override "
414 "the hard limit. The purpose of the hard limit is to secure the server "
417 )
423 return ConfigVariableGroupUserInterface
426 return ConfigDomainGUI
435 "appear listing all matching host names containing that text. "
436 "That list is limited in size so that the dropdown will not get "
439 )
445 return ConfigVariableGroupUserInterface
448 return ConfigDomainGUI
456 elements=[
459 choices=[
467 ],
468 ),
471 choices=[
477 ],
478 ),
479 ],),
482 )
488 return ConfigVariableGroupUserInterface
491 return ConfigDomainGUI
504 )
510 return ConfigVariableGroupUserInterface
513 return ConfigDomainGUI
522 "is shown in the main (right) frame. You can replace this with any other "
527 )
533 return ConfigVariableGroupUserInterface
536 return ConfigDomainGUI
547 )
553 return ConfigVariableGroupUserInterface
556 return ConfigDomainGUI
566 choices=[
570 ],
571 )
577 return ConfigVariableGroupUserInterface
580 return ConfigDomainGUI
589 "code received from external sources, like plugin output or log messages. "
590 "If you are really sure what you are doing and need to have HTML codes, like "
591 "links rendered, disable this option. Be aware, you might open the way "
593 "This setting can either be set globally or individually for selected hosts "
596 )
602 return ConfigVariableGroupUserInterface
605 return ConfigDomainGUI
614 "this fails for some reason, the crash reports can be sent by mail to the "
618 )
624 return ConfigVariableGroupUserInterface
627 return ConfigDomainGUI
637 "service in the multisite views. It is only displayed if the user "
639 )
652 }
654 # Transform existing dicts with old key "tag_groups"
664 return ConfigVariableGroupUserInterface
667 return ConfigDomainGUI
676 elements=[
680 )),
684 )),
689 )),
696 )),
697 ],
698 optional_keys=[],
699 ),
704 "These trees organize your hosts based on their values in certain host tag groups. "
708 ),
710 )
715 ]
718 # We add to the choices:
719 # 1. All host tag groups with their id
720 # 2. All *topics* that:
721 # - consist only of checkbox tags
722 # - contain at least two entries
723 choices = []
724 by_topic = {}
729 # Now search for checkbox-only-topics
733 break
739 ))
741 return choices
750 # Validate that each element is selected once
755 varprefix,
765 return ConfigVariableGroupUserInterface
768 return ConfigDomainGUI
777 "then Multisite will use this number of seconds as a timeout. If the "
778 "monitoring core has not executed the check within this time, an error "
783 )
789 return ConfigVariableGroupUserInterface
792 return ConfigDomainGUI
803 )
809 return ConfigVariableGroupUserInterface
812 return ConfigDomainGUI
821 "interval. You can change the refresh interval to fit your needs here. This "
822 "value means that all snapnis which request a regular refresh are updated "
827 )
833 return ConfigVariableGroupUserInterface
836 return ConfigDomainGUI
847 ),
850 "The sidebar can be configured to regularly check for pending popup notififcations. "
853 )
859 return ConfigVariableGroupUserInterface
862 return ConfigDomainGUI
871 elements=[
879 )),
887 )),
888 ],
889 ),
893 "When enabled a new button <i>Adhoc downtime for __ minutes</i> will "
895 )
901 return ConfigVariableGroupUserInterface
904 return ConfigDomainGUI
917 ),
922 "variable from the incoming HTTP request and simply takes the string "
923 "in this variable as name of the authenticated user. "
924 "Be warned: Only allow access from trusted ip addresses "
925 "(Apache <tt>Allow from</tt>), like proxy "
926 "servers, to this webpage. A user with access to this page could simply fake "
927 "the authentication information. This option can be useful to "
932 )
938 return ConfigVariableGroupUserInterface
941 return ConfigDomainGUI
950 'The staleness value of a host / service is calculated by measuring the '
951 'configured check intervals a check result is old. A value of 1.5 means the '
952 'current check result has been gathered one and a half check intervals of an object. '
955 )
961 return ConfigVariableGroupUserInterface
964 return ConfigDomainGUI
972 elements=[
978 )),
984 ),
986 )),
990 elements=[
995 ),
998 choices=[
1001 ],
1002 ),
1003 ],
1005 ),
1008 )),
1009 ],
1010 required_keys=[],
1011 )
1017 return ConfigVariableGroupUserInterface
1020 return ConfigDomainGUI
1029 elements=[
1036 ),
1037 ],),
1041 ),
1044 )
1050 return ConfigVariableGroupUserInterface
1053 return ConfigDomainGUI
1062 elements=[
1065 elements=[
1069 )),
1075 elements=[
1080 'can use some macros within the URL which are dynamically '
1081 'replaced for each object. These are:<br>'
1082 '<ul>'
1083 '<li>$HOSTNAME$: Contains the name of the host</li>'
1084 '<li>$HOSTNAME_URL_ENCODED$: Same as above but URL encoded</li>'
1085 '<li>$SERVICEDESC$: Contains the service description '
1086 '(in case this is a service)</li>'
1087 '<li>$SERVICEDESC_URL_ENCODED$: Same as above but URL encoded</li>'
1088 '<li>$HOSTADDRESS$: Contains the network address of the host</li>'
1089 '<li>$HOSTADDRESS_URL_ENCODED$: Same as above but URL encoded</li>'
1090 '<li>$USER_ID$: The user ID of the currently active user</li>'
1093 ),
1096 choices=[
1100 )),
1102 ],
1103 ),
1104 ],
1105 ),
1107 )),
1115 )),
1121 'elements in the column and the menu. The elements are sorted '
1122 'from smaller to higher numbers. The action menu icon '
1123 'has a sort index of <tt>10</tt>, the graph icon a sort index '
1124 'of <tt>20</tt>. All other default icons have a sort index of '
1128 )),
1129 ],
1131 ),
1132 ],),
1136 ),
1139 )
1145 return ConfigVariableGroupUserInterface
1148 return ConfigDomainGUI
1157 elements=[
1162 "service attribute will be computed based on the ID. The "
1163 "custom service attribute will be named <tt>_[ID]</tt> in "
1164 "the core configuration and can be gathered using the "
1165 "Livestatus column <tt>custom_variables</tt> using the "
1166 "<tt>[ID]</tt>. The custom service attributes are available "
1167 "to notification scripts as environment variable named "
1172 "An identifier must only consist of letters, digits, dash and "
1179 choices=[
1181 ],
1182 )),
1183 ],
1184 optional_keys=[],
1185 ),
1194 # Unique IDs are ensured by the transform below. The Transform is executed
1195 # before the validation function has the chance to validate it and print a
1196 # custom error message.
1198 ),
1201 )
1204 internal_ids = [
1210 ]
1215 seen_titles = []
1225 @property
1227 return RulespecGroupMonitoringConfigurationServiceChecks
1229 @property
1233 @property
1237 @property
1241 @property
1247 ),
1254 )
1257 choices = []
1269 seen_ids = []
1278 @property
1280 return RulespecGroupMonitoringConfigurationServiceChecks
1282 @property
1286 @property
1290 @property
1294 @property
1300 ),
1306 )
1309 choices = []
1318 seen_ids = []
1327 @property
1329 return RulespecGroupMonitoringConfigurationServiceChecks
1331 @property
1335 @property
1339 @property
1343 @property
1350 )
1355 @property
1357 return RulespecGroupMonitoringConfigurationHostChecks
1359 @property
1363 @property
1367 @property
1374 )
1380 return ConfigVariableGroupUserInterface
1383 return ConfigDomainGUI
1395 elements=[
1399 ),
1402 choices=[
1407 ],
1409 )
1410 ],
1413 ))],
1414 optional_keys=[],
1415 ),
1419 )
1425 return ConfigVariableGroupUserInterface
1428 return ConfigDomainGUI
1437 elements=[
1442 ),
1444 elements=[
1452 )),
1458 'elements in the column and the menu. The elements are sorted '
1459 'from smaller to higher numbers. The action menu icon '
1460 'has a sort index of <tt>10</tt>, the graph icon a sort index '
1461 'of <tt>20</tt>. All other default icons have a sort index of '
1464 )),
1465 ],
1467 ),
1468 ],),
1473 "options of the builtin icons. You can change whether or not "
1474 "the icons are shown in the popup menu or on top level and "
1476 ),
1479 )
1488 return ConfigVariableGroupUserInterface
1491 return ConfigDomainGUI
1499 elements=[
1507 )),
1515 )),
1516 ],
1517 optional_keys=[],
1518 ),
1521 "You can use this option to make the service table views fold services matching "
1522 "the given patterns into groups. Only services in state <i>OK</i> will be folded "
1523 "together. Groups of only one service will not be rendered. If multiple patterns "
1526 )
1532 return ConfigVariableGroupUserInterface
1535 return ConfigDomainGUI
1545 ),
1548 "By default the network topology view shows you the parent / child relations "
1549 "of all hosts within your local site. The list can be filtered based on hostgroup "
1550 "memberships by the users. You can define a default group to use for filtering "
1553 )
1559 return ConfigVariableGroupUserInterface
1562 return ConfigDomainGUI
1570 elements=[
1575 )),
1581 )),
1587 )),
1593 )),
1594 ],
1595 optional_keys=[],
1596 )
1602 return ConfigVariableGroupSiteManagement
1605 return ConfigDomainCACertificates
1614 "certificate authorities configured here for verifying the SSL certificate of "
1615 "the destination server. This is used for example when performing WATO "
1616 "replication to slave sites or when special agents are communicating via HTTPS. "
1619 elements=[
1624 "trusted CAs. Depending on your linux distributions the paths where "
1625 "these CAs are stored and the commands to manage the CAs differ. "
1626 "Please checko out the documentation of your linux distribution "
1627 "in case you want to customize trusted CAs system wide. You can "
1628 "choose here to trust the system wide CAs here. Check_MK will search "
1632 )),
1636 )),
1637 ],
1639 )
1642 #.
1643 # .--WATO----------------------------------------------------------------.
1644 # | __ ___ _____ ___ |
1645 # | \ \ / / \|_ _/ _ \ |
1646 # | \ \ /\ / / _ \ | || | | | |
1647 # | \ V V / ___ \| || |_| | |
1648 # | \_/\_/_/ \_\_| \___/ |
1649 # | |
1650 # +----------------------------------------------------------------------+
1651 # | Global Configuration for WATO |
1652 # '----------------------------------------------------------------------'
1667 return ConfigVariableGroupWATO
1670 return ConfigDomainGUI
1679 "will be created. You can also create snapshots manually. WATO will delete old "
1682 )
1688 return ConfigVariableGroupWATO
1691 return ConfigDomainGUI
1700 choices=[
1703 ],
1704 )
1710 return ConfigVariableGroupWATO
1713 return ConfigDomainGUI
1723 "communication between sites. Previous versions of Check_MK used an insecure encoding "
1724 "named <tt>pickle</tt>. Even in the current version WATO falls back to <tt>pickle</tt> "
1725 "if your Python version is not recent enough. This is at least the case for RedHat/CentOS 5.X "
1726 "and Debian 5.0. In a mixed environment you can force using the legacy <tt>pickle</tt> format "
1728 )
1734 return ConfigVariableGroupWATO
1737 return ConfigDomainGUI
1747 "are not shown. They will automatically be derived from the name of the folder "
1748 "when a new folder is being created. Disable this option if you want to see and "
1750 )
1756 return ConfigVariableGroupWATO
1759 return ConfigDomainGUI
1770 "of unverified snapshots represents a security risk, since the content of a snapshot is executed "
1771 "during runtime. Any manipulations in the content - either willingly or unwillingly (XSS attack) "
1773 )
1779 return ConfigVariableGroupWATO
1782 return ConfigDomainGUI
1792 )
1798 return ConfigVariableGroupWATO
1801 return ConfigDomainGUI
1812 )
1818 return ConfigVariableGroupWATO
1821 return ConfigDomainGUI
1831 )
1837 return ConfigVariableGroupWATO
1840 return ConfigDomainGUI
1850 "When enabled, all changes of configuration files are tracked with the "
1851 "version control system GIT. You need to make sure that git is installed "
1852 "on your monitoring server. The version history currently cannot be viewed "
1853 "via the web GUI. Please use git command line tools within your Check_MK "
1854 "configuration directory. If you want easier tracking of configuration file changes "
1855 "simply enable the global settings option <tt>Pretty print configuration files</tt>"
1856 ),
1857 )
1863 return ConfigVariableGroupWATO
1866 return ConfigDomainGUI
1877 "On the downside, however, pretty printing bigger configurations can be quite slow - "
1879 )
1885 return ConfigVariableGroupWATO
1888 return ConfigDomainGUI
1898 "When enabled, a subfolder is not shown, when the user does not have sufficient "
1899 "permissions to this folder and all of its subfolders. However, the subfolder is "
1901 )
1907 return ConfigVariableGroupWATO
1910 return ConfigDomainGUI
1918 elements=[
1921 ],
1923 ),
1928 )
1931 #.
1932 # .--User Management-----------------------------------------------------.
1933 # | _ _ __ __ _ |
1934 # | | | | |___ ___ _ __ | \/ | __ _ _ __ ___ | |_ |
1935 # | | | | / __|/ _ \ '__| | |\/| |/ _` | '_ ` _ \| __| |
1936 # | | |_| \__ \ __/ | | | | | (_| | | | | | | |_ |
1937 # | \___/|___/\___|_| |_| |_|\__, |_| |_| |_|\__| |
1938 # | |___/ |
1939 # +----------------------------------------------------------------------+
1940 # | Global settings for users and LDAP connector. |
1941 # '----------------------------------------------------------------------'
1956 return ConfigVariableGroupUserManagement
1959 return ConfigDomainGUI
1970 ),
1975 "the configured number of consecutive invalid login attempts. "
1976 "Once the account is locked only an admin user can unlock it. "
1977 "Beware: Also the admin users will be locked that way. You need "
1978 "to manually edit <tt>etc/htpasswd</tt> and remove the <tt>!</tt> "
1980 )
1986 return ConfigVariableGroupUserManagement
1989 return ConfigDomainGUI
1998 'You can define some rules to which each user password ahers. By default '
1999 'all passwords are accepted, even ones which are made of only a single character, '
2000 'which is obviously a bad idea. Using this option you can enforce your users '
2002 elements=[
2006 )),
2013 "Force the user to choose a password that contains characters from at least "
2014 "this number of different character groups. "
2015 "Character groups are: <ul>"
2016 "<li>lowercase letters</li>"
2017 "<li>uppercase letters</li>"
2018 "<li>digits</li>"
2019 "<li>special characters such as an underscore or dash</li>"
2021 )),
2028 )),
2029 ],
2030 )
2036 return ConfigVariableGroupUserManagement
2039 return ConfigDomainGUI
2051 ),
2055 "the user is locked. By enabling this option, you can apply a time limit "
2056 "to login sessions which is applied when the user stops interacting with "
2057 "the GUI for a given amount of time. When a user is exceeding the configured "
2058 "maximum idle time, the user will be logged out and redirected to the login "
2059 "screen to renew the login session. This setting can be overriden for each "
2061 )
2067 return ConfigVariableGroupUserManagement
2070 return ConfigDomainGUI
2083 ),
2087 "the same time. If you want to enforce your users to be able to login only once "
2088 " (from one client which means device and browser), you can enable this option. "
2089 "When the user logs out or is inactive for the configured amount of time, the "
2090 "session is invalidated automatically and the user has to log in again from the "
2092 )
2098 return ConfigVariableGroupUserManagement
2101 return ConfigDomainGUI
2110 "With this option you can specify the attributes a user which is created during "
2114 optional_keys=[],
2115 )
2118 elements = []
2131 )),
2136 default_value=[],
2138 )),
2145 ))
2146 ]
2161 return ConfigVariableGroupUserManagement
2164 return ConfigDomainGUI
2175 )
2178 #.
2179 # .--Check_MK------------------------------------------------------------.
2180 # | ____ _ _ __ __ _ __ |
2181 # | / ___| |__ ___ ___| | __ | \/ | |/ / |
2182 # | | | | '_ \ / _ \/ __| |/ / | |\/| | ' / |
2183 # | | |___| | | | __/ (__| < | | | | . \ |
2184 # | \____|_| |_|\___|\___|_|\_\___|_| |_|_|\_\ |
2185 # | |_____| |
2186 # +----------------------------------------------------------------------+
2187 # | Operation mode of Check_MK |
2188 # '----------------------------------------------------------------------'
2203 return ConfigVariableGroupCheckExecution
2206 return ConfigDomainCore
2215 "In order to make Check_MK more consistent, "
2216 "the descriptions of several services have been renamed in newer "
2217 "Check_MK versions. One example is the filesystem services that have "
2218 "been renamed from <tt>fs_</tt> into <tt>Filesystem</tt>. But since renaming "
2219 "of existing services has many implications - including existing rules, performance "
2220 "data and availability history - these renamings are disabled per default for "
2221 "existing installations. Here you can switch to the new descriptions for "
2223 choices=[
2284 ],
2286 )
2292 return ConfigVariableGroupCheckExecution
2295 return ConfigDomainCore
2304 "Timeout for TCP connect to agent in seconds. If the connection "
2305 "to the agent cannot be established within this time, it is considered to be unreachable. "
2306 "Note: This does <b>not</b> limit the time the agent needs to "
2310 )
2316 return ConfigVariableGroupCheckExecution
2319 return ConfigDomainCore
2329 "No hosts will be contacted, no DNS lookups will take place and data is read "
2330 "from cache files that have been created during normal operation or have "
2332 )
2338 return ConfigVariableGroupCheckExecution
2341 return ConfigDomainCore
2350 "you can decide to abort with an error (default) or have the requests "
2351 "serialized. It is also possible - but not recommended - to turn "
2353 choices=[
2357 ],
2358 )
2364 return ConfigVariableGroupCheckExecution
2367 return ConfigDomainCore
2377 "dynamic simulation data. This feature can be activated here. There "
2379 )
2385 return ConfigVariableGroupCheckExecution
2388 return ConfigDomainCore
2398 "If you enable this option, then Check_MK will not directly Python-bytecompile "
2399 "all host checks when activating the configuration and restarting Nagios. "
2400 "Instead it will delay this to the first "
2401 "time the host is actually checked being by Nagios.<p>This reduces the time needed "
2402 "for the operation, but on the other hand will lead to a slightly higher load "
2404 )
2410 return ConfigVariableGroupCheckExecution
2413 return ConfigDomainCore
2423 "use it instead of getting information from the target hosts while "
2424 "checking a cluster. Per default this is enabled and set to 90 seconds. "
2425 "If your check cycle is set to a larger value than one minute then "
2427 )
2433 return ConfigVariableGroupCheckExecution
2436 return ConfigDomainCore
2445 "The maximum age for piggy back data from another host to be valid for monitoring. "
2446 "Older files are deleted before processing them. Please make sure that this age is "
2448 )
2454 return ConfigVariableGroupCheckExecution
2457 return ConfigDomainCore
2467 "for the Check_MK output, giving information regarding the process times. "
2468 "It provides the following fields: user_time, system_time, children_user_time "
2470 )
2476 return ConfigVariableGroupCheckExecution
2479 return ConfigDomainCore
2489 "When this option is enabled (which is the default), then Check_MK tries to "
2490 "prevent IP address lookups during the configuration generation. This can speed "
2491 "up this process greatly when you have a larger number of hosts. The cache is stored "
2492 "in a simple file. Note: when the cache is enabled then changes of the IP address "
2493 "of a host in your name server will not be detected immediately. If you need an "
2494 "immediate update then simply disable the cache once, activate the changes and "
2495 "enabled it again. OMD based installations automatically update the cache once "
2497 )
2503 return ConfigVariableGroupCheckExecution
2506 return ConfigDomainCore
2516 "By default Check_MK uses command line calls of Net-SNMP tools like snmpget or "
2517 "snmpwalk to gather SNMP information. For each request a new command line "
2518 "program is being executed. It is now possible to use the inline SNMP implementation "
2519 "which calls the net-snmp libraries directly via its python bindings. This "
2520 "should increase the performance of SNMP checks in a significant way. The inline "
2521 "SNMP mode is a feature which improves the performance for large installations and "
2523 )
2529 return ConfigVariableGroupCheckExecution
2532 return ConfigDomainCore
2542 "When you have enabled Inline SNMP, you can use this flag to enable recording of "
2543 "some performance related values. The recorded values are stored in a single file "
2544 "at <tt>var/check_mk/snmp.stats</tt>.<br><br>"
2545 "<i>Please note:</i> Only enable this for a short period, because it will "
2547 )
2553 return ConfigVariableGroupCheckExecution
2556 return ConfigDomainCore
2566 elements=[
2571 "The ID must be a unique text. It will be used as an internal key "
2574 )),
2582 )),
2584 ],
2586 ),
2591 "used in different places to establish connections to services using these "
2594 ),
2597 )
2604 varprefix,
2610 varprefix,
2627 return ConfigVariableGroupServiceDiscovery
2630 return ConfigDomainCore
2644 "that does a regular check, if the service discovery would find new services "
2645 "currently un-monitored. <b>Note:</b> This option is deprecated and has been "
2647 "which allows a per-host configuration and additional features such as "
2648 "automatic rediscovery. Rules in that rule set will override the global "
2650 )
2656 return ConfigVariableGroupServiceDiscovery
2659 return ConfigDomainCore
2669 choices=[
2674 ],
2675 )
2681 return ConfigVariableGroupServiceDiscovery
2684 return ConfigDomainCore
2692 choices=[
2695 ],
2696 )
2702 return ConfigVariableGroupServiceDiscovery
2705 return ConfigDomainCore
2714 "Automatically schedule service discovery check after service configuration changes"
2715 ),
2717 "configuration of a host via WATO - may it be via manual changes or a bulk "
2718 "discovery - the service discovery check is automatically rescheduled in order "
2720 )
2723 #.
2724 # .--Rulesets------------------------------------------------------------.
2725 # | ____ _ _ |
2726 # | | _ \ _ _| | ___ ___ ___| |_ ___ |
2727 # | | |_) | | | | |/ _ \/ __|/ _ \ __/ __| |
2728 # | | _ <| |_| | | __/\__ \ __/ |_\__ \ |
2729 # | |_| \_\\__,_|_|\___||___/\___|\__|___/ |
2730 # | |
2731 # +----------------------------------------------------------------------+
2732 # | Rulesets for hosts and services except check parameter rules. |
2733 # '----------------------------------------------------------------------'
2738 @property
2742 @property
2746 @property
2753 @property
2755 return RulespecGroupGrouping
2757 @property
2761 @property
2765 @property
2770 "is to put hosts which belong together in a host group to make it possible "
2772 )
2777 @property
2779 return RulespecGroupGrouping
2781 @property
2785 @property
2789 @property
2793 @property
2800 @property
2802 return RulespecGroupGrouping
2804 @property
2808 @property
2812 @property
2819 @property
2821 return RulespecGroupGrouping
2823 @property
2827 @property
2831 @property
2835 @property
2842 @property
2846 @property
2850 @property
2858 @property
2860 return RulespecGroupMonitoringConfiguration
2862 @property
2866 @property
2873 @property
2875 return RulespecGroupMonitoringConfigurationServiceChecks
2877 @property
2881 @property
2885 @property
2892 )
2897 @property
2899 return RulespecGroupMonitoringConfigurationServiceChecks
2901 @property
2905 @property
2909 @property
2917 "check and for legacy checks. Here you can specify a larger interval. Please "
2918 "note, that this setting only applies to active checks (those with the "
2919 "reschedule button). If you want to change the check interval of "
2920 "the Check_MK service only, specify <tt><b>Check_MK$</b></tt> in the list "
2922 )
2927 @property
2929 return RulespecGroupMonitoringConfigurationServiceChecks
2931 @property
2935 @property
2939 @property
2947 "attempts to a number greater than one. In case a service check is not OK "
2948 "and the maximum number of check attempts is not yet reached, it will be "
2949 "rescheduled with this interval. The retry interval is usually set to a smaller "
2950 "value than the normal interval.<br><br>This setting only applies to "
2952 )
2957 @property
2959 return RulespecGroupMonitoringConfigurationServiceChecks
2961 @property
2965 @property
2969 @property
2974 "of that service will only be done in that period. Please note, that the "
2975 "checks driven by Check_MK are passive checks and are not affected by this "
2977 )
2982 @property
2984 return RulespecGroupMonitoringConfigurationServiceChecks
2986 @property
2990 @property
2994 @property
3000 )
3005 @property
3007 return RulespecGroupMonitoringConfigurationServiceChecks
3009 @property
3013 @property
3017 @property
3025 )
3030 @property
3032 return RulespecGroupMonitoringConfigurationServiceChecks
3034 @property
3038 @property
3042 @property
3047 "This setting allows you to disable the processing of passiv check results for a "
3051 )
3056 @property
3058 return RulespecGroupMonitoringConfigurationServiceChecks
3060 @property
3064 @property
3068 @property
3075 )
3080 @property
3082 return RulespecGroupMonitoringConfiguration
3084 @property
3088 @property
3095 @property
3097 return RulespecGroupMonitoringConfigurationHostChecks
3099 @property
3103 @property
3110 )
3115 @property
3117 return RulespecGroupMonitoringConfigurationHostChecks
3119 @property
3123 @property
3131 _("The default interval is set to 6 seconds for smart ping and one minute for all other. Here you can specify a larger "
3132 "interval. The host is contacted in this interval on a regular base. The host "
3133 "check is also being executed when a problematic service state is detected to check "
3135 )
3140 @property
3142 return RulespecGroupMonitoringConfigurationHostChecks
3144 @property
3148 @property
3156 "This setting is relevant if you have set the maximum number of check "
3157 "attempts to a number greater than one. In case a host check is not UP "
3158 "and the maximum number of check attempts is not yet reached, it will be "
3159 "rescheduled with this interval. The retry interval is usually set to a smaller "
3160 "value than the normal interval. The default is 6 seconds for smart ping and 60 seconds for all other."
3161 ),
3162 )
3167 @property
3169 return RulespecGroupMonitoringConfigurationHostChecks
3171 @property
3175 @property
3180 "host will only take place within that period. In the rest of the time "
3182 )
3187 @property
3189 return RulespecGroupMonitoringConfigurationHostChecks
3191 @property
3195 @property
3200 "Usually Check_MK uses a series of PING (ICMP echo request) in order to determine "
3201 "whether a host is up. In some cases this is not possible, however. With this rule "
3203 "The option to use a custom command can only be configured with the permission "
3208 )
3212 custom_choice = [
3214 ]
3216 custom_choice = []
3232 )),
3233 ] + custom_choice
3238 @property
3240 return RulespecGroupMonitoringConfiguration
3242 @property
3246 @property
3253 @property
3255 return RulespecGroupMonitoringConfigurationNotifications
3257 @property
3261 @property
3266 "host completely. Per default all notifications are enabled. Sometimes "
3267 "it is more convenient to just disable notifications then to remove a "
3268 "host completely from the monitoring. Note: this setting has no effect "
3270 choices=[
3273 ],
3274 )
3279 @property
3281 return RulespecGroupMonitoringConfigurationNotifications
3283 @property
3287 @property
3291 @property
3297 choices=[
3300 ],
3301 )
3306 @property
3308 return RulespecGroupMonitoringConfigurationNotifications
3310 @property
3314 @property
3318 choices=[
3324 ],
3326 ),
3329 "This ruleset allows you to restrict notifications of host problems to certain "
3330 "states, e.g. only notify on DOWN, but not on UNREACHABLE. Please select the types "
3331 "of events that should initiate notifications. Please note that several other "
3332 "filters must also be passed in order for notifications to finally being sent out."
3333 "<br><br>"
3334 "Please note: There is a difference between the Microcore and Nagios when you have "
3335 "a host that has no matching rule in this ruleset. In this case the Microcore will "
3336 "not send out UNREACHABLE notifications while the Nagios core would send out "
3337 "UNREACHABLE notifications. To align this behaviour, create a rule matching "
3341 )
3346 @property
3348 return RulespecGroupMonitoringConfigurationNotifications
3350 @property
3354 @property
3358 @property
3362 choices=[
3369 ],
3371 ),
3374 "This ruleset allows you to restrict notifications of service problems to certain "
3375 "states, e.g. only notify on CRIT, but not on WARN. Please select the types "
3376 "of events that should initiate notifications. Please note that several other "
3377 "filters must also be passed in order for notifications to finally being sent out."
3378 ),
3381 )
3386 @property
3388 return RulespecGroupMonitoringConfigurationNotifications
3390 @property
3394 @property
3399 "about problems of that host (not of its services!) will only be sent "
3400 "if those problems occur within the notification period. Also you can "
3401 "filter out problems in the problems views for objects not being in "
3402 "their notification period (you can think of the notification period "
3404 )
3409 @property
3411 return RulespecGroupMonitoringConfigurationNotifications
3413 @property
3417 @property
3421 @property
3426 "about that service will only be sent "
3427 "if those problems occur within the notification period. Also you can "
3428 "filter out problems in the problems views for objects not being in "
3429 "their notification period (you can think of the notification period "
3431 )
3444 @property
3446 return RulespecGroupMonitoringConfigurationNotifications
3448 @property
3452 @property
3456 @property
3465 "specified amount of time. If the host is up again within that "
3467 ),
3470 )
3475 @property
3477 return RulespecGroupMonitoringConfigurationNotifications
3479 @property
3483 @property
3487 @property
3491 @property
3501 "specified amount of time. If the service is OK again within that "
3503 ),
3506 )
3511 @property
3513 return RulespecGroupMonitoringConfigurationNotifications
3515 @property
3519 @property
3528 ),
3530 ),
3533 "of the host notifications will be sent out in regular intervals "
3538 )
3543 @property
3545 return RulespecGroupMonitoringConfigurationNotifications
3547 @property
3551 @property
3555 @property
3561 ),
3564 "of the service notifications will be sent out in regular intervals "
3569 )
3574 @property
3576 return RulespecGroupMonitoringConfigurationNotifications
3578 @property
3582 @property
3588 choices=[
3591 ],
3592 )
3597 @property
3599 return RulespecGroupMonitoringConfigurationNotifications
3601 @property
3605 @property
3609 @property
3615 choices=[
3618 ],
3619 )
3624 @property
3626 return RulespecGroupMonitoringConfigurationNotifications
3628 @property
3632 @property
3636 @property
3645 )
3650 @property
3652 return RulespecGroupMonitoringConfigurationNotifications
3654 @property
3658 @property
3667 )
3672 @property
3674 return RulespecGroupMonitoringConfigurationNotifications
3676 @property
3680 @property
3684 @property
3689 "to be displayed for certain services. This name is available as "
3690 "a column when creating new views or modifying existing ones. "
3691 "It is always visible in the details view of a service. In the "
3692 "availability reporting there is an option for using that name "
3693 "instead of the normal service description. It does <b>not</b> automatically "
3694 "replace the normal service name in all views.<br><br><b>Note</b>: The "
3695 "purpose of this rule set is to define unique names for several well-known "
3699 )
3704 @property
3706 return RulespecGroupMonitoringConfiguration
3708 @property
3712 @property
3719 @property
3721 return RulespecGroupMonitoringConfigurationInventoryAndCMK
3723 @property
3727 @property
3731 @property
3734 "to be actually monitored. As long as the rule set is empty "
3735 "all configured hosts will be monitored. As soon as you add at least one "
3738 @property
3740 return True
3745 @property
3747 return RulespecGroupMonitoringConfigurationInventoryAndCMK
3749 @property
3753 @property
3757 @property
3760 "to a host during discovery (automatic service detection). Services that already "
3761 "exist will continued to be monitored but be marked as obsolete in the service "
3764 @property
3771 @property
3773 return RulespecGroupMonitoringConfigurationInventoryAndCMK
3775 @property
3779 @property
3784 "This ruleset is similar to 'Disabled services', but selects checks to be disabled "
3785 "by their <b>type</b>. This allows you to disable certain technical implementations "
3786 "such as filesystem checks via SNMP on hosts that also have the Check_MK agent "
3788 )
3793 @property
3795 return RulespecGroupMonitoringConfigurationInventoryAndCMK
3797 @property
3801 @property
3805 @property
3808 "of a node should be assigned to the cluster and which services to the physical "
3809 "node. This is done by this ruleset. Please note that the rule will be applied to "
3810 "the <i>nodes</i>, not to the cluster.<br><br>Please make sure that you re-"
3813 @property
3820 @property
3822 return RulespecGroupMonitoringConfigurationInventoryAndCMK
3824 @property
3828 @property
3833 default_value={
3838 },
3839 elements=[
3844 ),
3848 "If enabled, Check_MK will create one additional service per host "
3849 "that does a periodic check, if the service discovery would find new services "
3851 elements=[
3858 )),
3863 "Please select which alarm state the service discovery check services "
3865 choices=[
3870 ],
3871 )),
3877 "shall assume in case that non-existing services are being monitored."
3878 ),
3879 choices=[
3884 ],
3885 )),
3889 choices=[
3893 ])),
3898 "If active the check will not only notify about un-monitored services, "
3900 elements=[
3910 )),
3914 "A delay can be configured here so that multiple "
3915 "discoveries can be activated in one go. This avoids frequent core "
3921 title=
3923 ),
3925 "that the automatic system doesn't interfere with "
3927 )),
3931 choices=[
3934 ],
3937 "Here you can have the changes activated whenever services "
3939 )),
3946 "allow only matching services to be activated automatically. "
3949 )),
3956 "prevent matching services from being activated automatically. "
3959 )),
3960 ],
3962 )),
3963 ],
3965 )
3966 ])
3971 @property
3973 return RulespecGroupMonitoringConfiguration
3975 @property
3979 @property
3986 @property
3988 return RulespecGroupMonitoringConfigurationVarious
3990 @property
3994 @property
3998 @property
4004 "such clusters "overlap". In such a case using the ruleset "
4005 "<i>Clustered services</i> is not sufficient since it would not be clear "
4006 "to which of the several possible clusters a service found on such a shared "
4007 "node should be assigned to. With this ruleset you can assign services and "
4009 )
4014 @property
4016 return RulespecGroupMonitoringConfigurationVarious
4018 @property
4022 @property
4027 "When it comes to availability reporting, you might want the report "
4028 "to cover only certain time periods, e.g. only Monday to Friday "
4029 "from 8:00 to 17:00. You can do this by specifying a service period "
4030 "for hosts or services. In the reporting you can then decide to "
4031 "include, exclude or ignore such periods und thus e.g. create a report "
4032 "of the availability just within or without these times. <b>Note</b>: Changes in the "
4033 "actual <i>definition</i> of a time period will only be reflected in "
4034 "times <i>after</i> that change. Selecting a different service period "
4036 )
4041 @property
4043 return RulespecGroupMonitoringConfigurationVarious
4045 @property
4049 @property
4053 @property
4058 "When it comes to availability reporting, you might want the report "
4059 "to cover only certain time periods, e.g. only Monday to Friday "
4060 "from 8:00 to 17:00. You can do this by specifying a service period "
4061 "for hosts or services. In the reporting you can then decide to "
4062 "include, exclude or ignore such periods und thus e.g. create a report "
4063 "of the availability just within or without these times. <b>Note</b>: Changes in the "
4064 "actual <i>definition</i> of a time period will only be reflected in "
4065 "times <i>after</i> that change. Selecting a different service period "
4067 )
4070 #.
4071 # .--User Interface------------------------------------------------------.
4072 # | _ _ ___ _ __ |
4073 # | | | | |___ ___ _ __ |_ _|_ __ | |_ ___ _ __ / _| __ _ ___ ___ |
4074 # | | | | / __|/ _ \ '__| | || '_ \| __/ _ \ '__| |_ / _` |/ __/ _ \ |
4075 # | | |_| \__ \ __/ | | || | | | || __/ | | _| (_| | (_| __/ |
4076 # | \___/|___/\___|_| |___|_| |_|\__\___|_| |_| \__,_|\___\___| |
4077 # | |
4078 # +----------------------------------------------------------------------+
4079 # | User interface specific rule sets |
4080 # '----------------------------------------------------------------------'
4085 @property
4089 @property
4093 @property
4100 @property
4102 return RulespecGroupUserInterface
4104 @property
4108 @property
4116 ),
4118 )
4123 @property
4125 return RulespecGroupUserInterface
4127 @property
4131 @property
4135 @property
4143 ),
4145 )
4150 @property
4152 return RulespecGroupUserInterface
4154 @property
4158 @property
4162 @property
4167 )
4172 @property
4174 return RulespecGroupUserInterface
4176 @property
4180 @property
4184 @property
4188 @property
4193 )
4198 @property
4200 return RulespecGroupUserInterface
4202 @property
4206 @property
4211 "code received from external sources, like plugin output or log messages. "
4212 "If you are really sure what you are doing and need to have HTML codes, like "
4213 "links rendered, disable this option. Be aware, you might open the way "
4215 "This setting can either be set globally or individually for selected hosts "
4217 choices=[
4220 ],
4222 )
4227 @property
4229 return RulespecGroupUserInterface
4231 @property
4235 @property
4239 @property
4244 "code received from external sources, like plugin output or log messages. "
4245 "If you are really sure what you are doing and need to have HTML codes, like "
4246 "links rendered, disable this option. Be aware, you might open the way "
4248 "This setting can either be set globally or individually for selected hosts "
4250 choices=[
4253 ],
4255 )
4260 @property
4264 @property
4268 @property
4275 @property
4277 return RulespecGroupAgent
4279 @property
4283 @property
4290 @property
4292 return RulespecGroupAgentGeneralSettings
4294 @property
4298 @property
4302 @property
4305 "IP addresses of hosts are statically configured or looked up when you activate "
4306 "the changes. In some rare cases DNS lookups must be done each time a host is "
4312 @property
4314 return RulespecGroupAgentGeneralSettings
4316 @property
4320 @property
4323 choices=[
4326 ],
4329 "normally IPv4 is used as primary address family to communicate with this "
4330 "host. The other family, IPv6, is just being pinged. You can use this rule "
4332 )
4337 @property
4339 return RulespecGroupAgent
4341 @property
4345 @property
4352 @property
4354 return RulespecGroupAgentSNMP
4356 @property
4360 @property
4365 _("By default Check_MK uses the community \"public\" to contact hosts via SNMP v1/v2. This rule "
4366 "can be used to customize the the credentials to be used when contacting hosts via SNMP."
4367 ),
4368 )
4373 @property
4375 return RulespecGroupAgentSNMP
4377 @property
4381 @property
4385 choices=[
4388 ],
4389 )
4394 @property
4396 return RulespecGroupAgentSNMP
4398 @property
4402 @property
4407 " always assumes UTF-8 encoding. You can declare other "
4409 choices=[
4413 ],
4414 )
4419 @property
4421 return RulespecGroupAgentSNMP
4423 @property
4427 @property
4431 @property
4434 "1, in order to support as many devices as possible. Please use this ruleset in "
4435 "order to configure SNMP v2c for as many hosts as possible. That version has two "
4436 "advantages: it supports 64 bit counters, which avoids problems with wrapping "
4437 "counters at too much traffic. And it supports bulk walk, which saves much CPU "
4438 "and network resources. Please be aware, however, that there are some broken "
4439 "devices out there, that support bulk walk but behave very bad when it is used. "
4440 "When you want to enable v2c while not using bulk walk, please use the rule set "
4446 @property
4448 return RulespecGroupAgentSNMP
4450 @property
4454 @property
4463 "This variable allows you to configure the numbr of OIDs Check_MK should request "
4464 "at once. This rule only applies to SNMP hosts that are configured to be bulk "
4465 "walk hosts.You may want to use this rule to tune SNMP performance. Be aware: A "
4466 "higher value is not always better. It may decrease the transactions between "
4467 "Check_MK and the target system, but may increase the OID overhead in case you "
4469 )
4474 @property
4476 return RulespecGroupAgentSNMP
4478 @property
4482 @property
4486 @property
4489 "normally ignored by the SNMP inventory. Use this ruleset to select hosts which "
4495 @property
4497 return RulespecGroupAgentSNMP
4499 @property
4503 @property
4507 @property
4510 "and bulk walk. If you want to use SNMP v2c on those devices, nevertheless, you "
4511 "need to configure this device as legacy snmp device and upgrade it to SNMP v2c "
4512 "(without bulk walk) with this rule set. One reason is enabling 64 bit counters. "
4513 "Note: This rule won't apply if the device is already configured as SNMP v2c "
4519 @property
4521 return RulespecGroupAgentSNMP
4523 @property
4527 @property
4531 @property
4535 @property
4541 elements=[
4542 (
4547 "After a request is sent to the remote SNMP agent we will wait up to this "
4555 ),
4556 ),
4563 )),
4564 ],
4565 )
4570 @property
4572 return RulespecGroupAgentSNMP
4574 @property
4578 @property
4582 @property
4585 "the load produced by SNMP monitoring on the monitoring host significantly. This "
4586 "option is enabled by default for all SNMP hosts and it is a good idea to keep "
4587 "this default setting. However, there are SNMP devices which have problems with "
4588 "this SNMP implementation. You can use this rule to disable Inline SNMP for these "
4594 @property
4596 return RulespecGroupAgentSNMP
4598 @property
4602 @property
4606 @property
4609 "the command line with cmk --snmpwalk HOSTNAME. A host that is configured with "
4610 "this ruleset will then use the information from that file instead of using real "
4616 @property
4618 return RulespecGroupAgentSNMP
4620 @property
4624 @property
4633 )
4638 @property
4640 return RulespecGroupAgent
4642 @property
4646 @property
4653 @property
4655 return RulespecGroupAgentCMKAgent
4657 @property
4661 @property
4670 )
4675 @property
4677 return RulespecGroupAgentCMKAgent
4679 @property
4683 @property
4691 "Timeout for TCP connect to the Check_MK agent in seconds. If the connection "
4692 "to the agent cannot be established within this time, it is considered to be unreachable. "
4693 "Note: This does <b>not</b> limit the time the agent needs to "
4694 "generate its output. "
4696 )
4701 @property
4703 return RulespecGroupAgentCMKAgent
4705 @property
4709 @property
4712 elements=[
4718 "baked agents encrypt their output and whether check_mk expects "
4719 "encrypted output. "
4720 "Please note: If you opt to enforce encryption, "
4721 "agents that don't support encryption will not work any more. "
4722 "Further note: This only affects regular agents, not special agents "
4736 ],
4737 optional_keys=[],
4740 )
4745 (
4748 ),
4749 (
4752 ),
4753 (
4756 ),
4757 (
4760 ),
4761 ]
4766 return p
4772 @property
4774 return RulespecGroupAgentCMKAgent
4776 @property
4780 @property
4784 @property
4792 }
4794 @property
4798 elements=[
4803 (
4808 ),
4809 (
4815 ),
4816 (
4820 elements=[
4824 'you can specify a regex pattern to match specific section names and '
4825 'give them an individual state in case they are missing. '
4829 ],
4832 ),
4833 ),
4834 ])),
4838 elements=[
4843 (
4848 ),
4849 ])),
4874 ])),
4875 ],
4877 ),
4881 "This ruleset specifies the total status of the Check_MK services <i>Check_MK</i>, "
4882 "<i>Check_MK Discovery</i> and <i>Check_MK HW/SW Inventory</i> in case of various "
4883 "error situations. One use case is the monitoring of hosts that are not always up. "
4884 "You can have Check_MK an OK status here if the host is not reachable. Note: the "
4886 )
4891 @property
4893 return RulespecGroupAgentCMKAgent
4895 @property
4899 @property
4905 " one specific version. Agents running "
4907 choices=[
4917 )),
4921 )),
4922 ])),
4923 ],
4925 ),
4926 # In the past, this was a OptionalDropdownChoice() which values could be strings:
4927 # ignore, site or a custom string representing a version number.
4930 )
4935 @property
4939 @property
4943 @property
4950 @property
4952 return RulespecGroupMonitoringAgents
4954 @property
4958 @property
4965 @property
4967 return RulespecGroupMonitoringAgentsGenericOptions
4969 @property
4973 @property
4979 "Check_MK agent to certain IP addresses and networks. "
4980 "Usually you configure just the IP addresses of your "
4981 "Check_MK servers here. You can enter either IP addresses "
4982 "in the form <tt>1.2.3.4</tt> or networks in the style "
4983 "<tt>1.2.0.0/16</tt>. If you leave this configuration empty "
4984 "or create no rule then <b>all</b> addresses are allowed to "
4986 )
4991 @property
4993 return RulespecGroupAgentGeneralSettings
4995 @property
4999 @property
5003 @property
5009 "for other hosts "piggyback" with their own data. This is the case "
5010 "for the vSphere special agent and the SAP R/3 plugin, for example. The hostnames "
5011 "that these agents send must match your hostnames in your monitoring configuration. "
5012 "If that is not the case, then with this rule you can define a hostname translation. "
5013 "Note: This rule must be configured for the "pig" - i.e. the host that the "
5015 )
5020 @property
5022 return RulespecGroupAgentGeneralSettings
5024 @property
5028 @property
5034 "<tt>Hostname translation for piggybacked hosts</tt>. Services such as "
5035 "<tt>Check_MK</tt>, <tt>Check_MK Agent</tt>, <tt>Check_MK Discovery</tt>, "
5036 "<tt>Check_MK inventory</tt>, and <tt>Check_MK HW/SW Inventory</tt> are excluded. "
5037 "<b>Attention:</b><ul>"
5038 "<li>Downtimes and other configured rules which match these "
5039 "services have to be adapted.</li>"
5040 "<li>Performance data and graphs will begin from scratch for translated services.</li>"
5041 "<li>Especially configured check parameters keep their functionality further on.</li>"
5042 "<li>This new ruleset translates also the item part of a service description. "
5043 "This means that after such a translation the item may be gone but is used in the "
5044 "conditions of the parameters further on if any parameters are configured. "
5045 "This might be confusing.</li></ul>"
5047 )
5068 @property
5070 return RulespecGroupAgentSNMP
5072 @property
5076 @property
5081 'This rule can be used to customize the check interval of each SNMP based check. '
5082 'With this option it is possible to configure a longer check interval for specific '
5084 elements=[
5089 "individual SNMP based checks here. It is only possible to define "
5090 "SNMP check intervals for main checks and all the related sub "
5091 "checks together. The reason for this is that the data of the "
5092 "main check and it's sub checks is defined for the whole group "
5093 "of checks in the main check and also fetched for all these "
5096 ),
5097 # Transform check types to section names
5099 ),
5105 ),
5106 ])
5111 @property
5113 return RulespecGroupAgentSNMP
5115 @property
5119 @property
5124 'By default Check_MK does not use a specific context during SNMPv3 queries, '
5125 'but some devices are offering their information in different SNMPv3 contexts. '
5126 'This rule can be used to configure, based on hosts and check type, which SNMPv3 '
5128 elements=[
5132 ),
5136 ),
5137 ])