[IMPALA-8914] Collect and publish QueryEventHook metrics

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Backend, Frontend
• Epic Color: ghx-label-13
• Assignee: Unassigned
• Reporter: radford nguyen
• Created: 30/Aug/19 23:54
• Updated: 30/Aug/19 23:56

Description

Metrics around QueryEventHook execution are currently not captured.  It would help debug/diagnosis to capture such metrics as:

• # of times hook execution has been rejected (due to full work queue)
• # of times hook execution has timed out
• # of times hook execution has exceptioned
• # of times hook execution has been requested
• avg time hook execution has spent queued up
• avg time hook execution has taken to execute

All metrics above should be further qualified by the hook implementation class.  The following naming convention is suggested (in respective order):

• query-event-hook.${hook}.num-execution-rejections
• query-event-hook.${hook}.num-execution-timeouts
• query-event-hook.${hook}.num-execution-exceptions
• query-event-hook.${hook}.num-execution-submissions
• query-event-hook.${hook}.mean-queued-time
• query-event-hook.${hook}.mean-execution-time

where ${hook} is the fully-qualified method name of the hook method, e.g. com.acme.impala.hooks.MyImpalaHook.onQueryComplete

Issue Links

• is caused by: IMPALA-8571 Make query-hook-execution more robust and observable