| To: | Paul Smith <psmith@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] PCP JMX PMDA |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Thu, 24 Mar 2016 00:33:40 -0400 (EDT) |
| Cc: | pcp developers <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <D9B89914-50FA-4847-9D57-12117B60949B@xxxxxxxxxx> |
| References: | <56D8858A.3020407@xxxxxxxxxx> <56E05862.7040707@xxxxxxxxxx> <282702840.33546644.1458721199633.JavaMail.zimbra@xxxxxxxxxx> <D9B89914-50FA-4847-9D57-12117B60949B@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | DiAlwIor0Pq1EalGTX4Ym8kJQGE18Q== |
| Thread-topic: | PCP JMX PMDA |
----- Original Message ----- > [...] > Stop-the-World-Make-Coffee-and-perhaps-have-some-biscuits; you get values, > likely 'stale'. In the GC paused state, not much is happening in the JVM > _anyway_ so whatever values are available aren't likely to change much > (other than the GC values themselves..) Right - for all counter metrics (the best kind of metrics), those values are still 100% correct. IOW the right thing to do is for tools to report a zero rate-of-change - which, happily, is exactly what happens. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates: python, kenj merge, Nathan Scott |
|---|---|
| Next by Date: | Re: [pcp] Handling Oracle PMDA Latencies, Marko Myllynen |
| Previous by Thread: | Re: [pcp] PCP JMX PMDA, Paul Smith |
| Next by Thread: | Re: [pcp] PCP JMX PMDA, Marko Myllynen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |