All-in-one Incident Management Platform

We are excited to announce the integration of ilert with IT-Conductor, a SaaS-based IT operations management and automation platform. This partnership enhances IT-Conductor’s powerful capabilities with ilert’s advanced alerting and incident management, ensuring that IT teams can address issues faster and more efficiently.

What is IT-Conductor?

IT-Conductor is a patented, cloud-based service platform designed to monitor, manage, and orchestrate enterprise IT through intelligent automation.

‍

As a global remote trusted advisor for enterprise customers, the platform delivers comprehensive solutions to optimize IT and business operations, including application performance management, cloud migration, and workflow orchestration. By leveraging intelligent automation, IT-Conductor empowers customers with a trusted partner to manage and automate end-to-end service delivery, enabling seamless management of their entire IT services portfolio. Key IT-Conductor's services include:

‍

• End-to-end SAP monitoring: Continuous tracking of SAP, databases, cloud services, and infrastructure components. The platform offers real-time performance analysis, proactive issue detection, and automated anomaly resolution.
• SAP automation: Automated health checks, performance tuning, and system maintenance for SAP environments.It streamlines SAP operations by automating transport request management, reducing deployment risks, and optimizing system refresh tasks. 
• IT process orchestration: Workflows to automate repetitive tasks, reducing manual efforts and minimizing errors.
• Automated migration: Enables organizations to transition smoothly to SAP on RISE and S/4HANA with pre-migration assessments, automated testing, and post-migration validation. Additionally, the platform simplifies complex IT migrations by automating data transfers, infrastructure provisioning, and application deployments, ensuring minimal downtime and risk-free transitions across on-premises, cloud, and hybrid environments.

‍

IT-Conductor is trusted by companies such as Panasonic, Under Armour, Day & Zimmermann, and other globally recognized enterprises.

How ilert complements IT-Conductor

While IT-Conductor provides deep insights and automation for IT environments, ilert ensures that the right people are notified and can take action promptly when issues arise. Here’s how ilert enhances IT-Conductor’s capabilities:

‍

• Intelligent incident management: ilert filters, groups, and prioritizes alerts from IT-Conductor, reducing noise and preventing alert fatigue.
• On-call scheduling: Ensures that the right team members are notified based on predefined schedules and escalation policies.
• Multi-channel notifications: Delivers alerts via SMS, phone calls, push notifications, and chat tools like Slack and Microsoft Teams.
• Incident collaboration: Enables real-time communication and response workflows, ensuring faster incident resolution.

‍

By integrating with ilert, IT-Conductor users can respond to SAP monitoring issues more efficiently, improving service reliability and minimizing downtime.

How ilert benefits SAP users

By integrating IT-Conductor’s automation with ilert’s incident management capabilities, SAP teams can minimize downtime, optimize operational efficiency, and maintain business continuity. IT-Conductor automates many aspects of SAP monitoring, but when critical issues occur—such as performance degradation, failed jobs, or system unavailability—fast response is crucial.

‍

Consider a large enterprise that relies on SAP for its core business functions. IT-Conductor continuously monitors SAP systems, conducting automated health checks to detect potential problems. If a critical issue arises—such as high database latency or an unresponsive system—IT-Conductor immediately generates an alert.

‍

Without an effective incident management system, such issues may go unnoticed, causing operational disruptions. This is where ilert comes into play:

‍

1. IT-Conductor identifies the issue and triggers an alert.
2. The alert is forwarded to ilert, which assesses its severity and determines the necessary response.
3. ilert immediately notifies the on-call team through multiple channels, including phone calls, SMS, and push notifications, ensuring prompt attention.
4. If no response is received, ilert escalates the issue to the next support level, ensuring it does not go unresolved.
5. Once resolved, ilert updates the incident status, maintains a detailed log for future analysis, and provides insightful post-mortems to help teams understand the root cause and improve future incident response.

‍

By combining IT-Conductor’s SAP monitoring and automation with ilert’s incident management capabilities, SAP teams can prevent downtime, improve operational efficiency, and ensure business continuity.

Connect ilert and IT-Conductor in a few simple steps

