consider JMX for monitoring crawling status

Bug #667002 reported by siznax
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Archive Widecrawl
Confirmed
Medium
siznax

Bug Description

currently, the de facto crawling status page uses the H3 REST API to get state, elapsed, downloaded, etc.

the same information should be available through JMX. perhaps this is a better source.

in particular, attempting to fetch "discovered" from the frontier-summary-report via REST API often fails. (this shows up as "~" in the current status table)

Tags: telemetry
siznax (siznax)
Changed in archivewidecrawl:
importance: Undecided → Medium
status: New → Confirmed
assignee: nobody → siznax (siznax)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.