Indexing: Inputs: HTTP Event Collector
This topic is a reference for the HTTP Event Collector dashboards in the Monitoring Console. See About the Monitoring Console.
What do these views show?
The Monitoring Console provides two dashboards for the HTTP Event Collector, one with an overview of the performance across your deployment, and one with details about performance on each instance within your deployment.
What should I look for?
You can start in the deployment-wide dashboard to survey for outlying performance. Drill down to find more details on a problem in the related instance-scoped dashboard.
Interpret results in these views
In the HTTP Event Collector: Deployment dashboard, the list of tokens shown is a list of currently configured tokens. So if your token has been disabled, it will not appear in the Token dropdown. In contrast, the instance-scoped view shows all tokens, enabled and disabled.
See Set up and use HTTP Event Collector in Getting Data In.
Troubleshoot these views
The instances doing the collecting must run Splunk Enterprise 6.3.0 or greater to use HTTP Event Collector. If your instance is a universal forwarder, the Monitoring Console cannot monitor it, because it cannot be a search peer.
Indexing: Indexes and Volumes
Indexing: License Usage
This documentation applies to the following versions of Splunk® Enterprise: 6.5.0, 6.5.1, 6.5.1612 (Splunk Cloud only), 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.5.7, 6.5.8, 6.5.9, 6.5.10, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 6.6.7, 6.6.8, 6.6.9, 6.6.10, 6.6.11, 6.6.12, 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6