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

ASF GitHub Bot commented on STORM-954:
--------------------------------------

Github user arunmahadevan commented on a diff in the pull request:

    https://github.com/apache/storm/pull/673#discussion_r37722401
  
    --- Diff: storm-core/src/clj/backtype/storm/daemon/nimbus.clj ---
    @@ -1159,6 +1161,18 @@
               (check-authorization! nimbus storm-name topology-conf 
"deactivate"))
             (transition-name! nimbus storm-name :inactivate true))
     
    +      (debug [this storm-name component-id enable?]
    +        (let [storm-cluster-state (:storm-cluster-state nimbus)
    +              storm-id (get-storm-id storm-cluster-state storm-name)
    +              topology-conf (try-read-storm-conf conf storm-id)
    +              storm-base-updates (assoc {} :component->debug (if (empty? 
component-id) {storm-id enable?} {component-id enable?}))]
    +          (check-authorization! nimbus storm-name topology-conf "debug")
    +          (when-not storm-id
    +            (throw (NotAliveException. storm-name)))
    +          (log-message "Nimbus setting debug to " enable? " for storm-name 
" storm-name " storm-id " storm-id)
    --- End diff --
    
    Thanks @Parth-Brahmbhatt, missed it. Will log component-id as well.


> Toplogy Event Inspector
> -----------------------
>
>                 Key: STORM-954
>                 URL: https://issues.apache.org/jira/browse/STORM-954
>             Project: Apache Storm
>          Issue Type: Improvement
>            Reporter: Sriharsha Chintalapani
>            Assignee: Arun Mahadevan
>
> •Ability to view tuples flowing through the topology
> •Ability to turn on/off debug events without having to stop/restart topology
> •Default debug events is off
> •User should be able to select a specific Spout or Bolt and see incoming 
> events and outgoing events
> •We could put a configurable numbers of events to view (e.g. last 100 events 
> or last 1 minute)
> •Tuple stream to have following info
> •Message id, batch/transaction id, name/value pair, timestamp, acked (boolean)
> •All the above to be available from Storm UI



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to