Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-8914

Collect and publish QueryEventHook metrics

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Backend, Frontend
    • Labels:
      None
    • Epic Color:
      ghx-label-13

      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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                radford-nguyen radford nguyen
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: