Resolution
From the instance’s main dashboard, navigate to to Manage Jenkins > System > Administrative monitors configuration > Administrative monitors. There, you’ll see a comprehesive list of all monitors that are applicable for your current version of the product there. Enable the one that you are missing and then go back to Manage Jenkins to confirm that the banner has been restored.
If the monitor message still doesn’t show up, open a Support ticket with CloudBees and provide a Support Bundle with Configuration Files (Jenkins Global Configuration File and Other Jenkins Configuration Files).
Example Use Cases
Example A: Node label migration monitor
Issue
-
I unintentionally dismissed the administrative monitor to perform the node label migration.
-
I have noticed that some of my controllers are using the old default node label and name "master".
Context
As explained in Built-In Node Name and Label Migration, as part of the terminology cleanup effort, the built-in node was renamed from "master node" to "built-in node" after Jenkins 2.319.1. This is not just a change affecting the UI and documentation: the node name affects the implicitly assigned label of the node, and consequently the NODE_LABELS and the NODE_NAME environment variables.
Same as in Jenkins, existing instances upgrading to CloudBees CI 2.319.1.5 or newer do not automatically get these behavior changes applied. Instead, an administrative monitor informs administrators about this change and allows them to apply it:
The name of the monitor that you need to restore is Built-In Node Name and Label Migration.
Example B: User Activity Monitoring database migration
Issue
-
I unintentionally dismissed the administrative monitor to perform the User Activity Monitoring data migration.
Context
As explained in Migrating historical User Activity Monitoring Plugin data, in the 2.332.3.2 release, the User Activity Monitoring Plugin was updated to use a new database. The new database is installed automatically when you upgrade to version 2.332.3.2 or later. However, historical data tracked by the plugin will not be migrated to the new database. You may continue to use the User Activity Monitoring Plugin normally and user activity will be captured again, or you can migrate the data from the old database if you need historical data.
An administrative monitor message appears after the upgrade asking whether you would like to migrate the historical User Activity Monitoring data:
The name of the monitor that you need to restore is Data migration needed for user activity monitoring.