DumbMonit
IntegracionesBases de datos y mensajería
Monitorizar SQL Server con DumbMonit
The database engine itself: databases that are not online, blocked requests, sessions against the limit, disk space of the data volumes, SQL Server Agent jobs and AlwaysOn availability groups.
DocumentaciónSitio web oficial: Microsoft SQL Server
Las descripciones están en inglés, como en el producto. Las etiquetas de la página siguen su idioma.
Qué vigila DumbMonit
The database engine: databases that are not online, requests blocked behind a forgotten transaction, sessions against the limit, the free space of the data volumes, SQL Server Agent jobs whose last run failed, and AlwaysOn availability groups.
Uso habitual. Databases not online, blocking, connections, volume space, Agent jobs, AlwaysOn
Ejemplos
- SQL Server 2019 to 2025
- SQL Server Express
- Azure SQL Managed Instance
Cómo se conecta
Qué necesita
- SQL Server loginA SQL Server authentication login, not a Windows account. Sent in the TDS login packet over TLS.
Puertos de red que abrir
1433/TCPSQL Server (TDS, default port)
Pasos de configuración: Create a read-only SQL Server login
Connect to the instance with SQL Server Management Studio or sqlcmd, with a login allowed to create logins, and create the login DumbMonit will use.
CREATE LOGIN dumbmonit WITH PASSWORD = 'choose-a-long-password', CHECK_POLICY = ON;Give it the server-wide read rights it needs to see the state of the engine, and nothing else.
GRANT VIEW SERVER STATE TO dumbmonit; GRANT VIEW ANY DEFINITION TO dumbmonit;Optional, for the SQL Server Agent jobs: let it read the job history in msdb.
USE msdb; CREATE USER dumbmonit FOR LOGIN dumbmonit; ALTER ROLE SQLAgentReaderRole ADD MEMBER dumbmonit;Check that the instance accepts SQL Server authentication (mixed mode) and listens on a fixed TCP port: SQL Server Configuration Manager, Network Configuration, TCP/IP.
In DumbMonit, enter the server address, for example sql.lan, or sql.lan:1444 for another port, then the login and its password.
Tick Accept an unverifiable certificate while the server still presents its self-signed certificate.
Ojo. Windows authentication is not supported: use a SQL Server login, on an instance that allows SQL Server authentication (mixed mode). Named instances need their fixed TCP port in the address.