metron-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (METRON-1925) Provide Verbose View of Profile Results in REPL
Date Thu, 06 Dec 2018 22:30:00 GMT

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

ASF GitHub Bot commented on METRON-1925:
----------------------------------------

Github user nickwallen commented on the issue:

    https://github.com/apache/metron/pull/1292
  
    > The underlying logic seems like it should be nearly identical. Is there any common
functionality that could be pulled out and shared between the two?
    
    All of the heavy lifting was already done by the HBaseProfilerClient.  So they already
share a common implementation through that.  And that is why you don't see a ton of change
needed in `PROFILE_GET`.


> Provide Verbose View of Profile Results in REPL
> -----------------------------------------------
>
>                 Key: METRON-1925
>                 URL: https://issues.apache.org/jira/browse/METRON-1925
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Nick Allen
>            Assignee: Nick Allen
>            Priority: Major
>
> When viewing profile measurements in the REPL using PROFILE_GET, you simply get back
a list of values. It is not easy to determine from which time period the measurements were
taken.
> For example, are the following values all sequential?  Are there any gaps in the measurements
taken over the past 30 minutes?  When was the first measurement taken?
> {code:java}
> [Stellar]>>> PROFILE_GET("hello-world","global",PROFILE_FIXED(30, "MINUTES"))
> [2655, 1170, 1185, 1170, 1185, 1215, 1200, 1170]{code}
> The `PROFILE_GET` function was designed to return values that serve as input to other
functions.  It was not designed to return values in a human-readable form that can be easily
understood.
> We need another way to query for profile measurements in the REPL that gives me a better
understanding of the profile measurements.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message