Deploy in minutes with 100+ ready-to-use integrations
ilert seamlessly connects with your tools using out pre-built integrations or via email. ilert integrates with monitoring, ticketing, chat, and collaboration tools.
See how industry leaders achieve 99.9% uptime with ilert
Organizations worldwide trust ilert to streamline incident management, enhance reliability, and minimize downtime. Read what our customers have to say about their experience with our platform.
Checkmk launched Checkmk Cloud (SaaS) in February 2025, which is a fully managed, cloud-based version of their monitoring technology. This solution, designed for ease of use, allows enterprises to start monitoring their IT infrastructure with no installation, maintenance, or manual upgrades required. The SaaS version is compatible with both cloud-based and on-premises systems, bringing them together under a single, straightforward platform.
As Checkmk is one of the popular monitoring solutions chosen by ilert users, we decided to dive deep and test this new SAAS version to provide you with a helpful guide on connecting your Checkmk monitoring with the ilert incident management platform.
If you get stuck or anything is unclear, reach out to the ilert support team via the chat widget. We are happy to help!
What this guide covers
This step-by-step guide will help you:
Set up and configure Checkmk Cloud Monitoring for cloud-based and on-premises infrastructure
Create a dedicated IAM user in your AWS account with the necessary permissions to allow Checkmk to access and monitor your AWS resources.
Build an intuitive dashboard to monitor performance, detect anomalies, and gain real-time insights.
Receive critical Checkmk alerts via multiple channels, like SMS, phone calls, messengers, or push notifications with the help of ilert.
Prerequisites: What you will need to follow this guide
A registered account on Checkmk.
AWS Account with API Access.
IAM (Identity and Access Management) access.
A Checkmk Cloud instance deployed and accessible via a browser.
A Windows-running machine.
Stage 1: Adding a Windows host via Checkmk agent
Adding hosts is now more straightforward with Checkmk Cloud, which supports deploying monitoring agents directly on target systems. This approach reduces the need for manual configuration and shortens setup time, helping administrators scale their monitoring infrastructure more efficiently.
Select the Windows agent package.
Open Powershell on your Windows machine and follow the instructions.
Navigate to the newly added host.
Stage 2: Creating an IAM User for Checkmk
In AWS, open the IAM service and go to users.
In the top right corner, click “Create User.”
Enter a User name.
In the next step, click Attach policy directly and select the ReadOnlyAccess in the Permission policies.
Click Create user.
Select the newly created user.
Click Security credentials.
Now, click Create access key.
Select Third-party Service, accept the confirmation message, and click Next.
Optional: Set a description tag.
An Access key and Secret key will be generated. You will need these two keys in the setup process for Checkmk Cloud cloud-based monitoring.
Stage 3: Adding an AWS host
On the sidebar, click Setup -> Hosts.
Click Add host.
Enter a Host name and set the IP address family to ‘No IP,’ then save the host.
In the sidebar, navigate to Setup -> VM, cloud, container.
Now, select Amazon Web Services (AWS).
Click Add rule.
Enter the access key ID and the secret access key from your AWS account into the corresponding fields.
Select the options you want to monitor.
Now, in the sidebar, navigate to Setup -> Hosts.
Select the previously created host.
Click Save & run service discovery.
Navigate to Setup -> Dynamic host management.
Click Add connection.
Enter a Unique ID and Title in the corresponding fields.
Enable ‘Automatically delete hosts without piggyback’ in the Delete vanished hosts settings.
Save the connection.
To apply the changes made, in the top right corner, click the Changes.
Now, click Activate on selected sites.
In the sidebar, navigate to Monitor -> AWS EC2 instances.
This view is a general overview of your EC2 Instances.
Stage 4: Build intuitive dashboards to monitor performance
Checkmk dashboards are customizable visual interfaces that provide real-time insights into the health and performance of your cloud and on-premises systems.
In the sidebar, navigate to Customize -> Dashboards.
Click on Add dashboard.
Select specific objects to which the dashboard is restricted. In this guide, we will set the restriction to: ‘No restrictions to specific objects.’
Click Continue.
Enter a Unique ID and Title and click Save & go to dashboard.
Now, navigate to Dashboard -> Enter layout mode.
Navigate to Add -> Combined graph.
Enter a Custom title for the graph.
Select the Service filter condition ‘Service (exact match)’ and enter ‘AWS/EC2 CPU utilization’ as the value.
Select ‘CPU utilization’ as Graph and select a desired Time range.
Click Save.
The Checkmk dashboard feature allows you to customize the size and layout of your dashboard fully.
To finalize the setup, navigate to Dashboard -> Leave layout mode.
Stage 5: Connect Checkmk Cloud with ilert
To connect Checkmk Cloud with ilert, add a new Notification rule of type ‘ilert’ and enter the Integration key of your Checkmk alert source in ilert.
By integrating Site24x7 with ilert, companies can automate their incident response workflows, ensure that the right people are notified instantly, and reduce Mean Time to Resolution (MTTR).
Site24x7 provides robust monitoring for servers, applications, networks, and cloud infrastructure, including application logs, giving teams visibility into their environments. But when things go wrong, a timely response is just as critical as visibility. This is where ilert comes in. In this article, we’ll explore how the Site24x7 + ilert integration works and how it helps teams improve operational efficiency and stay ahead of incidents.
What is Site24x7?
ManageEngine Site24x7 is an AI-powered observability platform for DevOps, SREs, and IT operations. Its cloud-based capabilities help monitor, predict, analyze, and troubleshoot problems related to the internet, websites, applications, microservices, servers, containers, virtualized and multi-cloud environments, and network infrastructure—all from a single console.
Why integrate Site24x7 with ilert?
While Site24x7 offers robust monitoring and observability features, teams still need a structured, reliable way to act on alerts. That’s where ilert shines. The integration allows you to:
Automatically create and resolve alerts in ilert based on Site24x7 events
Route alerts to the right on-call responders using ilert’s on-call schedules and escalation policies
Receive notifications through your preferred channels, including phone calls, SMS, mobile push, Microsoft Teams, Slack, and more
Suppress noise and avoid alert fatigue with ilert’s deduplication and filtering options
Collaborate during incidents, track timelines, and keep stakeholders informed using ilert’s incident communication features
By combining Site24x7’s monitoring capabilities with ilert’s alerting and incident management features, teams can move from detection to resolution in record time.
Who will benefit from this integration?
This integration is especially valuable for SREs and IT operations teams who need to detect, respond to, and resolve incidents quickly and efficiently. With real-time alerting from Site24x7 and ilert’s intelligent routing, teams can significantly reduce MTTA and MTTR.
For IT service providers and managed service providers (MSPs), the integration offers a scalable way to manage alerting across multiple clients. With customizable workflows, multi-tenant support, and detailed reporting, MSPs can consistently meet their Service Level Agreements (SLAs) and deliver high-quality support. The integration empowers all teams to move from monitoring to resolution—fast.
Setting up the integration
To integrate Site24x7 with ilert:
In ilert, create an alert source and select Site24x7.
ilert will generate a unique webhook URL.
In Site24x7, go to Admin > Third-party Integration > ilert.
At ilert, we do our best to provide as many sources as possible to send alerts to our platform. While our integrations catalog is constantly growing, Heartbeat is the only monitoring option available in ilert out of the box. It helps to check connectivity between users' systems and tools and ilert. With the recent update, we significantly improved this feature.
For those who have yet to try this feature in ilert, a monitor sends HTTP requests, aka heartbeats, at regular intervals to a chosen destination and checks if the signal is received on time. If the heartbeat fails to arrive, it means something might be wrong, and the monitoring tool triggers an alert.
First and foremost, a Heartbeat monitor is now a separate entity in ilert. Users will note that monitors are now live in the separate section of the navigation bar. This is not just a rearrangement; with this change, heartbeat monitors have received all vast alerting settings that other third-party integrations have in ilert, including various grouping and filtering options. So, to set up a new monitor, you will first need to visit the "Heartbeat monitoring” section and create a monitor that will ping the service in the chosen interval, and then visit Alert sources to specify alerting settings for a newly created monitor. Furthermore, this approach simplifies the management of monitors.
Additionally, with this change, all monitors can target one alert source, which means you can unify alerting settings for as many heartbeat monitors as you like. This significantly reduces time for adjustments, especially for teams with dozens of Heartbeats in ilert.
Heartbeat monitoring is included in all ilert plans, even the Free. However, users can now buy additional monitors as add-ons right from their account. Learn more about the add-on in the ilert pricing.
Email alert source reworked
Email as an alert source is now also more advanced than it was before. Emails sent to ilert are treated as alerts from other monitoring tools, meaning all templating, filtering, and dynamic routing settings are applied. The interface was also improved to simplify the setup.
Managing Holidays
ilert’s holiday feature, built into the Support Hours settings, makes it easy to manage exceptions to your regular support schedule. Whether it’s a national holiday, a company-wide day off, or any other irregular non-working day, you can account for it without manually editing your on-call rotations or escalation policies. It’s a smart, streamlined way to keep your team’s availability accurate—no last-minute adjustments required. You can either manually create holidays in ilert or transfer the list of days from a country-specific list. Continue reading a step-by-step instruction on how to set up holidays in ilert.
Status pages refinements
Status page widget live updates
Your users don't have to update a page to see the changes in the widget. The widget refresh is now automatic, so your clients will notice the updates as soon as they occur.
If you're using a custom domain for your status page, you can now integrate external analytics tools to better understand your audience. Whether you're curious about where your traffic is coming from or how users interact with your page, ilert supports two options: Google Analytics and PostHog. Just add your tracking key to connect your preferred platform and start gaining insights into your status page's performance and usage.
Call flow improvements
ilert hotlines can now forward calls directly to external support numbers, even if they use IVR menus—no confirmation needed from the other end. This update ensures smooth call handoffs without requiring manual workarounds or dedicated ilert users. It’s a simple way to connect your callers with third-party support while keeping your workflows clean and efficient.
With the latest release, you can easily copy a node or the whole subtree, or remove it by clicking the three dots. To paste the branch, simply copy it first, then choose a place where you'd like to add it, click the plus icon, and then click “Paste," which will appear as the first available action in the menu.
Also, it's simpler now to duplicate call flows. Just go to your Call flow list and click the three dots to create a copy of the previously created tree.
Additionally, choosing a voice that will accompany your call flow is easier now. You will find the AI voice menu at the top of the call flow editor. There, you can also test and listen to them all to pick the best option for your company. The voice of your choice will be applied to the whole call flow.
Voicemail is currently also visible in call logs. You will easily find left messages with the help of the icon in the Status column.
Audit logs enhancements
With the recent updates, you can download logs as a CSV file.
Furthermore, you can navigate to audit logs from the detail view pages of Call Flows, Escalations, Status Pages, Services, Metrics, and other features within ilert. For example, if you noticed changes in the Support hours, you can find a support hour schedule that you are interested in, click the three-dot icon on the right side of the screen, and choose “Go to audit logs.” It is a fast way to track changes and usage across your organization.
As a reminder, audit logs are available for ilert Enterprise customers. They are accessed via the Settings menu (the cog icon at the top right corner of the ilert navigation panel). If you want to enable Audit logs for your account, just message us at support@ilert.com.
ilert mobile app
While it's hard to enjoy the sound of incoming critical notifications, we did our best to improve this experience for you. You will find various sound options to ensure you never miss an incoming alert. We also introduced short and long tones, so you can choose something that will for sure catch your attention, but won't give a heart attack.
The list of incidents in the ilert mobile app is now enhanced with more filtering options. You can choose filtering by services, status pages, statuses, and time frames.
Also, the alert list and alert details look way better on mobile. We simplified and cleaned the interface to make it more intuitive to navigate the most critical section of the platform.
Call logs—incoming phone calls that go through your ilert call flows—are now also visible in the mobile app. If you are using the Call flow add-on, you will find logs in the navigation panel, right after the Incidents section.
Coverage requests are shown for 24 hours before they are moved to “Past requests” to give users more time to react and take a colleague's shift.
Remember to download the ilert mobile app for Android or iPhone.
AIOps is out of BETA
ilert AIOps is no longer in BETA version and is available for purchase as an add-on. The set of features is designed to make alerting smarter and more efficient by reducing noise and ensuring that only relevant alerts reach on-call teams. It automatically groups related alerts and filters duplicates so teams can focus on what really matters. It helps detect incidents faster, cut through the chaos during outages, and ultimately reduce alert fatigue. Read in our blog a detailed view on how ilert intelligent alerting features bring clarity and calm to incident response.
Minor improvements
Alert templates are supplemented by new fields: eventType and alertKey to help fine-tune alerting preferences.
More notification time options are available for ilert maintenance windows to provide you with more flexibility in informing your users and stakeholders about the upcoming maintenance. You can also double-check who will be notified by clicking “Show details” right below the "Schedule maintenance window” button.
The Alert sources menu is easier to navigate. You can use filters to find the needed solution. Don't forget that if you cannot find your solution in the list, simply leave the name of the tool in the field at the bottom of the page, and we will reach out to you for further use case clarifications.
More integrations
Find new alert sources in the ilert catalog!
Dash0—an AI-powered, OpenTelemetry-native observability platform that helps developers and SREs troubleshoot and resolve incidents faster by providing a high-quality experience for exploring logs, metrics, and traces—all in one place.
SAP Focused Run—an advanced operations platform designed for large-scale IT landscapes, providing high-volume system monitoring, alerting, and analytics for SAP and non-SAP environments.
IT Conductor—a patented, cloud-based service orchestration and automation platform designed to monitor, manage, and orchestrate enterprise IT through intelligent automation. It provides full-stack SAP monitoring, management, and orchestration, streamlining end-to-end management of the entire SAP landscape.
Checkmk integration was enhanced. It now has a bi-directional option, so users can acknowledge, clos, or annotate Checkmk events from ilert.
Moreover, we introduced Argo CD in the list of ilert deployment integrations. ArgoCD is a GitOps tool for Kubernetes that automates deployments by syncing the desired state from Git, ensuring consistent and auditable releases. With the ilert Deployment integration for Argo CD, you can display your deployment pipelines in ilert and expand the context of alerts.
.png)
.png)
.png)