It's very easy to start sending alerts from IT-Conductor to ilert. First, find IT-Conductor among other alert sources in ilert.

Assign the alert source to a team and connect it to one of your escalation policies, or you can create one on the go. Choose if you want to group alerts, enable the alert template, and specify notification priority. At the end of the setup, you will receive a webhook URL. Copy it proceed to the IT-Conductor interface.

‍

In IT-Conductor, navigate to the Integrations section and find ilert there. Create a new integration and add previously saved webhook URL.

For more detailed information check ilert step-by-step guide for the IT-Conductor integration.

Conclusion

The integration between IT-Conductor and ilert brings together advanced IT automation and reliable incident management to enhance SAP monitoring. IT-Conductor streamlines SAP performance tracking and management, while ilert ensures rapid incident response and collaboration.

‍

For SAP users, this integration means fewer disruptions, faster problem resolution, and a more resilient IT environment. Whether you’re managing SAP landscapes or other critical IT systems, IT-Conductor and ilert together provide a powerful solution for automation and incident management.

‍

‍

When the mobile app is a Progressive Web App (PWA) and shares a common codebase with the desktop web app, porting components from web to mobile often requires only minor adjustments to align with platform-specific nuances. However, this seemingly straightforward process comes with its own set of challenges. In this article, I’ll explore some of the common pitfalls to watch out for when migrating components.

‍

By the way, if you are curious about what framework we at ilert use for our mobile app, read our article “Ionic vs. React Native: Which one should you choose for mobile apps?”

‍

What is a Progressive Web App (PWA), and why is desktop-to-mobile migration straightforward with it?

Feel free to skip this chapter if you have already worked with PWAs. 

‍

A Progressive Web App, also known as PWA, is a web app that combines the best of both worlds. PWAs use modern web capabilities like offline support, push notifications, and installability while running in a browser. Since a PWA shares a single codebase across platforms, moving components from a desktop web app to a mobile PWA is often easier than moving to a fully native mobile app. Many components can be reused with minimal changes, just adapting to touch, screen sizes, and mobile UI patterns. However, while the shared codebase saves development time, user behavior and platform constraints still require thoughtful tweaks to make it seamless across devices. So, let's see what are those constraints. 

Touch vs. click / Finger vs. cursor

The most obvious but still crucial difference is how the user interacts with desktop and mobile applications. For accessibility, action areas in a mobile app have to be bigger. Hovering over components is not available with touch, only in a focused or active state. 

‍

For example, in a web app, a dropdown menu with hover effects works well because users can precisely navigate with a cursor. On mobile, the same dropdown becomes frustrating to use. Instead, a modal or a full-screen menu with large touch targets is a better solution.

‍

In the web app, the code for this component in JSX would look something like this:

1<Popover>
2	<PopoverContent>
3		<Stack>
4			<Searchbar />
5			<List />
6		</Stack>
7	</PopoverContent>
8</Popover>
9

‍

Transforming this component to mobile, using the Ionic framework, this looks in JSX like this:

1<IonModal>
2	<IonHeader>
3	   <Searchbar />
4	</IonHeader>
5	<ModalContent>
6		<IonList>
7			<IonItem>
8				<IonListHeader>
9					<IonLabel>Option 1</IonLabel>
10				</IonListHeader>
11			</IonItem>
12   		  	…
13   	 </IonList>
14	</ModalContent>
15</IonModal>

‍

A Modal ensures full-screen content, while the List with items provides large touch targets. If less customization is necessary, Ionic also provides another component specifically for dropdowns, which leads to even easier migration:

1<IonSelect value={selectedValue} onIonChange={handleChange}>
2	<IonSelectOption value="option1">Option 1</IonSelectOption>
3	<IonSelectOption value="option2">Option 2</IonSelectOption>
4	<IonSelectOption value="option3">Option 3</IonSelectOption>
5</IonSelect>

‍

A similar problem occurs with tooltips. On the desktop, users can hover over items, and tooltips appear with additional information. No hover is available for mobile devices. Holding over items suggests an action menu rather than a tooltip with brief text. In such cases, it’s better to display information without hiding it or using another modal).

Visual differences

