Monitoring
Monitor VIESUS deployments — result files, error codes, log parsing, GPU metrics, and alerting patterns for on-premise and cloud.
Production observability for VIESUS. This page covers the signals each deployment exposes — per-image result files, structured logs, GPU metrics, and Cloud API events — and the thresholds worth alerting on.
On-premise monitoring
Result files
When WriteResultFiles: 1 is set in viesusini.json, VIESUS writes a .json or .res file alongside each output image. These files contain per-image processing details and are the primary observability signal for on-premise deployments.
Node.js / CLI result JSON:
{
"brightCorrStrength": 0.011,
"colorCorrStrength": 0.083,
"fdApplied": 1,
"ieApplied": 1,
"isArtificial": 0,
"isMonochrome": 0,
"rszApplied": 0,
"arApplied": 1
}All fields are 0 or a float strength value. A result file present means the image processed. A missing result file (when WriteResultFiles: 1) means the enhancement failed.
PDF Enhancer XML report:
Error code 0 = success. Non-zero = partial or complete failure. See PDF Error Codes.
Parsing result files
Check for CLI/Node.js errors (bash):
Parse PDF XML reports:
Node.js module logging
Log both enhancement time and wall-clock time per job to detect pool saturation:
In the main thread:
Structured JSON logs integrate cleanly with log aggregators (Datadog, Loki, CloudWatch).
Key metrics to track:
enhanceMs p95
2× baseline — indicates degraded performance
wallMs - enhanceMs
> 5 sec — pool is saturated (jobs queuing)
Error rate
> 1% — investigate error codes
Queue depth
Monitor pool.queueSize if exposed by pool library
GPU monitoring
Check GPU utilization and VRAM usage alongside VIESUS metrics:
Expected values during active GPU processing:
GPU utilization
80–100%
VRAM used
4–8 GB per active worker
Temperature
< 85°C (thermal throttling above)
License expiry monitoring
When a license expires, VIESUS stops enhancing — images pass through unchanged (output = input). Check license validity directly with the CLI's -I flag rather than inferring it from output:
Run this check daily via cron and alert on a non-zero exit code.
Cloud API monitoring
Credit balance
Poll credit balance to detect approaching depletion:
Enhancement failure rate
Track error rates from webhook events:
Webhook delivery failures
Query webhook logs regularly to catch failed deliveries:
Alerting recommendations
Enhancement error rate
> 2% over 15 min
High
Pool saturation
wallMs - enhanceMs > 10 sec p95
High
License invalid / expired
viesus -I exits non-zero or reports invalid
Critical
Low credits
< 500 remaining
High
GPU temperature
> 85°C
High
Webhook failures
> 5 consecutive failed deliveries
Medium
Last updated
Was this helpful?
