Server health monitoring
Use Semonto to test the health of your servers. If something affects their performance, Semonto alerts you immediately. You can respond quickly and avoid interruption of your service.
Try it for free
Use Semonto to test the health of your servers. If something affects their performance, Semonto alerts you immediately. You can respond quickly and avoid interruption of your service.
Try it for freeWith server health monitoring, you keep an eye on the performance of your server. Depending on the type of test, you can check whether the server is up or down (HTTP Status Code) or gather more detailed data such as server load, memory usage and so on. You receive instant notifications of any performance issues. This way, you stay in control and your end users can enjoy your services without interruptions.
It is always easier to fix a small issue early on than to clean up a huge mess when something has spiralled out of control. With Semonto, you are warned immediately. This way, you can act proactively and nip server outages in the bud.
No need to worry when you go home. Semonto will notify you if anything happens. No need to keep a list of periodical checks either. Semonto will do it all automatically. You can relax and feel confident that everything is under control.
The server is the beating heart of any organization. Even the smallest interruption will cause a dramatic drop in productivity levels. After being distracted by an outage, it generally takes people 23 minutes to get back into focus.
Philip Verbist
Founder of XSOnline.be
We needed a way to know exactly when our servers were down without getting a lot of false positives. Semonto came to the rescue. They check our servers every 5 minutes. When a test fails, they first verify from another location before notifying us. It works like a charm!
Disk Space Load Average Memory Usage Current Server Load Server Temperature Hard Drive Health Basic SQL Queries Last Sync Last Activity Queues Running Processes Job Execution Time Anything you can dream of...Most server information that you want to monitor is shielded from the outside world for security reasons. That is why we have built a safe bridge between your server and Semonto. This way, your own server executes the test and communicates the results to us through a secure communication bridge. Easy and safe!
Unlike other custom server monitoring solutions, Semonto does not require you to download any third-party software. Our agentless monitoring happens through a secure communication bridge between your server and our dashboard.
Not only the tests can be adapted to your needs, but you can also customize the dashboard. It offers a clear overview, even if you have a large number of monitors. Tags can be used for easier filtering, and groups help you to manage and edit settings for multiple monitors at the same time.
Here are some examples of what custom tests can be used for
To check the logs of external APIs to make sure that they are still performing the way they should.
To monitor the traffic on your app (calls per minute) and be alerted when you are reaching a threshold.
To follow the status of your internal server and monitor the inode limit.
To get the last synchronization date of a server.
To know the number of active agents and the last activity.
To make sure that a certain program (such as anti-virus) is still running and has recently been updated.
And any other server monitor you can imagine.
Know if the server is up or down. Perform basic health endpoint validation, based on the HTTP code. Receive the result in the form of an HTTP code, for example: HTTP 200 if everything is OK
Use one of our predefined templates to get more detailed results, such as:
Disk space Memory Usage Server Load My SQL pingCreate your own test to get more detailed results about anything that matters to you.
Semonto performs the same tests from multiple locations to avoid false positives. In other words, we get a ‘second opinion’ before alerting you. If your server is down in one location (for example, Amsterdam) we verify the result by testing again from a second location (for example, New York). Only if both test locations confirm the problem, we send out an alert. If you want, you can go even further and specify how long we should wait before notifying you for each test.
Our testing locations:
Our monitoring is agentless, so it does not require a software agent to be installed on your server. You simply run a small application in your current stack and provide us with the URL of this installation. Semonto will send requests to this URL to get the latest test results. This access can be limited to the IPs of Semonto for an extra layer of security.
You can now create your own test, which we will execute by sending an HTTP GET request to your server, using the “test name” as the parameter. The alert severity levels are "ok", "warning", "critical" or "error" and you can assign the corresponding values, such as the percentage of available disk space, or the latency time. Your own server then executes the test and send us the reply.
The results of your tests are displayed in your Semonto dashboard. So everything comes together in one, clear overview.
If you are developing a new app, it can have very specific characteristics that you want to monitor remotely. You want to make sure that your app is available for your end users at all times. Use Semonto to make sure that all servers are up and running.
Semonto for web developers →The health of your servers can have a huge impact on the productivity and efficiency of your organization. Use Semonto to avoid unwanted interruptions of your internal tools and processes.
Semonto for business owners →With Semonto, you can monitor multiple servers at the same time. Stay on top of server load and storage usage so you can respond quickly and avoid unavailability of your services.
Semonto for server owners →Monitor the validity of your SSL certificates. Get alerted when certificates are about to expire so that you can renew them in advance.
Read more →Monitor periodical scripts or keep an eye on a server behind a firewall, a complex NAT situation or a server without an active webserver.
Read more →
