Storm plugin

This plugin monitors, visualizes and alert on your Apache Storm environment.

Prerequisites

Meter 4.5.0-778 or later must be installed.

The Apache Storm plugin 0.9.3 or later supports the following Operating System.

Linux(tick)

To install the plugin

  1. From the top right of the screen, perform one of the following actions:
    • Click Settings > Data Collection, select the TrueSight meter, and select the Sources tab.

    • Click Settings > Configure Sources.
  2. Use the search box or scroll through the page to find the source system which has the TrueSight meter on which you want to install the plugin.
  3. Click the name of the source to view source details.
  4. Select the Plugins tab.
  5. Use the search box or scroll through the page to find the plugin you want to install.
  6. Click + Install to start the installation.

    Refer to the following sections for the configuration details required to collect data and view the list of plugin metrics.

Configuration details

Field NameDescription
HostHost of the Storm UI service
PortPort of the Storm UI service
UsernameUsername to access the Storm UI service
PasswordPassword to access the Storm UI service
Topologies FilterSelect topologies (by name or id) to show metrics for. If not set, it will shows all topologies
Show BoltsShow metrics for each bolt in each topology (default: true)
Show SpoutsShow metrics for each spout in each topology (default: true)
SourceThe Source to display in the legend for the metrics data. It will default to the hostname of the server
Poll IntervalHow often should the plugin poll for metrics

Events Generated

An Event will be generated whenever the value of lasterror is not nil and will be displayed in the situation room. Once an error occurs an event will be triggered during each polling interval. We will see only one Event for the same error in the situation room with an occurrence count. A new Event will be generated for a different error.

Advanced configuration

To customize this plugin, see Apache Storm on GitHub.

Plugin metrics

Metric NameDescription
STORM_CLUSTER_TOPOLOGIESNumber of topologies running on the cluster.
STORM_CLUSTER_EXECUTORSTotal number of executors running on the cluster.
STORM_CLUSTER_SLOTS_TOTALTotal number of available worker slots on the cluster.
STORM_CLUSTER_SLOTS_USEDNumber of worker slots used on the cluster.
STORM_CLUSTER_TASKS_TOTALTotal number of tasks on the cluster.
STORM_CLUSTER_SUPERVISORSTotal number of supervisors on the cluster.
STORM_TOPOLOGY_TASKS_TOTALNumber of Tasks per toplogy.
STORM_TOPOLOGY_WORKERS_TOTALNumber of Workers per topolgy.
STORM_TOPOLOGY_EXECUTORS_TOTALNumber of executors per topology.
STORM_BOLT_EXECUTORSNumber of executor tasks in the bolt component.
STORM_BOLT_TASKSNumber of instances of bolt.
STORM_BOLT_EMITTEDNumber of tuples emitted per bolt per second.
STORM_BOLT_ACKEDNumber of tuples acked by the bolt per second.
STORM_BOLT_FAILEDNumber of tuples failed by the bolt per second.
STORM_BOLT_CAPACITYNumber of messages executed * average execute latency per second.
STORM_BOLT_EXECUTELATENCYAverage time to run the execute method of the bolt per second.
STORM_BOLT_PROCESSLATENCYAverage time of the bolt to ack a message after it was received per second.
STORM_BOLT_LASTERROR0-No error, 1-An error or exception occured.
STORM_SPOUT_EXECUTORSNumber of executors for the spout.
STORM_SPOUT_TASKSTotal number of tasks for the spout.
STORM_SPOUT_EMITTEDNumber of messages emitted per spout per second.
STORM_SPOUT_ACKEDNumber of messages acked per spout per second.
STORM_SPOUT_FAILEDNumber of messages failed per spout per second.
STORM_SPOUT_COMPLETELATENCYTotal latency for processing the message per spout per second.
STORM_SPOUT_LASTERROR0-No error, 1-An error or exception occured.

For STORM_BOLT_LASTERROR and STORM_SPOUT_LASTERROR, 1 is used if there was an error, and the value for the errorLapsedSecs is less than the polling interval.

Was this page helpful? Yes No Submitting... Thank you

Comments