Metrics

metrics explains how each page was processed. It is useful for troubleshooting, quality monitoring, and performance analysis.

Common fields

Returned fields may vary slightly by document and processing path, but common metrics usually include:

Field	Meaning
page	Page number
dpi	Effective or detected processing resolution
angle	Page skew or correction angle
duration / cost_time	Processing time for the page
width / height	Page image dimensions
status	Processing status for the page

Why these fields matter

• Low dpi often correlates with weaker OCR quality
• A non-zero angle means the page required rotation correction
• A high duration often indicates dense tables, large images, or complex layouts
• Abnormal status values help you isolate failing pages quickly

Recommended usage

• Review metrics together with result.pages during quality analysis
• Aggregate duration values for page-level performance monitoring
• Record failing page numbers together with x_request_id for retries and support cases

Troubleshooting tips

• If a few pages have poor text quality, inspect dpi and angle first
• If a whole document is slow, look for oversized image pages or dense table pages
• If only selected pages fail, compare them with the page structure described in Page details