Debug configuration plugin mk-sql.exe

CMK version: 2.3.0p17
OS version: Ubuntu Server 24.04 LTS

Hello everyone,

I am trying to enable the mk-sql.exe plugin on the agent running in the VM dedicated to SQL Server 2019 STD. After following this official guide

going to do a service discovery I don’t find the DBs to enable but only the services I need to keep under monitoring. I have tried both the system account and dedicated account route on SQL Server.

If on the VM from powershell I run mk-sql.exe I see the list of my DBs but CheckMK does not find them among the services to add. What am I doing wrong?

Maybe it depends on the account from which you are executing the agent plugin?
There is a rule in Checkmk with which you can also decide which user should run the agent plugin.

Hi, can you point me to the rule?

Hi,
That’s the one:

Hi, I can’t find this rule. I’ll do some more testing today and then in case I’ll update the thread

Hi, I have done various tests but I cannot get the status of SQL Server DBs as described in the documentation. The strange thing is that the rest of the services that I keep monitored at the VM level are being received correctly.

These are the steps I went to:

  • updated the agent checkmk
  • loaded the mk-sql.exe plugin in the directory C:\Program Files (x86)\checkmk\service\plugins
  • created the mk-sql.yml file with both a system user of the appropriate SQL Server

mssql:
main:
authentication:
username: MyUser
password: MyPassword
type: sql_server

  • copied the file in the path C:\ProgramData\checkmk\agent\config\mk-sql.yml

run from powershell as administrator the file mk-sql.exe (I saw the output and saw the list of my DBs

And if you run the Checkmk agent directly also as the same user. Does it still work ?

Yes, the agent is working correctly. I also tried stopping a service to see if the stop was being received and it is working. It is only the monitoring via mk-sql that is not working

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.