Storm ui display field description

  1. The Storm ui home page is mainly divided into 4 parts: Cluster Summary, Topology summary, Supervisor summary, Nimbus Configuration, as shown in the following figure:

  •  Cluster Summary

Version: storm version number

Nimbus uptime : nimbus uptime

Supervisor : the number of supervisors in the storm cluster

User slots : the number of slots used Free slots: the number of remaining slots

Total slots : The total number of slots (corresponding to the number of ports configured in the supervisor.slots.ports property of the configuration file, the sum of the clusters)

Executors : the number of threads

Tasks : number of tasks

 

  • Topology summary

Name : topology name

Id : The topology id generated by the system

Status : Running status (ACTIVE, INACTIVE, KILLED, REBALANCING)

Uptime : Uptime

Num workers : the number of workers running

Num Exectors : The number of threads that workers are running

Num Tasks : The number of tasks that Excetors ran

 

  • Supervisor summary

Id : The supervisor Id generated by the system

Host : the hostname of the supervisor (host)

Uptime : Uptime

Slots : The number of ports of supervisor

User slots : the number of ports used

 

  • Nimbus Configuration

It is the configuration file information in the nimbus cluster, not explained in detail (the key can be viewed in the storm installation chapter)

 

2 Topology page 

Topology 页面主要分6块:Topology summary,Topology actions,Topology stats,Spouts (All time),Bolts (All time),Topology Visualization,Topology Configuration

 

  •  Topology summary

Same as Topology summary in the home page

 

  • Topology actions

Topology running status, you can manually change the status (ACTIVE, DEACTIVATE, KILLED, Rebalance)

 

  •  Topology stats

Window : Time window, showing the running status of 10m, 3h, 1d and all time

Emitted: emit tuple数

Transferred : The number of transferred tuples, let's talk about the difference from emitted: if a task emits a tuple to two tasks, the number of transferred tuples is twice the number of emitted tuples

complete latency : the average time from spout emitting a tuple to spout ack this tuple

Acked : Number of successful tuples

Failed : Number of failed tuples

 

  • Spouts (All time)

Id: spout id

Executors : the number of threads

Emitted: emit tuple数

Transferred :  transferred tuple数,

complete latency : the average time from spout emitting a tuple to spout ack this tuple

Acked : Number of successful tuples

Failed : Number of failed tuples

Error Host : The machine where the error occurred

Error Port : the port number where the error occurred

last error : the number of recent errors

 

  • Bolts (All time)

Execute latency(ms) : The average time for the bolt to execute the execute method

Executed : number of tuple processed

Process latency(ms) : The average time from when the bolt receives a tuple to the bolt ack tuple . If the Acker mechanism is not enabled, the value of Process latency is 0.

Note: The other fields have been mentioned above, so they will not be explained.

 

  • Topology Visualization

Topology display

 

  • Topology Configuration

Configuration instructions, not in detail

 

Note on the spout and bolt pages, you can refer to the field descriptions in spout and bolt in the topology page

 

 

 

 

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=327031605&siteId=291194637