influxdata / influxdata/telegraf
SqlServer Input: Add sqlserver ProcessID to SQL queries
- Dominant language
- Go
- Stars
- 17.8k
- Forks
- 5.8k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 161
Description
## Feature Request
Adding SqlServer Process ID to ServerProperties metrics
### Proposal:
Adding **SERVERPROPERTY('ProcessID')** can help for correlation between **win_perf_counters** metrics and SqlServer Process counters and the corresponding SQL Server instance
### Current behavior:
Currently there is no way to correlate CPU usage in interval of seconds
### Desired behavior:
Having the ProcessID of the sqlservr process from ServerProperties query V2
### Use case:
In a scenario where there is one SQL instance installed on a Windows Server, correlation with Win process counters is easy because there is only one instance of the sqlserver process. However, the current proposal would be helpful for SQL multi-instances scenarios due to multiple instances of the sqlservr process in win_perf_counters making the correlation between Win process counters and the corresponding SQL Instances impossible without the correct Process ID.
Contributor guide
Research direction
Start by locating the SqlServer input and its ServerProperties query V2, then review how query results become ServerProperties metrics. Add the SQL Server ProcessID so it can be correlated with win_perf_counters process metrics, and verify that the resulting metric exposes the value for multi-instance scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- databases, observability-sre
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100