Administrative monitors are warnings shown to Jenkins administrators about the state of the Jenkins instance. It is generally strongly recommended to keep all administrative monitors enabled, but if you are not interested in specific warnings, uncheck them here to permanently hide them.
If access control for builds is not set up, this shows a warning, explaining the problem.
When updating Jenkins from before 2.307, this allows administrators to migrate the built-in node name and label.
Shows a warning when the built-in node has executors despite agents (static or clouds) being configured.
Shows a warning when the built-in node has executors and recommends that agents (static or clouds) are set up.
A diagnostic feature warnings administrators about incorrect encoding of URLs, typically with improperly set up reverse proxies or containers.
This warns administrators that triggers are not firing on schedule, typically because some plugins perform additional actions (like network access) during trigger processing.
When Jenkins detects a cyclic dependency between plugins (a bug in one or more plugins), this message is shown.
Informs administrators about the deprecation of one or more currently installed plugins. This is metadata provided by the configured update sites, and the plugin documentation will usually explain why the plugin is deprecated.
Authentication (security realm) and authorization (authorization strategy) should be set up.
This warning shows up when the available disk space for the Jenkins home directory falls below a certain threshold.
Informs administrators that the TCP agent port is different than its enforced value and will be reset on restart.
Informs administrators about a required plugin update. This is unrelated to plugin updates being available.
Informs about the presence of JRE crash dumps after an abnormal Jenkins termination, and allows viewing them.
Warns about an incomplete initialization, indicating a bug in Jenkins.
When a new release of Jenkins has been released, this informs administrators about it.
Warns administrators about the legacy behavior of allowing users to generate new legacy API tokens.
Warns administrators about the legacy behavior of automatically generating API tokens for new users.
Warns administrators about the presence of legacy API tokens in the configuration of some users.
When Jenkins configuration files contain unloadable data, this informs administrators about the problem. A common cause is plugins having been downgraded, or having changed in backwards-incompatible ways.
Informs administrators about a problem with extensions in some legacy plugins.
Whenever a resource monitor marks a node offline, this warning is shown to inform administrators about it.
If any plugins failed to load, this informs administrators about the problem. This is a severe problem, as re-saving configuration at this point could result in the loss of configuration data related to unloadable plugins.
Recommends Java 11 for running Jenkins if an older version is used.
Informs about the resource root URL option if the Content-Security-Policy HTTP header for user-controlled resources served by Jenkins has been set to a custom value.
If Jenkins is running behind a reverse proxy, this identifies problems with a bad configuration.
Some Jenkins features require the root URL to be defined, and this warns when it is undefined.
Recommends the creation of additional views to help categorize jobs if there are none and too many jobs exist.
If there are more SCM polling activities scheduled than Jenkins can handle in parallel, this informs administrators about the problem and provides diagnostic information.
This warning informs administrators about active security warnings for installed Jenkins core or plugin versions. Rather than disable this warning entirely (including any future issues), consider disabling specific messages in the global security configuration.
![[Jenkins]](/jenkins/static/9f321c9c/images/svgs/logo.svg){kind=logo}
