-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Collect stored procedure metrics from dm_exec_procedure_stats #15805
Conversation
Codecov Report
Flags with carried forward coverage won't be shown. Click here to find out more. |
e2d0f5a
to
35101bd
Compare
'min_collection_interval': self.collection_interval, | ||
'tags': self.tags, | ||
'cloud_metadata': self.check.cloud_metadata, | ||
'payload_type': 'procedure_metrics', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a thought since we're at the stage where we can still consider changes: should we call this kind
instead of payload_type
? That's what we use for the metadata payloads and I was looking at this and thinking of adopting similar patterns for the new metric type.
6f1157f
What does this PR do?
When DBM is enabled, starts collecting stored procedure metrics from sys.dm_exec_procedure_stats at 60s interval (configurable). Also adds the corresponding
procedure_metrics
section to the config file. The new DBM-only metrics aresqlserver.procedures.count
,sqlserver.procedures.time
,sqlserver.procedures.worker_time
,sqlserver.procedures.physical_reads
,sqlserver.procedures.logical_reads
,sqlserver.procedures.logical_writes
andsqlserver.procedures.spills
.Motivation
Improve the SQL Server monitoring posture of DBM (Database Monitoring) by adding stored procedure metrics to the collected telemetry.
Additional Notes
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.