Logstash TCP 🔗
The Splunk Distribution of OpenTelemetry Collector provides this integration as the
logstash-tcp monitor by using the SignalFx Smart Agent Receiver.
Use this integration to monitor the health and performance of Logstash deployments through Logstash’s Monitoring APIs.
This receiver is available on Linux and Windows.
After you’ve configured the integration, you can:
View metrics using the built-in dashboard. For information about dashboards, see View dashboards in Observability Cloud.
View a data-driven visualization of the physical servers, virtual machines, AWS instances, and other resources in your environment that are visible to Infrastructure Monitoring. For information about navigators, see Splunk Infrastructure Monitoring navigators.
Access Metric Finder and search for metrics sent by the monitor. For information about Metric Finder, see Use the Metric Finder.
Follow these steps to deploy the integration:
This monitor is available in the Smart Agent Receiver, which is part of the Splunk Distribution of OpenTelemetry Collector. The Smart Agent Receiver lets you use existing Smart Agent monitors as OpenTelemetry Collector metric receivers.
Using this monitor assumes that you have a configured environment with a functional Smart Agent release bundle on your system, which is already provided for
x86_64/amd64 Splunk Distribution of OpenTelemetry Collector installation paths.
To activate this monitor in the Splunk Distribution of OpenTelemetry Collector, add the following to your configuration file:
receivers: smartagent/logstash-tcp: type: logstash-tcp ... # Additional config
To complete the integration, include the monitor in a metrics pipeline. To do this, add the monitor to the service > pipelines > metrics > receivers section of your configuration file.
service: pipelines: metrics: receivers: [smartagent/logstash-tcp]
Configuration settings 🔗
||The host name of the Logstash monitoring API. The default value is
||The port number of Logstash monitoring API. The default value is
||If true, the agent connects to the host using HTTPS instead of HTTP. The default value is
||The maximum amount of time to wait for API requests, in seconds. The default value is
There are no metrics available for this integration.
If you are not able to see your data in Splunk Observability Cloud: