metron-issues mailing list archives

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


ASF GitHub Bot commented on METRON-1925:

Github user mmiklavc commented on the issue:
    This seems pretty useful, thanks for the submission @nickwallen.
    > For lack of a better name, I just called it PROFILE_VIEW. I would be open to alternatives.
I did not want to add additional options to the already complex PROFILE_GET.
    Heh, that was going to be my first question. I think simplifying the client-facing function
signatures, as you've done, makes sense. I don't see any modifications to the existing PROFILE_GET
function, though. 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?

> Provide Verbose View of Profile Results in REPL
> -----------------------------------------------
>                 Key: METRON-1925
>                 URL:
>             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
> 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
> 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

View raw message