Logging Configuration

Overview

TaprNext logs operational events, errors, and debugging information. These settings control what gets logged and in what format.

Configuration

Navigate to Tapr Settings > Other tab > Logging section.

Log Level

Setting	Default	Options
Log Level	INFO	DEBUG, INFO, WARNING, ERROR

Each level includes all messages from more severe levels:

Level	Includes	Use Case
ERROR	Errors only	Production, minimal logging
WARNING	Errors + Warnings	Production, alert on issues
INFO	Errors + Warnings + Info	Standard operation (default)
DEBUG	All messages	Troubleshooting, development

What each level logs:

ERROR: Failed API calls, extraction failures, database errors, integration failures

WARNING: Rate limit approaches, slow operations, deprecated feature usage, recoverable errors

INFO: Invoice processing events, successful API calls, workflow state changes, user actions

DEBUG: Detailed request/response data, internal state changes, performance metrics, step-by-step processing details

Log Format

Setting	Default	Options
Log Format	text	text, json

Text Format: Human-readable format suitable for manual review

• Use for: Manual log review, development and testing, simple troubleshooting

JSON Format: Structured format for log aggregation tools

• Use for: Log aggregation (ELK, Splunk, Datadog), automated alerting, analytics, production environments

Accessing Logs

Frappe Logs

TaprNext logs are written to Frappe’s standard log locations:

~/frappe-bench/logs/
frappe.log        # General Frappe logs
worker.log        # Background job logs
scheduler.log     # Scheduled task logs

Filtering TaprNext Logs

# View TaprNext-specific logs
grep "taprnext" ~/frappe-bench/logs/frappe.log

# View recent errors
grep "ERROR.*taprnext" ~/frappe-bench/logs/frappe.log | tail -50

# Watch logs in real-time
tail -f ~/frappe-bench/logs/frappe.log | grep "taprnext"

Log Rotation

Frappe automatically rotates logs. Configure rotation in common_site_config.json:

{
  "logging": {
    "max_bytes": 10485760,
    "backup_count": 5
  }
}

Troubleshooting with Logs

Enable Debug Temporarily

For troubleshooting specific issues:

1. Set Log Level to DEBUG
2. Reproduce the issue
3. Review logs for detailed information
4. Return Log Level to INFO

Performance Note: DEBUG logging significantly increases log volume. Don’t leave it enabled in production.

Common Log Patterns

• AI Extraction Issues: grep "taprnext.ai" ~/frappe-bench/logs/frappe.log
• Intake Channel Problems: grep "taprnext.intake" ~/frappe-bench/logs/frappe.log
• ERP Integration Errors: grep "taprnext.adapters" ~/frappe-bench/logs/frappe.log
• Approval Workflow: grep "taprnext.workflow" ~/frappe-bench/logs/frappe.log

Configuration Reference

Field	Type	Default	Description
log_level	Select	INFO	Minimum severity to log
log_format	Select	text	Output format (text or JSON)

Best Practices

Production Settings

Setting	Value	Rationale
Log Level	INFO or WARNING	Balance visibility and volume
Log Format	json	Enables log aggregation and alerting

Development Settings

Setting	Value	Rationale
Log Level	DEBUG	Maximum visibility for development
Log Format	text	Easier to read during development

Log Monitoring

Set up alerts for:

• ERROR level logs (immediate attention)
• High frequency of WARNING logs (potential issues)
• Specific patterns (integration failures, rate limits)

Log Retention

Consider compliance requirements:

• Financial regulations may require log retention
• Include logs in backup procedures
• Define log retention policy