Thanks for reaching out to us.
When you talk about the OFF setting in ServiceControl, are you referring to the configuration screen in ServicePulse? That screen controls whether or not ServicePulse monitors the endpoint heartbeats. If it is set to "OFF" then the ServicePulse does not consider the endpoint to be heartbeating or offline and simply ignores it, even if it is currently online and sending messages.
After reviewing the different use cases with the ServiceControl, ServiceInsight, and ServicePulse teams, we've come to the conclusion that the list of endpoints used in ServicePulse and the one in ServiceInsight are actually different. In ServicePulse we want the list of all endpoints that are currently running (or that should currently be running). In ServiceInsight we want the list of endpoints which are referenced by failed and audited messages in ServiceControl.
Users of each product will be interested in the data over different time periods. If an endpoint has been decommissioned, then ServicePulse will want to stop monitoring the endpoint immediately. Users of ServiceInsight may still want to see the endpoint (and all messages associated with it) until the data retention period of ServiceControl elapses and all data related to that endpoint is cleaned up.
You should see that endpoints with no correlated message data will disappear as soon as the first bullet point is resolved. If you need to clear out some data before then please let us know and we'll look into your specific case.
Regards,
Mike Minutillo