Use the service view for a complete view of your service health 🔗
As a service owners you can use the service view in Splunk APM to get a complete view of your service health in a single pane of glass. The service view includes a service-level indicator (SLI) for availability, dependencies, request, error, and duration (RED) metrics, runtime metrics, infrastructure metrics, Tag Spotlight, endpoints, and logs for a selected service. You can also quickly navigate to code profiling and memory profiling for your service from the service view.
Note
The service view is available for instrumented services that send spans with a service.name value.
Access the service view for your service 🔗
You can access the service view for a specific service in several places.
You can search for the service using the search in the top toolbar.
You can also access the service view for a specific service within the service map. Start by selecting Service Map on the APM landing page. Select a service in the service map, then select Service view in the panel.
Finally, you can also access the service view for a specific service by selecting the service from the APM landing page.
Use the service overview to monitor the health of your service 🔗
When you open the service view an environment is selected based on your recently viewed environments. Adjust the environment and time range filters if necessary. Use the following sections to monitor the health of your service.
Service metrics 🔗
Use the following metrics in the Service metrics section to monitor the health of your service. Collapse sub-sections that are not relevant to you to customize your service view.
Availability SLI - The availability service-level indicator (SLI) shows the percentage of time your service was available in the last 30 days. The chart shows successful and unsuccessful requests. If you configured an availability service-level objective (SLO), an additional chart displays availability over the compliance window you specified in your objective. See Measure and track your service health metrics with service level objectives (SLOs).
Service map - The service map shows the immediate upstream and downstream dependencies for the service you are viewing. The service map in service view is limited to 20 services, sorted by the most number of requests. Hover over the chart and select View full service map to go to the service map.
Service requests - The service requests chart shows streaming request data for the service. If you have detectors for the service requests configured, triggered alerts display below the chart. Select the chart to view example traces. Select the alert icon to view alert details.
Service latency - The service latency chart shows p50, p90, and p99 latency data for the service. If you have detectors for the service latency configured, triggered alerts display below the chart. Select the chart to view example traces. Select the alert icon to view alert details.
Service error - The service error chart shows streaming error data for the service. If you have detectors for the service error rate configured, triggered alerts display below the chart. Select the chart to view example traces. Select the alert icon to view alert details.
- Dependency latency by type - The dependency latency by type chart shows the latency for each of the downstream systems. Select the chart to see details about each system category. Systems are categorized as follows:
Services - instrumented services
Databases - not yet supported
Inferred services - uninstrumented, inferred services
Pub/sub queues - not yet supported
Runtime metrics 🔗
Instrument your back-end applications to send spans to Splunk APM to view runtime metrics. The following runtime metrics are available for Java, Node.js, and .NET in the service view. See Instrument back-end applications to send spans to Splunk APM.
Memory usage
Allocation rate
Class loading
GC activity
GC overhead
Thread count
GC overhead
Thread count
Thread pools
Infrastructure metrics 🔗
If you are using the Splunk Distribution of the OpenTelemetry Collector and the SignalFx Exporter, infrastructure metrics for the environment and service you are viewing display. See Get started with the Splunk Distribution of the OpenTelemetry Collector and SignalFx exporter.
The following infrastructure metrics are available:
Host CPU usage
Host memory usage
Host disk usage
Host network usage
Pod CPU usage
Pod memory utilization
Pod disk usage
Pod network utilization
View Tag Spotlight view for your service 🔗
Select Tag Spotlight to view Tag Spotlight view filtered for your service. See Analyze service performance with Tag Spotlight to learn more about Tag Spotlight.
View endpoints for your service 🔗
Select the Endpoints tab to view endpoints for the service. Use the search field to search for specific endpoints. Use the sort drop-down list to change how endpoints are sorted. Select an endpoint to view endpoint details or go to Tag Spotlight, traces, code profiling, or the dashboard for the endpoint.
View logs for your service 🔗
Select Logs to view logs for the environment and service you are viewing. By default, logs are displayed for all indices that correspond to first listed Log Observer Connect connection. Logs are filtered by the service you are viewing using the service.name value. If your logs do not have a service.name value, you can create an alias in Splunk Web. See Create field aliases in Splunk Web .
To select a different connection or refine which indices logs are pulled from, select Configure service view.
In the Log Observer Connect Index drop-down list, select the Log Observer Connect connection, then select the corresponding indices you want to pull logs from.
Select Apply
Select Save changes.
The connection and indices you select are saved for all users in your organization for each unique service and environment combination.
Go to the code profiling view for your service 🔗
Select Code profiling to go to the code profiling view of AlwaysOn Profiling filtered for your service. See Introduction to AlwaysOn Profiling for Splunk APM to learn more about AlwaysOn Profiling.
Go to the memory profiling view for your service 🔗
Select Memory profiling to go to the memory profiling view of AlwaysOn Profiling filtered for your service. See Introduction to AlwaysOn Profiling for Splunk APM to learn more about AlwaysOn Profiling.
Configure the service view 🔗
Select Configure service view to modify the Log Observer Connect connection and indices for the logs you want to display for your service.
In the Log Observer Connect Index drop-down list, select the Log Observer Connect connection, then select the corresponding indices you want to pull logs from.
Select Apply
Select Save changes.
The connection and indices you select are saved for all users in your organization for each unique service and environment combination.