Hello,

We are happy to announce our latest feature: “Webhook for Incidents”

Notification channels on Xitoring let you receive Incidents and Alerts about your servers and websites instantly. we are constantly working to add more Integrations to Notification Channels including Google Chat, Mattermost, and more.

we’ll go over how to set up webhook integration in Xitoring and give an example of what Xitoring will post to your webhook URL.

Creating a Webhook URL

To get started, you need to create a webhook URL in your server or application. This is the URL where Xitoring will send the webhook notifications. It’s essential to make sure the URL is publicly accessible and can receive HTTP POST requests.

Configuring Webhook in Xitoring

Once you have a webhook URL, log in to your Xitoring account and go to the Notification Roles page. From there, you can create a new notification role or add a webhook to an existing role. Then, enter your webhook URL in the field provided and click on “Send a Test Notification” to verify that everything is set up correctly.

Request breakdown

The following table is a guide to making it easy to integrate the Xitoring webhook feature into your application.

You can always be informed of our latest releases هنا.

If you have any questions, you can reach the support team at [email protected]

Hello,

Heartbeat monitoring is finally here!

At Xitoring, we know how important it is to ensure that your services and applications are running smoothly. That’s why we’re excited to introduce our latest feature: the Heartbeat Check.

So, what is a Heartbeat Check? Simply put, it’s a signal sent by your service or application at regular intervals to Xitoring. Our system then checks whether it has received the heartbeat within a certain time frame. If it hasn’t, we assume that the service or application is not responding correctly and triggering an incident.

Setting up a Heartbeat Check is easy. Just select a label like you would for any other check, configure the proper trigger and notification roles, and set the fault tolerance (the maximum interval between heartbeats) to your desired time frame. After creating the check, you’ll receive a unique link that you can use to define your heartbeat. Adding a simple GET request to your script or code can ensure that your service or application is running smoothly.

Using a Heartbeat Check is also a great way to perform an overall availability check for your Linux machine. By adding the GET request command to your crontab, you can ensure that your machine is up and running every minute.

Heartbeat monitoring use cases:

Don’t let service disruptions catch you off guard. With Xitoring’s Heartbeat Check, you can rest easy knowing that your services and applications are always being monitored. Try it out today and see the difference it can make!

You can read more about heartbeat monitoring, and some code snippets of Bash script and Python on our docs.

Hello,

We have just deployed a new version including the “Recurring Email Report” feature that lets you create multiple email reports for your uptime checks or servers, with your desired period (Daily, Weekly, Monthly) and your main email or teammates!

The free plan is limited to one report, Paid users can create as many as reports they want!

Email report sends out schedule:

• Daily Reports: you get an email report every day at 10 AM UTC.
• Weekly Reports: you get an email report every week on Monday at 10 AM UTC.
• Monthly Reports: you get an email report every 1st of the month at 10 AM UTC.

(المزيد…)

We are happy to announce that Xitogent is now compatible with Redhat 9 distros.  Xitoring offers free server monitoring (up to 5 servers) for Centos 9 / Redhat 9 / CloudLinux 9 / Almalinux 9 / Rockylinux 9 users.

By Installing Xitogent on your Redhat 9 distro server you can easily gather all server statistics and data without hassle, and Xitoring does the most for you, including service discovery, creating initial checks, generating graphs, configuring initial triggers, etc.

Xitogent runs as a service on your server and automatically sends your server statistics continuously to your nearest Xitoring Server and we use the data to generate graphs or find out if something’s wrong on your server (e.g. we’ll automatically notify you if your CPU or memory usage is above normal). It runs on a recurring interval and sends statistics to the nearest probe node, we’ll use the data to make sure everything is fine on your server and then use it to make useful graphs (Server Load, CPU Usage, Memory Usage, Disk IO, and Disk Usage).

If you’re new to Xitoring, you can register in a minute and start monitoring 5 Linux servers at no cost forever!

About Xitogent

Hello,

We are thrilled to announce the new feature on Xitoring, that lets you create “Maintenance Schedules” for your uptime checks and servers in order to avoid false positive alerts or inaccurate reporting of downtime during a maintenance window. The feature is available for free and paid users without any limitations. Selected monitoring Checks or Servers will be paused during the maintenance window, also the status will be reflected on your Public Status Page automatically to inform your users.

Is it necessary to pause monitoring during maintenance?

It depends on the type of maintenance being performed and the specific requirements of the organization. In some cases, it may be necessary to pause uptime monitoring during maintenance to avoid false positives or inaccurate reporting of downtime.

For example, if the maintenance activity involves taking the system or service offline or making changes to critical components, uptime monitoring may need to be paused until the maintenance is completed. Otherwise, the monitoring system may generate false alerts or report false downtime, which could lead to confusion and unnecessary investigations.

On the other hand, if the maintenance activity is not expected to impact the uptime of the system or service, uptime monitoring may not need to be paused. In fact, continuing to monitor uptime during maintenance can help identify any unexpected issues that may arise during the maintenance activity.

Ultimately, the decision to pause uptime monitoring during maintenance should be based on an assessment of the potential impact of the maintenance on system uptime, as well as the specific requirements and objectives of the organization. It is important to communicate any changes in monitoring to relevant stakeholders to ensure clear expectations are set.

If you need help creating your first maintenance you can read more on Docs or contact [email protected] anytime!

Thanks.

It’s very thrilling to announce that we have re-coded our whole user interface with the latest technologies using React v18 to improve the user experience. Our frontend engineers and product team is working very hard for daily builds, adding features, and applying bug fixes.

The mobile experience is improved significantly compared to the latest version, also we now have Dark mode!

New drag-and-dropable widgets on the dashboard let you have a glance at your Servers, Uptime Checks, Incidents, or account-related stuff like login sessions or billing.

Dark mode:

Light mode:

Stay tuned, we have plenty of good news to be announced shortly!

We are always reachable at [email protected] if you have any questions or feedback.