-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Include Lock:Timeout (timeout > 0) Event Class in sqlserver input #6978
Comments
Seems like a good idea to me, what do you think @denzilribeiro? |
What we have is just a perf counter in which Lock timeout/sec is a rate counter you cannot just ignore /exclude values. Look at the cntr_type column in sys.dm_os_performance_counters |
There is a separate counter that is actually named "Lock Timeouts (timeout > 0)/sec" - it is available by default, it is just a matter of including it as it gives much more realistic values. |
That is totally fine to replace this one with that . |
Proposed change in sqlserver.go: |
@sawo1337 Can you open a pull request with both counters? |
Feature Request
The current metric only shows Lock Timeouts/sec, which includes internal lock probes that may not be a problem at all. In a live environment, you may get 100s of lock timeouts/sec, but actually no lock timeouts that are longer than 0.
Proposal:
Add Lock Timeouts (timeout > 0)/sec to the sqlserver_performance metric
Current behavior:
Only Lock Timeouts/sec is being gathered
Desired behavior:
Add Lock Timeouts (timeout > 0)/sec to the sqlserver_performance metric
Use case:
If you want to only see locks that are actually causing issues, it is better to skip locks where the timeout is 0. From MSDN:
MSDN Article
The text was updated successfully, but these errors were encountered: