[
https://issues.apache.org/jira/browse/SENTRY-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176042#comment-14176042
]
Lenni Kuff commented on SENTRY-477:
-----------------------------------
This is really cool [~sravya] and IMO looks like the correct approach. In
addition to timing, you could also consider adding some aggregate metrics such
as total #of roles, total #of privileges, etc. Another area to consider is JVM
metrics to expose information on memory usage / garbage collection. There are
APIs you can use to gather this info. For example, see:
{{http://docs.oracle.com/javase/7/docs/api/java/lang/management/ManagementFactory.html#getMemoryPoolMXBeans()}}
The JVM metrics are probably something that can be done as a follow on change
once we have the initial framework in place.
> Sentry service should expose metrics
> ------------------------------------
>
> Key: SENTRY-477
> URL: https://issues.apache.org/jira/browse/SENTRY-477
> Project: Sentry
> Issue Type: New Feature
> Affects Versions: 1.4.0
> Reporter: Sravya Tirukkovalur
> Assignee: Sravya Tirukkovalur
> Fix For: 1.5.0
>
> Attachments: SENTRY-477.WIP.1.patch, SENTRY-477.WIP.patch,
> metrics.png, metrics_main.png, ping.png, threads.png
>
>
> It would be good to have Sentry service expose some metrics for both
> performance testing and monitoring purposes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
