At ilert, one of the key tools in our debugging process is the Event Explorer, which provides an extensive overview of incoming events and their processing lifecycle. In this article, I will explain more about the capabilities of Event Explorer.
In this article, we’ll share the structured checklist that we use to measure and optimize ilert's PWA performance.
At ilert, we build our Progressive Web App (PWA) using Capacitor, Ionic, React, and MUI to deliver a robust and responsive incident management platform. Progressive Web Apps are revolutionizing web experiences by combining the best of web and mobile applications. They offer fast native-like experiences, offline capabilities, and many more.
However, ensuring high performance is crucial for providing users with a smooth and engaging experience.
Understanding progressive web apps
Feel free to skip this chapter if you already have experience with progressive web apps.
Progressive web apps (PWAs) are a type of web application that provides a native app-like experience to users. Built using web technologies such as HTML, CSS, and JavaScript, PWAs are designed to work seamlessly across multiple platforms and devices. One of the standout features of progressive web apps is their ability to deliver a smooth and engaging user experience, even in areas with poor internet connectivity.
Unlike traditional websites, PWAs are designed to be installed on a user’s device, allowing for offline access and push notifications. This means users can continue to interact with the app even when they are not connected to the internet.
Additionally, unlike native apps, PWAs are not platform-specific and do not require a separate codebase for each platform, making them a versatile and cost-effective solution for developers.
PWAs come with several core features that set them apart from traditional web applications and native apps. These features include:
Offline functionality: Thanks to caching and service workers, PWAs can function even when the user is offline or has a poor internet connection. This ensures that users can access essential features and content without interruption.
Installability: PWAs can be installed on a user’s device, providing the convenience of offline access and the ability to send push notifications.
Custom offline page: When users are offline, PWAs can display a custom offline page, enhancing the user experience by providing useful information or alternative actions.
Push notifications: PWAs can send push notifications to users, keeping them engaged and informed even when the app is not open.
App window: PWAs can be displayed in a custom app window, offering a native app-like experience that feels integrated with the device’s operating system.
Why progressive web apps performance matters
Performance is a critical factor for PWAs as it directly impacts user experience. Users perceive the performance of a PWA as critical to their overall experience, influencing their engagement and satisfaction. A fast-loading and responsive PWA encourages users to stay, interact, and utilize its features effectively.
One of the key metrics in performance evaluation is Time to Interactive (TTI). This is the time it takes for a PWA to become fully interactive.
Ideally, your TTI should be below 3.8 seconds, which is considered fast and ensures a smooth user experience. A TTI between 3.9 and 7.3 seconds indicates moderate performance that needs improvement, while anything above 7.3 seconds is considered slow and likely to increase frustration and bounce rates.
Measuring PWA performance
Before optimizing your PWA, it’s essential to establish a baseline by measuring current performance. Here are some effective ways to evaluate your PWA’s speed and responsiveness:
Browser developer tools: Inspect loading times and resource usage in Chrome DevTools.
Manual testing: Just clicking through the app can actually reveal a lot of performance issues and bad UX. Doing this after developing a new feature can bring significant insights for optimization.
At ilert, manual testing is an important part of our performance evaluation. Whenever we develop a new feature, we actively test it by navigating through the app, identifying potential performance issues, and ensuring a smooth user experience. Manual testing also helps to identify performance issues that automated tools might miss.
Following our performance checklist, we can proactively address issues before they impact our users.
Checklist: Improving PWA performance
1. Optimize bundle sizes
Reduce bundle sizes: Remove unused code and load images from a CDN to minimize bundle sizes.
Implement code splitting: Only load the necessary scripts and components that are required for the current page.
2. Implement Lazy Loading
Don't load images and content until they are needed.
Use skeletons wisely: Avoid excessive placeholders that may cause unnecessary lag.
3. Minimize artificial loading times
Eliminate unnecessary delays: Review intentional load times to ensure they are essential for UX.
4. Optimize app size
Trim audio files: Reduce unnecessary sound assets or cut them shorter.
Ensure a fast backend: Reduce API response times through efficient backend design and optimized queries.
We are actively making incremental improvements with our PWA. Small changes such as optimizing skeleton loaders, reducing JavaScript bundle sizes, and ensuring a fast backend have significantly reduced load times and improved our time to interactive (TTI). Feel free to copy the checklist from the article and use it when reviewing your PWA next time.
We weren't caught by surprise by Atlassian’s recent announcement that Opsgenie will end sales in the summer of 2025 and discontinue the service in 2027. We heard from new clients who decided to favor ilert over Opsgenie that the Atlassian platform has stagnated for some time now. What did surprise us, however, were the alternatives Atlassian offered its existing Opsgenie users.
We decided to write this explainer to help users make a knowledgeable decision and migrate smartly. For all Opsgenie users who are considering a migration, we offer additional demos and help to simplify the process. Just fill in the form below, and we will contact you for further support.
Request a consultation to migrate from Opsgenie
Jira Service Management vs. Real-time incident management
First of all, while we see an opportunity in this situation, Opsgenie EOL is sad news. The company was among the pioneers who built the category of incident management platforms. Opsgenie was a big whale, and it's heartbreaking to know that years of engineers' efforts are soon going on the shelf.
So, Atlassian is now offering Opsgenie's users to choose between two other solutions: Jira Service Management and Compass. None of these two actually covers the need for a centralized alert dispatcher and incident management. Each of the two covers a specific use case and misses one or another part of good old Opsgenie. Let's take a closer look.
Jira Service Management (JSM) is Atlassian’s ITSM solution. While it does offer some incident response functionalities, it is fundamentally a ticketing system designed primarily for IT support teams rather than engineering and on-call teams.
You can read more about the major differences between real-time incident management platforms and ITSM in our Buyers’ Guide.
JSM provides features such as request management, change management, and asset management, which are valuable for structured IT workflows. It also integrated some of Opsgenie's features, like alerting and escalations. However, those don’t replace the end-to-end incident management solution that must be a central point of all critical events and accompany teams at all stages of an incident. For example, to use status pages, JSM users will have to employ an additional solution, like Atlassian Status Pages.
Also, the plans that JSM offers are way more demanding, especially for small teams that are only starting their incident management journey.
This brings us to Compass, the second option Atlassian offers to Opsgenie customers. But does it fill the gaps that JSM leaves? Let’s see.
Compass – a developer portal, not an incident management solution
Compass is Atlassian’s other alternative for Opsgenie users, but calling it a replacement would be a stretch. Unlike JSM, which is focused on ITSM workflows, Compass is a developer portal designed to help teams track and manage their software components, dependencies, and service health.
At its core, Compass is meant to improve software visibility and collaboration. It provides teams with a centralized place to document service ownership, monitor service performance, and establish best practices across microservices. While this is useful for reducing long-term operational overhead and improving developer experience, it doesn’t offer critical tools for proper incident management and communication. Compass, like JSM, isn't meant to cover all incident lifecycle stages.
While the solution does integrate with observability tools to surface insights about service reliability, it lacks the automated workflows needed to act on those insights. There’s no built-in way to ensure alerts reach the right engineers at the right time, no comprehensive and adjustable call routing to prevent incidents from slipping through the cracks, and no Stakeholder role for fine-tuned communication. And there is no support for the European region.
That's something that is worth a dedicated paragraph about: only the US region is supported in Compass.
You can check the full list of “there is no” in the official Atlassian documentation under “Deprecated features in Compass”. In short, Compass is a great tool for maintaining software health over time, but it doesn’t answer the immediate needs of on-call teams.
So, where does this leave Opsgenie customers looking for a proper incident management solution? Let’s talk about why ilert is the best alternative.
Why ilert is the best Opsgenie alternative
If you’re an Opsgenie user looking for a true replacement, neither Jira Service Management nor Compass will fully cover your needs. That’s where ilert comes in.
Unlike Atlassian’s suggested alternatives, ilert is built for incident response—not just ITSM workflows or developer documentation. It combines on-call scheduling, alerting, and incident management in a way that ensures no critical issue goes unnoticed.
Powerful on-call management: ilert offers flexible on-call schedules, escalation policies, and overrides that ensure incidents always reach the right person at the right time.
Multi-channel alerting: Whether it’s phone calls, SMS, push notifications, or messengers, ilert ensures teams are alerted instantly and reliably.
Broad integrations: ilert seamlessly integrates with the monitoring, observability, automation, and ITSM tools you already use, including AWS solutions, Datadog, Prometheus, ServiceNow, and (yes) Jira. We also built our integrations in a way that provides users with absolute freedom to filter and template alerts.
ChatOps is an inherent part of incident management: we sincerely believe in it, and we don't charge extra for ChatOps capabilities.
Built-in CI/CD pipelines: Real-time visibility into your deployment events helps to pinpoint whether a recent deployment triggered an incident, saving valuable time during critical moments. ilert natively integrates with the most popular CI/CD solutions.
The most advanced call-routing on the market: ilert provides a powerful hotline for on-call engineers to automate incident response, nurture relationships with customers and stakeholders, and deliver fast support in emergencies.
Best choice for European Companies: Unlike many competitors, ilert is hosted in the EU, ensuring compliance with GDPR and other European data protection regulations. Our infrastructure is optimized for European customers, providing low-latency alerting and regional support. For organizations that require data residency within the EU, ilert is the clear choice over U.S.-based alternatives.
And in case you’re wondering about our future: we’re not going anywhere. ilert GmbH is a German, bootstrapped company: motivated, independent, and resilient. We use our own solution every day to maintain 99.99% platform uptime. Our customers know us personally, and we take pride in giving them the support they deserve.
Last thoughts
Atlassian’s decision to sunset Opsgenie means teams need to rethink their approach to incident management. While JSM and Compass serve different use cases, neither fully replaces the capabilities Opsgenie users rely on.
At ilert, we are fully dedicated to incident response. Our platform is a centralized dispatcher for all critical events, be it alerts from monitoring tools, phone calls, or tickets. It is a future-proof solution for teams that need fast and effective incident management—without compromise.
Many teams have already switched to ilert to keep their operations running smoothly. We'd love to help you find the right solution if you're exploring alternatives.
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:
IT-Conductor identifies the issue and triggers an alert.
The alert is forwarded to ilert, which assesses its severity and determines the necessary response.
ilert immediately notifies the on-call team through multiple channels, including phone calls, SMS, and push notifications, ensuring prompt attention.
If no response is received, ilert escalates the issue to the next support level, ensuring it does not go unresolved.
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.
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.
.png)
.svg)
.png)
