You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@nutch.apache.org by "Lewis John McGibbney (Jira)" <ji...@apache.org> on 2026/01/08 21:00:00 UTC

[jira] [Work started] (NUTCH-3142) Add Error Context to Metrics

     [ https://issues.apache.org/jira/browse/NUTCH-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on NUTCH-3142 started by Lewis John McGibbney.
---------------------------------------------------
> Add Error Context to Metrics
> ----------------------------
>
>                 Key: NUTCH-3142
>                 URL: https://issues.apache.org/jira/browse/NUTCH-3142
>             Project: Nutch
>          Issue Type: Sub-task
>          Components: metrics
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>            Priority: Major
>             Fix For: 1.22
>
>
> Current error metrics lack granularity. While protocol status codes are tracked dynamically, there's no categorization of:
>  * HTTP error codes (4xx vs 5xx)
>  * Exception types (timeout, connection refused, DNS failure)
>  * Parse failure reasons
> This makes it difficult to diagnose crawl issues from metrics alone e.g. necessitating the interrogation of logs, adding complexity to troubleshooting. 
> This ticket will add new error context metrics for FetcherThread, ParseSegment and IndexerMapReduce. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)