The techniques discussed in this section apply to debugging a service in both Symphony DE and Symphony.
The following diagram describes the overall process to follow to debug a service.
You can use the service event replay logs to try to reproduce your problem—you replay the relevant service events that occurred on the service instance.
You should be able to catch the most common service problems using this mode, particularly problems that are isolated (non-cumulative). If you cannot reproduce your problem in this mode, try debugging your service using the full service replay debugging.
Consider moving your application into production with customized service replay debugging enabled. You can test your service thoroughly in a grid environment until your service no longer produces service event replay logs in testing. Therefore any service replay debug logs generated in production reflect new problems (i.e. those that did not arise in testing).
Full service replay debugging generates service event replay logs for every service instance in your cluster, regardless of whether an error occurs in that service instance.
You can use the service event replay logs to try to reproduce your problem—you replay the service events that occurred on the service instance.
You should be able to use this mode to catch problems that are cumulative. For example, this mode may help you to find that your service memory becomes more and more corrupted at each task invocation. You would also use full service replay debugging if your service problem does not generate a SERL in customized mode, or if you cannot reproduce the problem using customized service replay debugging.
If you cannot reproduce your problem using either customized or full service replay debugging, try debugging your service using live service debugging.
Live service debugging allows you to debug your service instance as it is running live.
This mode gives you an exact picture of the runtime environment, not just a simulated environment.
If you still cannot reproduce your service problem using this mode, try debugging your service using ad hoc service debugging.