Webhook Logging And Monitoring

Webhook Logging and Monitoring

Understanding what's happening with your webhooks is crucial for maintaining reliable integrations. The webhook catcher provides comprehensive logging and monitoring tools to track webhook activity, troubleshoot issues, and ensure data flows correctly.

Understanding Webhook Logs

Every webhook request is logged, whether it succeeds or fails. Logs help you:

• Verify webhooks are receiving data
• Troubleshoot errors and failures
• Monitor webhook performance
• Audit data changes
• Understand what data external services are sending

Viewing Webhook Logs

To access logs for a specific webhook:

1. Open the webhook from your dashboard
2. Navigate to the "Logs" or "Call History" tab
3. Browse the list of webhook calls

Each log entry shows:

• Timestamp: When the request was received
• Status: Success, Failed, or Processing
• Records Created/Updated: Number of records affected
• Processing Time: How long it took to process
• Error Details: If the call failed, why it failed

Log Detail View

Click on any log entry to see detailed information:

Request Information

• Incoming Payload: The complete JSON/data sent by the external service
• Request Headers: HTTP headers included in the request
• Source IP Address: Where the request came from
• User Agent: Application that sent the request

Processing Information

• Processing Steps: For multi-step webhooks, see each step's results
• Field Mappings: What data was mapped to which fields
• Records Created: Links to the actual records created in your app
• Validation Results: Whether validation rules passed or failed

Response Information

• Response Sent: What your webhook returned to the external service
• Status Code: HTTP status code (200 for success, 400/500 for errors)
• Response Time: Total processing duration

Understanding Log Status

Success

The webhook processed successfully and created/updated records as expected.

• Green indicator
• Shows number of records affected
• All validation passed

Failed

The webhook encountered an error and could not complete processing.

• Red indicator
• Includes error message
• No records were created/updated
• Can be retried

Partial Success

For multi-value webhooks, some records succeeded while others failed.

• Yellow/orange indicator
• Shows count of successful vs failed records
• Can retry only the failed records

Processing

The webhook is currently being processed (usually only visible for slow operations).

• Blue indicator
• Shows progress if available
• Will update to Success or Failed when complete

Common Error Messages

Field Mapping Errors

• "Field not found" - The incoming data doesn't contain the expected field
• "Invalid field value" - Data type doesn't match field requirements
• "Required field missing" - A required field has no value

Authentication Errors

• "Invalid API credentials" - App connection credentials are incorrect
• "App not found" - Connected app was deleted or is inactive
• "Permission denied" - API credentials lack necessary permissions

Security Errors

• "IP address blocked" - Request came from unauthorized IP
• "Signature verification failed" - Webhook signature is invalid
• "Unauthorized host" - Request host not in allowlist

Validation Errors

• "Validation failed" - One or more validation rules were not met
• "Duplicate record" - Record already exists (if duplicate prevention enabled)

Retrying Failed Webhooks

When a webhook fails, you can retry it after fixing the underlying issue.

How to Retry

1. Open the failed webhook call log
2. Review the error to understand what went wrong
3. Fix the issue (update field mappings, fix app credentials, etc.)
4. Click "Retry" or "Reprocess"
5. The webhook will process again with the same original payload

Partial Retry for Multi-Value Webhooks

For webhooks that process multiple records, you can retry only the failed records:

1. Open the partially failed webhook call
2. Review which specific records failed
3. Select only the failed records
4. Click "Retry Selected"

Retrying processes the original incoming data. If the external service's data has changed, you'll still get the original values.

Automatic Retry

For certain types of temporary errors (network issues, temporary API problems), the system may automatically retry failed webhooks a few times before marking them as permanently failed.

Webhook Reports

The reporting dashboard provides an overview of all webhook activity.

Accessing Reports

1. Navigate to "Reports" or "Dashboard"
2. Select your date range
3. View aggregated statistics

Report Metrics

• Total Calls: Number of webhook requests received
• Success Rate: Percentage of successful vs failed calls
• Failed Calls: Count of failed requests
• Records Created: Total records added to your app
• Records Updated: Total records modified
• Average Processing Time: How long webhooks take to process

