DoubleTie Logger Troubleshooting
Solutions for common issues when using DoubleTie Logger.
Troubleshooting
This page provides solutions for common issues you might encounter when using DoubleTie Logger.
Logs Not Appearing
If your logs aren't showing up as expected, check these potential causes:
1. Check your configured log level
The logger only shows messages at or above the configured level:
Solution: Adjust your log level to match your needs:
2. Verify the logger isn't disabled
Solution: Make sure to check if you've disabled logging:
3. Ensure custom log handlers are correctly implemented
Solution: Verify your custom log handler is actually emitting logs somewhere.
TypeScript Errors
If you encounter TypeScript errors when using the logger:
1. Import the types you need
2. For extending loggers with custom methods
Circular References
If you encounter issues with circular objects in your logs:
Solution: Use a JSON-safe version for logging:
Next.js Redirection Issues
If you're having trouble redirecting Next.js logs:
1. Timing issues
Solution: Delay the redirection or retry if it fails:
2. Different behavior on client and server
Solution: Handle client and server differently:
Custom Formatters Not Applied
If your custom formatters aren't being applied:
Solution: Specify the formatter in your logger configuration:
Performance Issues
If logging is causing performance issues:
1. Consider disabling lower-priority logs in production
2. Lazy evaluation for expensive operations
3. Disable logging entirely for performance-critical paths
Result Pattern Issues
If you're experiencing issues with the Result pattern integration: