Automatic discovery and zero-code instrumentation for Kubernetes 🔗
Automatic discovery detects and collects signal data from third-party services, such as databases and web servers. Through auto discovery the Collector automatically generates a configuration snipet that you can modify and incorporate into your existing configuration to retrieve your services』 data.
注意
Auto discovery of third-party services is only available for the Collector in Linux and Kubernetes environments.
Via automatic discovery you can also enable zero-code instrumentation of back-end applications, which allows the Collector to retrieve data from application language runtimes without having to modify the source application code or adding any new installation or configuration steps. With this option you won’t have to install and configure your instrumentation agents separately. Zero-code instrumentation using the Collector’s automatic discovery feature is only available for the Java, Node.js, and .NET language runtimes. Alternatively you can deploy zero-code instrumentation independently from the Collector for 8 back-end languages, as described in バックエンドアプリケーションをインストルメンテーションして、スパンを Splunk APM に送信する.
Get started
To enable zero-code instrumentation of Java, Node.js, and .NET applications running on Kubernetes via auto discovery see Zero-code instrumentation for back-end applications in Kubernetes. With this option you won’t have to install and configure your instrumentation agents separately.
To use the Collector’s automatic discovery of third-party applications in Kubernetes environments see Automatic discovery for third-party services in Kubernetes. With this option you’ll only have to reuse a config file automatically generated by the Collector.
For a walkthrough of how to use automatic discovery and zero-code instrumentation to monitor an application in a Kubernetes environment, see Advanced customization for automatic discovery and instrumtenation in Kubernetes.