sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lenni Kuff (JIRA)" <>
Subject [jira] [Commented] (SENTRY-477) Sentry service should expose metrics
Date Sat, 18 Oct 2014 15:39:33 GMT


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:

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:
>             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

View raw message