You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "radford nguyen (Jira)" <ji...@apache.org> on 2019/08/30 23:55:00 UTC
[jira] [Created] (IMPALA-8914) Collect and publish QueryEventHook
metrics
radford nguyen created IMPALA-8914:
--------------------------------------
Summary: Collect and publish QueryEventHook metrics
Key: IMPALA-8914
URL: https://issues.apache.org/jira/browse/IMPALA-8914
Project: IMPALA
Issue Type: Improvement
Components: Backend, Frontend
Reporter: radford nguyen
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
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org