Start monitoring your websites and servers successfully.
Monitors are the main feature of Semonto. There are two types of Monitors, Webapp and Servers. A Webapp is used to monitor the behaviour and availability of websites and web applications. For example does a website respond quickly and does not show any errors. A Server can be used to monitor multiple aspects of a dedicated or virtual server.
A requirement to use a Monitor for a server is that it needs to be reachable over the internet. Otherwise a PulseCheck can be used.
When you would like to monitor a web application fully, we suggest to create a Server and a webapp for this web application.
A Webapp performs test on the reachability of a website or web application and if it responds quickly, the response time.
Additionally content tests can be performed, which are tests on forbidden content or required content. Missing required content of presence of forbidden content could indicate an error state of the website or web application. Sometimes websites show a text such as ‘be back soon’ when they are offline, this can then be used for testing on the presence of forbidden content.
Just like a Webapp, a Server can test the reachability and response time, the latency, of your server. And Semonto can verify if specific ports are reachable which are essential for one of your services.
It's also possible to measure more technical aspects of a server. To these aspects of a server there normally is no external access. Therefore we provide a bridge: the extended tests. This 'bridge' provides the opportunity to monitor for example server load, disk usage or memory load. For this it is needed to install a small application on your server. It is also possible to define and create your own custom tests.
When you would like to perform extended or custom tests, you need to supply a URL to the ‘bridge’ for Semonto to be able to find and perform those tests. This is because Semonto does not has access to your server settings or database configuration for example. This is for security reasons. If you want to monitor your database or want to keep an eye on the server-load, you will need to install a small web application on your server, the 'bridge'. This allows Semonto to access the needed data, without having too much access. Just make sure Semonto’s IP-addresses are whitelisted. The IP-addresses can be found in Semonto Supervisor.
We provide some standard web applications available for you, at the moment written in PHP and a start in Ruby-On-Rails publicly accessible at GitHub. Feel free to use these and add more functionality.
The 'URL to Bridge' should be the URL to the main-root of the web application and should end with
'/'. If you use PHP and the files are the directory
semc in the root of your htdocs, the URL needs to be:
If you use Ruby-On-Rails, the path needs to be on the routings you defined for Semonto.
With this 'bridge' running on your server, you can also implement custom tests, tests written for your specific needs. Custom tests need to be implemented in the web application as explained in the section above. Let say Semonto wants to perform the test X, the called URL will be the
URL to bridge'?test=X , for example:
It's up to your webapp to handle this GET-variable and print the correct test-result. The answers of the webapplication should be formatted as:
X::INFO::MORE_INFO. Where X is the status, with:
If you need more support on this, feel free to email us at firstname.lastname@example.org.
Tags can be used for easier filtering of the Monitors or PulseCheck you would like to see in the overview, this is only visual and has no effect on the monitoring. This is very useful when you have a large amount of monitors.
Tags can be across between Monitors and PulseChecks.
Each Monitor is member of at least one Group. When you create a Monitor you can make it a member of an existing group or create a new Group with a default name. You can fully customize the new group.
In each group you can configure the interval for the testing by Semonto. This affects your usage of you plan together with the amount of monitors you have. You can also change the server that performs the tests. Best is to pick one of Semonto's servers nearby.
For each group you can select one or multiple Contact Groups that define who and how they are warned when something occurs. This gives you fine grain control on this. Be sure to add at least one Contact Group to a group if you want to get warned effectively! You can read more on Contact Groups and Groups in this guide.
Semonto can pause the monitoring of a specific group of Monitors, for example when you have maintenance on your servers. However do keep in mind that pausing affects all Monitors using in this Group!
Sometimes, it can be useful to know the IP-addresses of the Semonto servers. Be sure to allow these IP-addresses in your firewalls, if you are using any. If you use log analyzers, you can filter those IP-addresses to ignore Semonto's hits/requests. Be sure to allow at least all Verification-servers and the TestCenters you use. When we perform a major upgrade, it is possible that another than the preferred TestCenter performs your tests. It is best to allow all our IP-addresses. The IP-addresses can be found in Semonto Supervisor.