0% found this document useful (0 votes)
19 views13 pages

Splunk Apm DB Query Performance

Uploaded by

오정민
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
19 views13 pages

Splunk Apm DB Query Performance

Uploaded by

오정민
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

Splunk APM - DB Query Performance

Enablement Agenda

Feature Overview

Feature Demo

Key Takeaways & Resources

EN AB LEMEN T TOPICS

Feature Overview

Feature Demo

Key Takeaways & Resources


Lesson 1 of 3

Feature Overview

Find trends in aggregate DB queries without DB


Instrumentation

01:08

Pinpoint the database that is causing slowness for your application

See slow and frequently executed aggregate queries, with historical trends

Slice and dice in Tag Spotlight to find out what services, endpoints, workflows, AZs, etc

have been affected

Enabled OOTB for SQL-based DBs, with no DB instrumentation required


Why DB Query Performance in APM?

01:42

Availability
As an SRE/ Service owner, I want to know if service availability issues are related to
databases

I want to know whether an increase in the latency or error rate of a service is


related to a database. If it is, I want to identify which database and which specific
query is contributing the most latency and resolve it by involving the DBA or the
owner of the service that’s making the slow database call.
When I receive alerts about service availability, I want to eliminate databases as a
root cause of the issue by seeing at a glance whether database latency or error
rate increased, or whether a particular query is slow or bottle necked.

I want to see if my new release impacted anything, wrt DB interactions. I would


like a dashboard to determine whether a new release to a service had an impact
on database interactions by examining the average query response time, the
number of query executions, and the change in these values over time.

When I receive an alert related to database latency, I want to quickly assess the
radius of impact to determine whether customer-facing services were affected

Performance Optimization
As a performance engineer, I want to know if there are points of optimization in my DB
interactions (query performance over time), as part of standard ongoing tuning of the
system Monitoring As a service owner / SRE, I want to monitor / alert on specific
queries before they create customer facing issues for my service, etc

Monitoring
As a service owner / SRE, I want to monitor / alert on specific queries before they
create customer facing issues for my service, etc

What did we implement?

02:21
Prior to this release - Databases as inferred services

Splunk APM identifies databases as inferred services in your system using


automatically generated span tags such as db.type, db.instance and db.statement

Databases appear throughout APM, such as in their inferred locations in the


service map, in the service filter list, and in trace view

Troubleshooting MetricSets available for DBs

Can manually connect DB integration(IMM dashboards) as dashboards to DBs in


the service map through Data Links

With this release - OOTB Database Query Performance

Normalize db.statement queries: We capture SQL statements (or queries) from


the span in which each call is made, normalize each query to contain cardinality
and record the following metrics about the query’s performance

Total response time

90th percentile (P90) of latency

Total number of requests

Requests per second

Index DB related span tags: Db query performance indexes a set of database-

related span tags - Normalized db.statement, db.name, db.operation, db.sql.table,


db.system - They work like any other indexed tags and will be available to slice
and dice in Tag Spotlight
Indexing Database Query Performance tags counts towards
Troubleshooting MetricSets entitlement. The indexing can be
explicitly turned off in the UI.

How to configure this feature?

No instrumentation or configuration required!

Following general availability in January 2022, this feature will be enabled for all new accounts.

Customer can explicitly turn off TMS creation for this feature through
toggle OOTB db tags in ‘MetricSets Configuration’ page in APM
C O NT I NU E
Lesson 2 of 3

Feature Demo

Watch the video below to see this feature in action.

C O NT I NU E
Lesson 3 of 3

Key Takeaways & Resources

Key takeaways and resources


Click on the interactive plus signs on the image below to review key takeaways and
resources




Instrumentation

No additional set up or configuration work.


Documentation

Don't forget to leverage the feature documentation on Splunk Docs:


https://docs.splunk.com/Observability/apm/db-query-perf/db-query-performance.html

SQL Databases

Oracle

MySQL

Microsoft SQL Server

PostgreSQL

Aurora

MariaDB

Db2

Pricing

Included in APM pricing

C O NT I NU E

You might also like