Part 1: Instrument back-end services and applications to send traces, logs, and metrics 🔗
Splunk Application Performance Monitoring (APM) monitors and reports on data from your in-house applications, such as Java, Python, and Ruby applications. Using Splunk APM, you can gain important insights into the behavior of your applications.
Instrumentation is the process of integrating Splunk with these applications. With instrumentation, you can send traces, logs, and metrics to Splunk Observability Cloud.
Instrument your applications 🔗
To begin instrumenting your applications, see the instrumentation guides corresponding to the language of the application you want to instrument:
Use Splunk APM to view your application data 🔗
アプリケーションをインストルメンテーションした後、以下の場所でデータにアクセスできます：
The APM landing page
APM explorer view
Metric finder
Splunk Log Observer Connect
Use one of these methods to make sure that your application data is reaching Splunk Observability Cloud.
View traces on the APM landing page 🔗
The APM landing page displays previews of trace data for applications. To use the APM landing page to find your trace data, see APMのランディングページでアプリケーションの健全性を評価する.
View traces in the APM Explorer view 🔗
The APM explorer view gives detailed information about traces, such as highlighting dependencies among your application.
To learn more about APM explorer, see サービスマップでサービス間の依存関係を表示する.
Search for metrics using metric finder (Java only) 🔗
If you’ve instrumented a Java application, you can see application metrics using the metric finder. See メトリクス・ファインダーでメトリクスを検索する for more information.
Query logs in Log Observer Connect 🔗
If you chose to ingest logs, you can find logs in Splunk Log Observer Connect. To learn how, see View overall system health using the timeline.
次のステップ 🔗
To continue setting up your application monitoring with Splunk APM, see Part 2: Instrument serverless functions to send traces and metrics.