Active service checks in Nagios Core run plugins from the scheduler. Disabling active checks for one service stops Nagios from scheduling that service's plugin while keeping the service visible for status review, comments, downtime, and later re-enablement.
The web interface submits the runtime change through cmd.cgi and the external command file. The current CGI user must be authorized for service commands, and Nagios Core must have external command processing enabled before the scheduler accepts the request.
Use disabled active checks for a narrow case such as a broken plugin, a temporary check target problem, or a controlled test where the service should stay visible but stop running active checks. Use scheduled downtime instead when contacts should see that an outage is planned.
http://monitor.example.net/nagios4/
The command list shows the inverse action for the current state. Disable active checks means active checks are currently enabled for that service.
Related: How to enable external commands in Nagios Core
Related: How to configure Nagios Core CGI authorization

The service can still show its previous state until a passive result is submitted or active checks are enabled and a new check runs.
