You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Ari Rabkin (JIRA)" <ji...@apache.org> on 2008/08/04 17:48:44 UTC

[jira] Reopened: (HADOOP-3772) Proposed hadoop instrumentation API

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

Ari Rabkin reopened HADOOP-3772:
--------------------------------


Whups, conf file part of patch was slightly wrong

> Proposed hadoop instrumentation API
> -----------------------------------
>
>                 Key: HADOOP-3772
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3772
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: metrics
>            Reporter: Ari Rabkin
>            Assignee: Ari Rabkin
>             Fix For: 0.19.0
>
>         Attachments: instrumentation-2.patch, instrumentation-3.patch, instrumentation-4.patch, instrumentation.patch, tweak_inst.patch
>
>
> We want to evolve the Hadoop metrics subsystem into a more generic Instrumentation facility.  The ultimate goal is to add structured logging to Hadoop, with causal tags, a la X-trace.  The existing metrics framework is not quite suitable for our needs, since the implementation and interface are tightly coupled. There's no way to use the metrics instrumentation points for anything other than metricss, and there's no way for a metrics context to find out what event just happened.  
> We want to tease apart the generic notion of hookable instrumentation points, from the specifics of the information recording. The latter ought to  be pluggable at run-time.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.