Filtering Reports

Filter reports by:

• Date range (today, last 7 days, last 30 days, custom)
• Specific webhook
• Status (all, success, failed)
• Connected app

Report Visualization

Reports include charts and graphs showing:

• Webhook activity over time
• Success vs failure trends
• Most active webhooks
• Peak usage times

Email Notifications

Stay informed about webhook issues with automatic email notifications.

Failure Notifications

Receive emails when webhooks fail to process.

Setting Up Failure Notifications

1. Go to your profile settings
2. Navigate to "Notification Settings"
3. Enable "Webhook Failure Notifications"
4. Choose notification frequency:
   • Immediate - Email for every failure
   • Hourly Summary - One email per hour with all failures
   • Daily Summary - One email per day
5. Optionally add additional recipient emails
6. Save settings

Failure Notification Contents

Failure notification emails include:

• Which webhook failed
• When it failed
• Error message
• Link to view full log details
• Quick retry option

Daily Reports

Receive a daily summary of all webhook activity.

Enabling Daily Reports

1. Go to your profile settings
2. Enable "Daily Webhook Reports"
3. Choose report time (e.g., 9:00 AM)
4. Select timezone
5. Save

Daily Report Contents

• Total webhooks received yesterday
• Success count and percentage
• Failed count and percentage
• Most active webhooks
• Any critical errors requiring attention
• Comparison to previous day

Monitoring Best Practices

Regular Review Schedule

• Daily: Check for any failed webhooks from the previous day
• Weekly: Review overall success rates and performance trends
• Monthly: Analyze usage patterns and optimize slow webhooks

Setting Up Alerts

• Enable failure notifications for production webhooks
• Add team members to notification lists
• Use immediate notifications for critical integrations
• Use summaries for less critical webhooks to avoid email overload

Proactive Monitoring

• Monitor success rates - investigate if rate drops below 95%
• Watch processing times - investigate if times increase significantly
• Review error patterns - recurring errors indicate configuration issues
• Check for inactive webhooks - remove or update unused webhooks

Troubleshooting with Logs

Webhook Not Receiving Data

1. Check webhook logs to see if any requests arrived
2. If no logs: Issue is with the external service sending data
3. If logs exist but failed: Review error messages
4. Verify webhook URL is correctly configured in external service

Intermittent Failures

1. Filter logs to show only failures
2. Look for patterns (specific times, specific data patterns)
3. Check if failures coincide with external service issues
4. Review if payload structure is inconsistent

Slow Processing

1. Check processing times in logs
2. Identify if specific steps are slow (for multi-step webhooks)
3. Consider queuing equations instead of running immediately
4. Review if large file attachments are causing delays

Log Retention

Webhook logs are retained based on your plan:

• Logs are kept for a minimum period (typically 30-90 days)
• Archived logs may be available for longer periods
• You can export log data for your own archival

Check your specific plan details for exact log retention periods.

Exporting Log Data

For analysis or record-keeping, you can export webhook logs:

1. Navigate to webhook logs
2. Apply any desired filters
3. Click "Export" or "Download"
4. Choose format (CSV, JSON)
5. Download the export file

Exported data includes all visible columns and can be opened in spreadsheet applications for further analysis.

Performance Metrics

What to Monitor

• Success Rate: Target 98%+ for production webhooks
• Processing Time: Under 2 seconds for simple webhooks, under 10 seconds for complex
• Daily Volume: Track trends to plan for scaling
• Error Rate by Type: Identify most common error types

Performance Optimization

• Use queue mode for equations when immediate calculation isn't needed
• Simplify complex multi-step webhooks if possible
• Reduce unnecessary field mappings
• Optimize validation rules to be efficient
• Consider breaking high-volume webhooks into multiple separate webhooks

Getting Help

When troubleshooting webhook issues:

1. Review the specific log entry and error message
2. Check this documentation for solutions
3. Search the Tadabase community forums
4. Enable support mode and contact Tadabase support with:
   • Webhook ID
   • Specific log entry/call ID showing the issue
   • Description of expected vs actual behavior
   • Any troubleshooting steps already attempted