Overview
S4Kit logs every request made through the platform, providing a complete audit trail for monitoring, debugging, and compliance.Log Information
Each log entry captures:Viewing Logs
Dashboard
- Navigate to Logs
- View the log stream
- Click on any entry for details
Filtering
Filter logs by:Search
Search logs by:- Request ID
- Entity name
- Error message
- Path
Log Details
Click on a log entry to see full details:Error Tracking
Error Logs
Filter for errors:- Set Status filter to “Error”
- View failed requests
- Check error details
Error Information
Error logs include:Common Errors
Performance Monitoring
Response Times
Monitor performance with timing data:- Total Time: End-to-end request duration
- SAP Time: Time spent in SAP
- Proxy Time: S4Kit overhead
Identifying Slow Requests
- Sort by response time
- Look for patterns:
- Specific entities
- Large result sets
- Complex filters
Optimization Tips
For slow requests:- Use
$selectto limit fields - Add
$topto limit results - Optimize
$filterexpressions - Use pagination instead of fetching all
Log Retention
Retention Period
Logs are retained based on your plan:Exporting Logs
Export logs for compliance or analysis:- Set your filters
- Click Export
- Choose format (JSON, CSV)
- Download the file
Using Request IDs
Every request has a unique ID for correlation:In SDK Errors
In Support Requests
When reporting issues:- Note the request ID
- Include timestamp
- Describe expected vs actual behavior
- Share the request ID with support
Webhooks (Coming Soon)
Log webhooks are planned for a future release.
- SIEM integration
- Custom monitoring
- Alert systems
Best Practices
Regular Review
- Check error rates daily
- Monitor response times
- Look for unusual patterns
Alerting
Set up alerts for:- Error rate spikes
- Response time degradation
- Rate limit hits
Compliance
For audit requirements:- Export logs regularly
- Store exports securely
- Document retention policies