Overview Getting Started Examples Smart Alerts API Documentation CI/CD Integration Troubleshooting FAQ

Troubleshooting Guide

Common Issues

Possible Causes:
  • Incorrect token in the URL
  • Network connectivity issues
  • Firewall blocking outbound connections
  • SSL/TLS certificate issues
Solutions:
  1. Verify the token: Copy the exact token from your dashboard
  2. Test manually: Try the check-in URL in your browser
  3. Check connectivity: 
    curl -v "https://silentcanary.com/checkin/YOUR_TOKEN"
  4. Verify SSL: Use -k flag to bypass SSL validation temporarily
  5. Check logs: Look at your application/script logs for HTTP errors

Common Reasons:
  • Grace period is too short
  • Check-in interval doesn't match actual process timing
  • Process has variable execution time
  • Smart Alerts sensitivity is too high
Solutions:
  1. Increase grace period: Add buffer for normal timing variation
  2. Adjust interval: Match your actual process frequency
  3. For variable timing: Enable Smart Alerts to learn patterns
  4. Monitor timing: Check canary logs to understand actual patterns

Check These Items:
  1. Email address: Verify it's correct in canary settings
  2. Spam folder: Check your spam/junk mail folder
  3. Email verification: Ensure your account email is verified
  4. Alert type: Confirm alert type includes 'email' or 'both'
If Still Not Working:
  • Try a different email address
  • Check canary logs for notification status
  • Contact support if the issue persists

Webhook Issues:
  1. Verify webhook URL: Test it manually: 
    curl -X POST YOUR_WEBHOOK_URL -H 'Content-type: application/json' -d '{"text":"Test message"}'
  2. Check Slack app: Ensure the webhook is still active in your Slack workspace
  3. Channel permissions: Verify the webhook can post to the target channel
  4. Alert configuration: Confirm alert type includes 'slack' or 'both'

Requirements:
  • At least 3 successful check-ins in learning period
  • Some consistency in check-in patterns
  • Smart Alerts must be enabled
Solutions:
  1. Check data: Verify you have enough check-in history
  2. Increase sensitivity: Try 80-90% for more detection
  3. Re-learn patterns: Use the "Re-learn Patterns" button
  4. Review patterns: Check if your process has learnable patterns

Common Causes:
  • Check-in code not being executed
  • HTTP request failing silently
  • Process running but not completing successfully
  • Network issues preventing check-ins
Debugging Steps:
  1. Add logging: Log before and after check-in attempts
  2. Test check-in URL: Manually verify it works
  3. Check error handling: Ensure failures don't prevent check-ins
  4. Review timing: Verify process completes within expected timeframe

Diagnostic Commands

Test Check-in Manually
# Simple GET test
curl "https://silentcanary.com/checkin/YOUR_TOKEN"

# POST with message
curl -X POST "https://silentcanary.com/checkin/YOUR_TOKEN" \
     -d "message=Manual test check-in"

# With verbose output for debugging
curl -v "https://silentcanary.com/checkin/YOUR_TOKEN"
Test Network Connectivity
# Test DNS resolution
nslookup silentcanary.com

# Test basic connectivity
ping silentcanary.com

# Test HTTPS connection
openssl s_client -connect silentcanary.com:443
Debug Script Issues
# Add debugging to your scripts
set -x  # In bash scripts
curl -v ... # For verbose HTTP output
python -u script.py  # Unbuffered Python output

Performance Optimization

Reduce Check-in Latency
  • Use connection keep-alive in HTTP clients
  • Set appropriate timeouts (5-10 seconds recommended)
  • Consider using fire-and-forget patterns for non-critical check-ins
Handle Network Failures
# Example retry logic in bash
for i in {1..3}; do
    if curl -m 10 "https://silentcanary.com/checkin/YOUR_TOKEN"; then
        break
    else
        echo "Check-in attempt $i failed, retrying..."
        sleep 5
    fi
done
Optimize for High-Frequency Monitoring
  • Use connection pooling
  • Consider HTTP/2 if available
  • Batch multiple status updates if possible
  • Use async HTTP clients where appropriate

Getting Help

Before Contacting Support
  1. Check this troubleshooting guide
  2. Review your canary logs in the dashboard
  3. Test your check-in URL manually
  4. Verify your configuration settings
Information to Include
  • Canary name and approximate creation date
  • Error messages or unexpected behavior description
  • Steps you've already tried
  • Your environment (OS, programming language, etc.)
  • Sample code that's not working (remove sensitive data)
Support: For issues not covered here, please contact support with the above information for faster resolution.