Logging & Monitoring

Scottsdale Mint uses structured JSON logging via Wonolog, integrated with AWS CloudWatch in production, and file-based logging locally.

---

Wonolog Logging Stack

Library: Inpsyde Wonolog (Monolog-based WordPress logging) MU Plugin: web/app/mu-plugins/wonolog.php Vendor packages: vendor-static/inpsyde/, vendor-static/monolog/

Configuration

// wonolog.php (mu-plugin)

// Custom SUMA log channel
$channel = new \Monolog\Logger('SUMA');

// Production (Ymir/Lambda): Log to PHP stderr (captured by CloudWatch)
// Development: Log to local file
$handler = \Ymir\isProduction()
    ? new StreamHandler('php://stderr')
    : new StreamHandler(WP_CONTENT_DIR . '/suma.log');

$handler->setFormatter(new JsonFormatter());

$channel->pushHandler($handler);

Minimum Log Level

Controlled by the WONOLOG_DEFAULT_MIN_LEVEL environment variable:

Value	Level	Description
100	DEBUG	All logs (verbose)
200	INFO	Informational messages
250	NOTICE	Notable events
300	WARNING	Default — unexpected conditions
400	ERROR	Runtime errors
500	CRITICAL	Critical conditions
550	ALERT	Immediate action required
600	EMERGENCY	System unusable

Log Format

All logs are structured JSON for easy parsing in CloudWatch Logs Insights:

{
  "message": "Price update failed for product 1234",
  "context": {
    "product_id": 1234,
    "sku": "SM-1OZ-SILVER-BAR",
    "error": "Invalid spot price returned from NFusion"
  },
  "level": 400,
  "level_name": "ERROR",
  "channel": "SUMA",
  "datetime": "2026-03-26T14:30:00.000000+00:00"
}

Using the Logger in Custom Code

The theme and plugins use the \Suma\Logger integration class (via sumatra-logger plugin):

use Suma\Logger;

// Log a warning
Logger::warning( 'Unexpected payment status', [
    'order_id'   => $order_id,
    'status'     => $status,
    'gateway'    => $gateway_id,
] );

// Log an error
Logger::error( 'Kount ENS callback failed', [
    'order_id' => $order_id,
    'response' => $kount_response,
] );

---

Kount Fraud Logging

The Kount-Remove-Unecessary-Logging.patch removes verbose Kount debug output that was flooding logs. Kount fraud decisions are logged at the WARNING level when an order is declined, and at INFO when approved.

Kount logs are stored in: /uploads/kount_logs.log (local development)

---

NewRelic APM

Plugin: wp-newrelic ^1.3

Features

• Transaction tracing — Full PHP stack traces per request
• Error tracking — PHP exceptions and fatal errors
• Database query analysis — Slow query detection
• External API monitoring — NFusion, Plaid, Klaviyo, Kount call timing
• Custom metrics — Precious metals transaction counts, pricing update frequency

When to Use NewRelic

• Investigating slow page loads
• Tracking down N+1 database queries
• Monitoring Lambda cold start frequency
• Alerting on API timeout spikes (e.g., NFusion pricing timeouts)

---

CloudWatch Logs (Production)

In production, all PHP stderr output (including Wonolog JSON logs) is automatically captured by AWS CloudWatch Logs. Access via the AWS Console or via Ymir:

# Tail Lambda logs for production
ymir logs production --tail

# View recent logs
ymir logs production

Useful CloudWatch Query (Logs Insights)

fields @timestamp, message, context.order_id, context.error
| filter channel = "SUMA" and level >= 400
| sort @timestamp desc
| limit 50

---

WooCommerce Status Logs

WooCommerce has its own built-in logging system accessible at: WP Admin → WooCommerce → Status → Logs

Key log files to check for payment debugging:

• woocommerce-{date}.log — General WC errors
• kount-{date}.log — Kount fraud events
• angelleye_ppcp-{date}.log — PayPal PPCP errors
• cryptowoo-{date}.log — Crypto payment events
• scottsdale-ach-gateway-{date}.log — ACH gateway errors

---

Error Levels by Environment

Environment	PHP Error Reporting	WordPress Debug	Wonolog Level
Local	E_ALL	WP_DEBUG=true, WP_DEBUG_LOG=true	100 (DEBUG)
Development	E_ALL	WP_DEBUG=true	100 (DEBUG)
Staging	E_ERROR	Off	300 (WARNING)
Production	E_ERROR	Off	300 (WARNING)

---

Log Retention Policy

• CloudWatch Logs: Configured in AWS Console (typically 30-90 days for Lambda)
• Local log files: Not automatically rotated — clear manually during development
• WooCommerce logs: Auto-cleaned after 30 days by WooCommerce's scheduled cleanup