Resolving a downtime status of an endpoint
Typically, monitoring jobs automatically adjust their up or down status based on the health of their associated endpoint. In some cases, you might want to force an up or down status manually to resume or prevent traffic to that endpoint, regardless of the outcome of the health check.
For example, suppose that a health check indicates that an endpoint is up, but you want to stop traffic to that endpoint. In this case, you can adjust the status of the monitoring job to down manually. Doing this drains traffic away from the endpoint, which can be a helpful tool during maintenance windows that require a restart.
Example use case
Suppose that your website is up, but the monitoring job indicates that the site is down due to a networking issue. The monitoring job sends a notification through all notifiers, including the data feed notifier, which is the mechanism that updates the answer metadata, indicating that the endpoint is down, triggering the automatic failover configuration that you applied to your DNS records. IBM® NS1 Connect® avoids sending DNS traffic to the endpoint until the monitoring job indicates that the endpoint is available.
- Pause the monitoring job to prevent automatic updates to the status of the monitoring job.
- Force the status of the monitoring job to up where it remains until you change it again or resume the monitoring job.
To pause a monitoring job and change its status through the API, refer to the NS1 Connect API documentation.