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

To install the plugin

From the top right of the screen, perform one of the following actions:
- Click > Data Collection, select the TrueSight meter, and select the Sources tab.
- Click > Configure Sources.
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.
Click the name of the source to view source details.
Select the Plugins tab.
Use the search box or scroll through the page to find the plugin you want to install.
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 Name	Description
Host	Host of the Storm UI service
Port	Port of the Storm UI service
Username	Username to access the Storm UI service
Password	Password to access the Storm UI service
Topologies Filter	Select topologies (by name or id) to show metrics for. If not set, it will shows all topologies
Show Bolts	Show metrics for each bolt in each topology (default: true)
Show Spouts	Show metrics for each spout in each topology (default: true)
Source	The Source to display in the legend for the metrics data. It will default to the hostname of the server
Poll Interval	How 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 Name	Description
STORM_CLUSTER_TOPOLOGIES	Number of topologies running on the cluster.
STORM_CLUSTER_EXECUTORS	Total number of executors running on the cluster.
STORM_CLUSTER_SLOTS_TOTAL	Total number of available worker slots on the cluster.
STORM_CLUSTER_SLOTS_USED	Number of worker slots used on the cluster.
STORM_CLUSTER_TASKS_TOTAL	Total number of tasks on the cluster.
STORM_CLUSTER_SUPERVISORS	Total number of supervisors on the cluster.
STORM_TOPOLOGY_TASKS_TOTAL	Number of Tasks per toplogy.
STORM_TOPOLOGY_WORKERS_TOTAL	Number of Workers per topolgy.
STORM_TOPOLOGY_EXECUTORS_TOTAL	Number of executors per topology.
STORM_BOLT_EXECUTORS	Number of executor tasks in the bolt component.
STORM_BOLT_TASKS	Number of instances of bolt.
STORM_BOLT_EMITTED	Number of tuples emitted per bolt per second.
STORM_BOLT_ACKED	Number of tuples acked by the bolt per second.
STORM_BOLT_FAILED	Number of tuples failed by the bolt per second.
STORM_BOLT_CAPACITY	Number of messages executed * average execute latency per second.
STORM_BOLT_EXECUTELATENCY	Average time to run the execute method of the bolt per second.
STORM_BOLT_PROCESSLATENCY	Average time of the bolt to ack a message after it was received per second.
STORM_BOLT_LASTERROR	0-No error, 1-An error or exception occured.
STORM_SPOUT_EXECUTORS	Number of executors for the spout.
STORM_SPOUT_TASKS	Total number of tasks for the spout.
STORM_SPOUT_EMITTED	Number of messages emitted per spout per second.
STORM_SPOUT_ACKED	Number of messages acked per spout per second.
STORM_SPOUT_FAILED	Number of messages failed per spout per second.
STORM_SPOUT_COMPLETELATENCY	Total latency for processing the message per spout per second.
STORM_SPOUT_LASTERROR	0-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.