- 2 minutes to read

Release Notes

Nodinite WCF Diagnostics tracing Troubleshooting and FAQ

This troubleshooting and FAQ guide helps you resolve common WCF Diagnostics Tracing issues quickly.

I can't see my events, why?

There can be many reasons for that:

Check Pickup service

Is the Pickup Log Events Service Logging Agent really running?

If the Pickup Service has been stopped for a long time, it may take a while to catch up, try widening your timespan.

Check output folder

Are there trace files in the output folder?

Yes: Then either the Pickup Log Events Service Logging Agent has a problem accessing the Log API or even simpler it is not running. If the Log API is available and the service is running, there might be a problem with access rights. Please review security settings detailed in the Prerequisites user guide.

Pickup Log Events Service Logging Agent

Pro Tip: Work Proactively with Non-Events Monitoring

Don't wait for failures—detect silent problems before they escalate. While WCF Diagnostics Tracing captures transaction failures, Non-Events Monitoring alerts you when expected WCF traffic stops arriving.

Why This Matters

  • Silent failures - WCF service crashes without error messages
  • Configuration issues - Endpoints disabled, bindings misconfigured
  • Network problems - Firewall rules blocking traffic, DNS failures
  • Dependency failures - Database down, external API unavailable

How It Works

  1. Set expected message volume thresholds (e.g., "min 50 Order requests/hour during business hours")
  2. Configure alerts when volume drops below threshold
  3. Get notified before customers report issues

Example

Your Order Processing WCF service normally receives 200 requests/hour. Non-Events alert triggers at 11:15 AM when only 20 requests logged in past hour. Investigation reveals database connection pool exhaustion—fixed before lunch rush begins.

Learn more about Non-Events Monitoring - Catch silent failures proactively

Next Steps