Mobile screens are smaller and allow content to grow only vertically, while web apps usually have more space horizontally. Thanks to the screen sizes, content can grow in both dimensions.

‍

For example, in a web app, a navigation bar displays all menu items horizontally. While on mobile, the same navigation bar collapses into a hamburger menu to save space.

‍

Another example is when working with popovers: while popovers are sufficient on the web app, on mobile, they often don't have enough space to display their content. This becomes even clearer when one of the components inside the popover is a dropdown menu, requiring another modal on mobile. The solution here is to stack multiple modals over each other, providing enough space for each component to be displayed.

Performing actions

Navigating with a cursor allows for more precise movements and clicks, reducing accidental actions. On mobile, the combination of small screen size with touch results in more mistakes when using an app. To tackle this problem, mobile apps often need confirmation steps and smart placement of action buttons.

‍

‍

While the accept button at the top is sufficient for desktops, having it at the bottom of the action bar makes it accessible to click with the thumb.

Steps to Migrate Desktop Components to a Progressive Web App 

The final migration from the desktop app to the PWA depends heavily on the complexity of the components, the final use case, and whether a component library is used. 

Roughly, these steps should be followed:

• Identify reusable components
• Replace hover states
• Implement touch actions
  
  • Simplify interactions if necessary
• Check whether orientation change is needed
• Scaling fonts/visuals for screen size

‍

Using a component library (like Ionic) immensely helps in the process as it offers a platform-specific style change to match the device while also providing native functionality. However, if components and design are consistent across devices, further work is needed, and a custom solution from the start may save a lot of migration work.

We are pleased to announce a new inbound integration in the ilert catalog: RapidSpike. This integration enhances incident management by connecting ilert with RapidSpike’s website monitoring capabilities, ensuring teams receive real-time alerts on website performance, uptime, and security threats.

What is RapidSpike, and How Do ilert users benefit?

RapidSpike is a comprehensive digital experience monitoring platform that enables businesses to maintain optimal website performance, security, and availability. It provides synthetic monitoring, which simulates user interactions to identify performance bottlenecks proactively. 

‍

Additionally, RapidSpike offers cybersecurity insights, helping organizations detect vulnerabilities, prevent security breaches, and ensure compliance with industry standards. By continuously assessing website performance and security, RapidSpike allows businesses to enhance user experience, protect sensitive data, and maintain high availability.

‍

With the ilert + RapidSpike integration, users can:

‍

• Receive instant alerts in ilert when RapidSpike detects downtime, slow load times, or security risks.
• Automate incident response by routing alerts to the right teams through on-call schedules and escalation policies.
• Reduce alert fatigue with ilert’s smart notification rules and AI-powered noise reduction.
• Improve service reliability by correlating RapidSpike events with other monitoring tools in one centralized incident response platform.
• Track and analyze alerts and incidents with the help of reports to improve long-term reliability.

ilert and RapidSpike: Ideal combination for Retailers

Both ilert and RapidSpike serve retailers across Europe by providing essential tools to maintain high website availability, security, and performance. Retailers of all sizes rely on seamless digital experiences to maximize customer satisfaction and revenue. 

‍

This integration offers a comprehensive monitoring and incident response solution, enabling companies to detect and resolve issues swiftly. For small and medium-sized retailers, this combination ensures a cost-effective and reliable way to manage uptime and mitigate performance risks. Larger enterprises benefit from advanced automation and real-time alerting, allowing IT and operations teams to respond proactively to incidents.

‍

With ilert and RapidSpike working together, retailers of different sizes can ensure their websites remain operational, secure, and optimized—regardless of business size or technical complexity.

How to use the integration

To send alerts from RapidSpike to ilert, begin by locating RapidSpike among the other alert sources in the ilert interface.

Next, follow the on-screen instructions to configure the settings for RapidSpike. Once you have set everything up, copy the generated URL and log into your RapidSpike account. There, select the Webhook integration option in the RapidSpike user interface and paste the Webhook URL into the designated field.

Check the complete step-by-step guide on how to connect ilert and RapidSpike, and feel free to reach out to the ilert support team if you have any questions.