[ https://issues.apache.org/jira/browse/METRON-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689658#comment-16689658 ]
ASF GitHub Bot commented on METRON-1874: ---------------------------------------- Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/1265 I was also wanting to do a follow-on that would load the parser configuration from Zk instead of requiring you to define that. In some cases, you just want to work with whatever the current 'live' configuration is. > Create a Parser Debugger > ------------------------ > > Key: METRON-1874 > URL: https://issues.apache.org/jira/browse/METRON-1874 > Project: Metron > Issue Type: New Feature > Reporter: Nick Allen > Assignee: Nick Allen > Priority: Major > > Users need a way to test their parser configurations in a controlled > environment. This would allow a user to tweak and test the parser > configuration before deploying it into a live Metron cluster. The user could > also use the REPL to understand why a particular message failed to parse > correctly. > This could follow the pattern of the [Profiler > Debugger|https://github.com/apache/metron/tree/master/metron-analytics/metron-profiler#creating-profiles] > and [Threat Triage > Simulator|https://github.com/apache/metron/tree/master/metron-platform/metron-management#simulate-threat-triage-rules]. > This allows a user to apply canned messages against a configuration and > inspect the output, all within the REPL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)