Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/395
So now I'm thinking about changes to the Profiler Client API based on those
usage scenarios.
For the **Live Data** use case, the existing `PROFILE_GET(profile, entity,
look-back)` function should work just fine. I think this is the most simple
function signature to use in this case.
For the **Replayed Data** use case, the existing `PROFILE_GET` signature is
not going to work. To query the Profiler for replayed data, we need one or
both of the following functions. Or maybe there is a better function signature
that I'm not thinking of.
#### PROFILE_GET_RANGE
Return the measurements taken for a profile and entity between a range of
time defined by a start and end.
The only problem here is how do I make it easy for the user to specify a
timestamp? Do I have to accept a number of different formats and try to coerce
to a timestamp? What formats should I accept?
```
PROFILE_GET_RANGE(profile, entity, start timestamp, end timestamp)
```
#### PROFILE_GET_FROM
Return the measurements taken for a profile and entity starting from a
point in time, the offset, and looking back from that offset. This might seem
initially hard to grok, but also might seem easier to use once you have your
mind wrapped around it. This follows closely the existing `PROFILE_GET`
function signature.
```
PROFILE_GET_FROM(profile, entity, look-back, offset)
```
For example, I replayed data that I know is 2 months old and now I need to
look at that data. I am interested in a 15 minute window from a profile that I
know is offset by 2 months.
```
PROFILE_GET_FROM('replayed-profile', '10.0.0.1', 15, "MINUTES", 2, "MONTHS")
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
