-
Notifications
You must be signed in to change notification settings - Fork 3
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
Invoke-IcingaCheckMSSQLResource uses wrong/insufficient query #50
Comments
Additionaly:
|
Same for me. I am also using named instances. Same problem with Invoke-IcingaCheckMSSQLPerfCounter. |
And if you are using the direcor you have to set '\MSSQL$$MYDATABASE01::Buffer Manager\Buffer cache hit ratio' |
Ok, I think I have found a solution. I don't know if it is the best way to solve the problem but for me it works. You have to change the follwing files: C:\Program Files\WindowsPowerShell\Modules\icinga-powershell-mssql\provider\mssql\Get-IcingaMSSQLPerformanceCounter.psm1 Change Line 117 C:\Program Files\WindowsPowerShell\Modules\icinga-powershell-mssql\plugins\Invoke-IcingaCheckMSSQLResource.psm1
Change Line 140-158 to:
After the manual changes you have to rebuild the cache and restart the icinga services:
|
When using
Invoke-IcingaCheckMSSQLResource
the effective query used isIn my case, using MSSQL-Server Express Edition, this query returns no results since the
object_name
column does not look likeobject_name = 'SQLServer:Buffer Manager'
but instead looks like
object_name = 'MSSQL$SQLEXPRESS01:Buffer Manager'
for example.
At least in the case of MSSQL-Server Express Edition the direct string comparison does not seem to be sufficient.
The text was updated successfully, but these errors were encountered: