ilert seamlessly connects with your tools using our 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.
The end of the year brings pressure. (Oh, we know!) Customer demand spikes, response expectations stay high, and engineering teams are juggling production issues, releases, and time off. For many teams, this is when on-call becomes chaotic: schedules break, notifications hit at the wrong time, and coverage gaps appear exactly when you can’t afford them.
ilert's Holidays and Support hours features were built to fix that. They simplify on-call management, protect your team’s time, and keep organizations running smoothly.
In this article, we’ll cover how these features help to stay in control, prevent burnout, and create predictable, reliable schedules even during the busiest seasons. And at the end, you’ll find a practical bonus chapter: how to stay healthy, sane, and avoid burnout during this pre-holiday rush.
End of the year – a crash-test for your on-call routine
On-call management gets complicated when support expectations vary across regions, customers, or time zones. Add holidays and PTO season on top, and teams often resort to spreadsheets, Slack pings, or “please cover my shift” chaos.
End-of-year operations already demand tight focus. Yet many teams still patch schedules manually with spreadsheets, emails, or Slack threads. These small improvisations add up, pulling engineers and managers away from solving the real problems and into administrative firefighting.
Holidays and Support hours solve this by giving teams precise, automated control over when alerts should trigger and who should handle them. The result: fewer interruptions, cleaner routing, and schedules that reflect real-world availability.
Let's first look at the Support hours feature.
The Support hours feature in ilert lets teams define exactly when alerts should fire and how they should be routed using time-based rules. It acts as a guardrail that checks whether an event happens during business hours, outside them, or during specially defined windows. This allows teams to tailor behavior depending on urgency: critical incidents can escalate 24/7, while lower-severity issues can quietly wait until the next morning.
Support Hours can be simple (weekdays 9–5) or highly structured with multiple blocks, time zones, and logic layers. They’re ideal for organizations with different SLA tiers, global customer bases, or engineering teams who want to protect nights and weekends from non-urgent noise.
Holidays take this concept further. Internally, we jokingly call them “Support Hours on steroids.”
They let teams automatically exclude national holidays, company-wide days off, or regional observances from regular support windows. Instead of manually adjusting schedules every time a holiday rolls around, ilert matches your service hours with the relevant holiday calendar and automatically adapts routing.
This is especially powerful for distributed teams with country-specific holidays, or anyone who was accidentally paged on Christmas morning. Holidays ensure your escalation flow reflects the real world: fewer surprises for engineers, and cleaner operational coverage when the office lights are off.
Here is why your future self will thank you
We established Support hours and Holidays for fundamental reasons. We receive numerous support tickets daily, but December is a unique peak season, and we understand the challenges our customers face. Do any of these sound familiar to you?
Coverage gaps appear at the worst time. With engineers taking well-earned time off, gaps in coverage become inevitable unless schedules adapt automatically. Without that automation, the burden shifts unevenly; someone ends up carrying extra on-call weight, or – worst of all – an engineer gets notified during their holiday. These gaps hurt morale and directly slow down incident response when uptime matters most.
Manual fixes drain time you don’t have.Year-end work already demands focus, yet many teams still scramble through spreadsheets or Slack threads to patch schedules. These last-minute adjustments consume engineering time that should be spent on stabilizing systems, shipping features, or preparing for traffic spikes – not babysitting calendars.
Escalations become noisy and inaccurate.When support hours and holidays aren’t fully integrated into the on-call logic, alerts fire at the wrong moments. People get pinged outside business hours, or urgent issues quietly fall through the cracks. In a peak season full of customer activity, misrouted alerts escalate quickly into incidents, impacting customers and leaving unpleasant red spots on your status pages.
International teams feel the complexity even more. Distributed teams deal with a patchwork of national holidays, cultural observances, and regional support-hour rules. Without a system that adapts to each region’s calendar, some teams get overloaded while others are unintentionally under-utilized. This imbalance becomes especially dangerous when global usage spikes.
Customers don’t pause their expectations. Even while internal teams slow down or go on vacation, SLAs keep ticking. Customers expect the same level of responsiveness, and any misalignment between support contracts and on-call coverage becomes painfully visible. Poorly controlled support hours during the busiest season don’t just inconvenience engineers – they damage trust.
Bonus: 8 tips for engineers on duty to avoid burnout during the pre-holiday rush
Enhance your alerts. Clean up noisy monitors, retire outdated checks, and tune thresholds before traffic spikes. A quieter, more accurate alert setup pays off massively during high-stress weeks.
Automate what you can. Small automations, such as log parsers, deployment scripts, and error-notification filters, save hours when systems get noisy.
Use rotations effectively. Make sure on-call responsibilities are distributed fairly, and that holidays are properly reflected so no one works a stretch longer than they should.
Rehearse failovers and edge cases. Run quick simulations or tabletop exercises with your team. Knowing how systems behave under load removes guesswork when real issues hit.
Configure safety nets. Enable auto-remediation where appropriate, make sure backup contacts are defined, and double-check that escalations route correctly if someone is unavailable.
Share context proactively. Post short updates in Slack or your incident channel about ongoing issues, infrastructure changes, or known risks. The next person on-call shouldn’t have to rediscover what you already know.
Lean on your tools. Features like Support Hours and Holidays exist to reduce mental load. Let them do the heavy lifting so you don’t have to think about schedules or routing.
If an incident happens, debrief faster. Short, focused post-incident reviews help teams resolve patterns quickly without sinking hours into analysis.
Modern SRE and IT operations run on two truths: you must see problems the way users do, and you must respond fast. With the new ilert and Ekara integration, you can turn Ekara’s powerful synthetic and real-user insights into actionable alerts and incidents in ilert – routed to the right on-call engineer, enriched with context, and communicated to stakeholders via status pages. The result: fewer surprises, faster recoveries, and happier users.
What is Ekara?
Ekara by the French company ip-label is a digital experience monitoring platform that combines synthetic monitoring (robots) and Real User Monitoring to detect and diagnose issues across web, mobile, APIs, business apps, and voice/IVR – deployed as SaaS, hybrid, or fully on-prem. Ekara offers no-code journey scripting, Edge/branch monitoring, and options like Flow AI and AI Incident Guard. The platform processes billions of measurements daily and is used by 400+ customers across 25 countries.
Ekara is used by enterprises across e-commerce, travel, finance, public sector, and contact centers to see performance the way users do. PVCP Group, for example, models key booking journeys to catch issues before they hurt conversions. Contact centers and telecoms run Ekara’s IVR/Voice probes to validate call flows and speech quality. Hybrid IT teams monitor thick-client and Citrix apps alongside web and APIs, including from edge sites with Ekara Pod. In short, it helps diverse teams spot real user problems early and act fast.
Why connect Ekara to ilert?
Ekara detects problems and sends alerts. ilert turns those alerts into actionable notifications and gets the right people moving fast if issues have a business impact.
Faster response: When Ekara sends an event, ilert notifies the on-call teams via voice, SMS, push, Slack, or Microsoft Teams. No manual steps, no guesswork.
Less noise, clearer focus: Similar alerts from the same scenario or region are grouped into one. Teams identify one problem to fix, rather than multiple duplicates.
AI that speeds you up: ilert offers powerful AI features, all designed to reduce the time to resolution. ilert AI summarizes incoming information, so responders start with context, not a blank page. It also helps prepare clear status updates and later assembles blameless postmortems. AI is integrated into every stage of incident response to reduce manual burden and enable teams to react quickly.
Keep everyone informed: using ilert public and private status pages, users can keep customers and stakeholders informed.
Step-by-step setup
Create Ekara's Alert source in ilert. Copy the Webhook URL.
Configure Ekara to send alerts. Choose the events to forward: failure, recovery, threshold breach, and SLO alert.
Test and verify. Trigger a test failure in Ekara. Confirm an alert opens in ilert and pages the current on-call.
A complete step-by-step guide is available at doc.ilert.com. If you experience any issues or have questions, feel free to reach out to the ilert support team at support@ilert.com.
Managing alert routing in complex environments is hard. When events occur, alerts must reach the right people at the right time, but traditional alert sources struggle with sophisticated, context-aware routing. Event Flows is ilert’s node-based workflow system at the heart of our alerting infrastructure. It enables intelligent event processing, time- and context-based routing, and safe automation, so teams reduce alert fatigue and accelerate incident response.
The pain points Event Flows address
As monitoring footprints grow, standard alerting patterns show limits. Event Flows targets four recurring pain points:
Complex routing logic. Standard alert sources may route by priority or keywords, but real-world scenarios demand decisions based on event content, custom fields, error patterns, context, and time. Different escalation paths are needed depending on the situation.
Time-based routing. During support hours, alerts go to the primary on‑call; after hours, they may escalate to a different team or follow a different policy. Without Event Flows, this often requires multiple alert sources or brittle external logic.
Context-aware decisions. The same signal can have different meanings depending on the context. A database connection error might be critical during peak hours but informational during maintenance windows. Reducing alert noise requires routing that evaluates business context.
Maintenance overhead. Managing many slightly different alert sources increases operational complexity and the risk of configuration drift. A single, expressive workflow reduces duplication.
Architecture and integration
Event Flows sits between ingestion and alert source routing to deliver smart, reliable processing. It defines how incoming events are processed, transformed, and routed through a configurable sequence of logical components. Let’s take a closer look at the key components that make Event Flows both powerful and adaptable in practice.
Node-based flow builder. A tree-structured builder defines event-processing workflows. Current node types:
Branch: create scenarios based on conditions.
Route to alert source: direct events to a specific alert source.
Support hours: route using predefined support hours.
Queue-based processing. Events arriving via ilert’s event API are first processed by Event Flows, then routed to alert sources. Processing uses AWS SQS FIFO with message groups per API key. This preserves ordering for events from the same alert source and prevents race conditions while keeping near real-time behavior.
Deterministic execution. Each node evaluates conditions and chooses the next step. Execution context is preserved across nodes, enabling decisions that build on prior computations.
Data model. Event Flow contains multiple Event Flow Nodes; each node has Event Flow Branches defining conditions and targets, mirroring the hierarchical execution path.
Powerful automation with ICL (ilert Condition Language)
Event payload – e.g. event.priority, event.summary, event.source, custom fields
Time context – business‑hours, weekends, maintenance windows
Accumulated context – values written by earlier nodes
Examples
Route by priority:
Match text safely:
Time-based routing using support hours:
Combine multiple checks:
Conclusion
Event Flows brings intelligent context-aware routing to ilert’s alerting stack. With a node-based builder and the ilert Condition Language (ICL) for advanced logic, teams can enrich and route events before they become alerts. Strong reliability guarantees ensure less alert noise, fewer misroutes, and faster, more consistent responses.
.png)
