Monitoring Overview

Version 1.3.0 of Splunk Firehose Nozzle for VMware Tanzu comes with a monitoring module that collects the metrics and sends them to your Splunk environment on SPLUNK_METRIC_INDEX index. These metrics can be used to monitor RAM/CPU usage and troubleshoot the nozzle. They can provide insights if you need to scale up your Splunk/Nozzle environment.

The following metrics are collected:

Metric Name Description
nozzle.queue.percentage Shows how much internal queue is filled.
splunk.events.dropped.count Number of events dropped from Splunk HEC.
splunk.events.sent.count Number of events sent to Splunk platform.
firehose.events.dropped.count Number of events dropped from nozzle.
firehose.events.received.count Number of events recieved from firehose(websocket).
splunk.events.throughput Average Payload size.
nozzle.usage.ram RAM Usage
nozzle.usage.cpu CPU Usage
nozzle.cache.memory.hit Number of times it has successfully retrieved the data from memory.
nozzle.cache.memory.miss Number of times it has unsuccessfully tried to retrieved the data from memory.
nozzle.cache.remote.hit Number of times it has successfully retrieved the data from remote.
nozzle.cache.remote.miss Number of times it has unsuccessfully tried to retrieved the data from remote.
nozzle.cache.boltdb.hit Number of times it has successfully retrieved the data from BoltDB.
nozzle.cache.boltdb.miss Number of times it has unsuccessfully tried to retrieved the data from BoltDB.