We recently had an incident where replcation to several subscriptions stopped and no alarms went off in either SQL Server or Spotlight. We only found out a couple of days after the fact when we started to notice reports not producting expected results.
When this happened, the only indication of a problem was one or both of the following messages in the Distributor To Subscriber History tab of the Subscription properties window of Replication Monitor:
TCP Provider: An existing connection was forcibly closed by the remote host.
and/or
The initial snapshot for publication 'MyPublication' is not yet available.
When this happens however, according to Repliction Monitor, the Performance for each Subscription in the Subscription Watch List is Execellent.
How can I configure Spotlight to capture these events so that if this ever happens again we will know before the users do?