[
https://issues.apache.org/jira/browse/OOZIE-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559447#comment-14559447
]
Robert Kanter commented on OOZIE-2251:
--------------------------------------
That patch appears to be related to yarn tags; I think you uploaded the wrong
one?
In any case, OOZIE-1817 added an implementation of the instrumentation that
uses Codahale Metrics (which looks like it's the Dropwizard metrics):
https://dropwizard.github.io/metrics/3.1.0/
Their disabled by default because their output formatting is slightly different
than the original instrumentation, but you can enable them by following the
docs here:
http://oozie.apache.org/docs/4.1.0/AG_Install.html#Using_Metrics_instead_of_Instrumentation
We're currently only exposing a JSON reporter from Codahale, but if you want to
add better integration with graphite or ganglia, it looks like it should be
pretty easy to add some code and oozie-site configs that do this:
https://dropwizard.github.io/metrics/3.1.0/manual/ganglia/#manual-ganglia
https://dropwizard.github.io/metrics/3.1.0/manual/graphite/#manual-graphite
> Expose instrumental matrices in Realtime Graphing tool
> ------------------------------------------------------
>
> Key: OOZIE-2251
> URL: https://issues.apache.org/jira/browse/OOZIE-2251
> Project: Oozie
> Issue Type: New Feature
> Components: monitoring
> Reporter: Jaydeep Vishwakarma
> Assignee: Jaydeep Vishwakarma
> Attachments: OOZIE-2243-v0.patch
>
>
> We have been logging so many important matrices in oozie-instrumentation.log
> . These information is very useful for oozie functional monitoring. But it is
> always difficult to get the meaning from flat file. If we expose this
> information on some graphing tool, We can get the lot of meaning out of it
> and can take some actions based on it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
