atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-519) metrics
Date Thu, 25 Feb 2016 04:44:18 GMT

    [ https://issues.apache.org/jira/browse/ATLAS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166724#comment-15166724
] 

Hemanth Yamijala commented on ATLAS-519:
----------------------------------------

Big +1 for this. To start with we can probably focus on system metrics and KPIs - like number
of metadata objects being indexed, number of operations, time for operations etc. A pluggable
framework for the metrics system so that they can be published to different systems (like
the Hadoop metrics capability) would be desirable, IMO.

> metrics
> -------
>
>                 Key: ATLAS-519
>                 URL: https://issues.apache.org/jira/browse/ATLAS-519
>             Project: Atlas
>          Issue Type: Wish
>    Affects Versions: trunk
>            Reporter: Nigel Jones
>
> Metadata is crucial in an enterprise. Atlas can increasingly store a wide variety of
metadata for the organization, and this may well be within a cloud type environment (be it
on-prem or public cloud).
> Usage/performance metrics are needed in atlas to
> * Better understand how atlas is being used, to identify areas for improvement
> * understand performance characteristics and capacity planning
> * allow in future for usage oriented billing & QOS.
> * aid in debugging
> Opening this as a discussion focal point to think about what infrastructure may be needed,
and the kind of metrics that might make sense.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message