[
https://issues.apache.org/jira/browse/METRON-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Allen updated METRON-1699:
-------------------------------
Attachment: Screen Shot 2018-07-27 at 11.07.33 AM.png
> Create Batch Profiler
> ---------------------
>
> Key: METRON-1699
> URL: https://issues.apache.org/jira/browse/METRON-1699
> Project: Metron
> Issue Type: Improvement
> Reporter: Nick Allen
> Assignee: Nick Allen
> Priority: Major
> Attachments: Screen Shot 2018-07-27 at 10.55.27 AM.png, Screen Shot
> 2018-07-27 at 11.07.33 AM.png
>
>
> Create a Batch Profiler that satisfies the following use cases.
> h3. Use Cases
> * As a Security Data Scientist, I want to understand the historical behaviors
> and trends of a profile that I have created so that I can determine if I have
> created a feature set that has predictive value for model building.
> * As a Security Data Scientist, I want to understand the historical behaviors
> and trends of a profile that I have created so that I can determine if I have
> defined the profile correctly and created a feature set that matches reality.
> * As a Security Platform Engineer, I want to generate a profile using
> archived telemetry when I deploy a new model to production so that models
> depending on that profile can function on day 1.
> h3. Goal
> * Currently, a profile can only be generated from the telemetry consumed
> *after* the profile was created.
> * The goal would be to enable “profile seeding” which allows profiles to be
> populated from a time *before* the profile was created.
> * A profile would be seeded using the telemetry that has been archived by
> Metron in HDFS.
> * A profile consumer should not be able to distinguish the “seeded” portion
> of a profile.
> !Screen Shot 2018-07-27 at 10.55.27 AM.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
