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
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