Network, databases, brokers and mail
A website can work while the database, queue or mail server is already down. Check every layer.
The task
Behind one service there is a database, a cache, a message queue, mail and file exchange. Usually they are checked with different tools or not checked at all.
How it is solved
Each layer is checked by its own monitor type with a clear error code: timed out, wrong password, no topic, certificate rejected. Database queries are read-only: write commands are rejected as early as on save.
What is included
- Network: TCP with sending data and checking the response, ICMP, DNS with A, AAAA, CNAME, MX, TXT, NS types
- SSL: certificate expiry and domain registration expiry
- WebSocket, SignalR hub and gRPC health
- Databases: PostgreSQL, MySQL and MariaDB, MongoDB, Redis
- Brokers: MQTT, RabbitMQ, Kafka
- Mail: SMTP, IMAP, POP3 without sending emails
- Files: FTP, FTPS and SFTP with server key verification
Limitations
- Kafka is checked only through a private agent.
- Database queries are read-only: commands that change data are not saved.
Questions about this feature
Will a check change data in the database?
No. Queries and commands are checked on save, and anything that changes data is rejected.
How do I check a database that is not visible from the internet?
Install a private agent in your network. The agent checks PostgreSQL, MySQL, MongoDB, Redis and brokers from the inside.
Where it helps
Other features
All featuresCheck your services today
The free plan includes checks, a status page and a team of up to three people. The setup wizard takes you from a product to the first notification.