Introduction

Planned maintenance is a normal part of IT operations. Servers are upgraded, applications are updated, and individual components may be temporarily unavailable while engineering teams complete scheduled work. However, maintenance on one component does not always mean the entire service should be treated as under maintenance.

If only a specific production server or application function is undergoing planned maintenance, applying maintenance to the entire service can affect unrelated incoming events. Callgoose SQIBS addresses this through Maintenance Tags, allowing teams to apply full or partial service maintenance based on matching data within API request payloads or email bodies.

Understanding Maintenance Tags

Maintenance Tags help control how maintenance applies to incoming API or email requests. If the tags are left empty, the service is fully under maintenance. When Maintenance Tags are configured, the service can be partially under maintenance based on the incoming request data.

Callgoose SQIBS checks the configured tags against the API request payload or email body. If the request matches a configured maintenance filter, the service is considered under maintenance for that request. If no filter matches, the service is considered not under maintenance for the request and continues through normal processing.

This allows teams to apply maintenance to relevant events without treating every event associated with the service in the same way.

How Maintenance Filters Work

Maintenance Tags can be organized into multiple filters. The filters use an OR condition between each filter, while the tags within an individual filter use an AND condition. If any one filter is successful, the request is considered under maintenance. For a specific filter to succeed, all tags configured within that filter must be present in the incoming payload.

For example:

Filter 1: production-server01

Filter 2: production-server02 AND user-registration

If the payload contains production-server01, Filter 1 succeeds and the request is considered under maintenance. If the payload contains only production-server02, Filter 2 fails because user-registration is not present, and the request is not considered under maintenance. If the payload contains both production-server02 and user-registration, Filter 2 succeeds and the request is considered under maintenance.

This filter logic gives teams more precise control over which incoming events are associated with planned maintenance.

Partial Maintenance Instead of Full-Service Maintenance

A single service may receive operational events from multiple servers, application functions, or infrastructure components. Planned maintenance may affect only one of those components.

With Maintenance Tags, teams can define the specific event data associated with the component under maintenance. Matching API or email requests are treated as maintenance-related, while non-matching requests continue to be processed normally.

For example, if production-server01 is under maintenance, teams can configure it as a Maintenance Tag. Events containing that text match the maintenance filter. Events related to other servers that do not match the configured filter continue through normal service processing.

This helps reduce unnecessary event suppression while maintaining visibility into unrelated operational activity.

Maintenance Logs for Requests During Maintenance

When an incoming request matches the configured condition filter while the service is under maintenance, the request is not processed even if the condition is true. Instead, Callgoose SQIBS keeps the request as a Maintenance Log for future use.

This provides a record of requests received during the maintenance period. While Maintenance Tags determine which requests are treated as maintenance-related, Maintenance Logs retain those matching requests rather than processing them during maintenance.

This gives teams visibility into the requests received while maintenance was active without allowing those matching requests to continue through normal processing.

Using Request Data to Control Maintenance

Callgoose SQIBS checks Maintenance Tags against text contained in the API request payload or email body. Teams can use identifiable information already present in incoming event data to define maintenance filters.

These tags may represent a server, application function, or another relevant component included in the payload. By combining multiple tags within a filter, teams can also apply maintenance only when a specific combination of information is present.

This makes the maintenance decision dependent on the actual incoming request data and the filters configured by the team.

Benefits of Tag-Based Maintenance Mode

Tag-Based Maintenance Mode provides more targeted control over planned maintenance. Teams can place an entire service under maintenance when required or use Maintenance Tags to apply partial maintenance to specific matching requests.

This approach helps reduce unnecessary suppression of unrelated events, maintains visibility into operational issues outside the maintenance scope, and retains maintenance-related requests in Maintenance Logs for future use.

For DevOps, SRE, and IT operations teams managing services with multiple components, this provides a more flexible way to handle planned maintenance without applying the same maintenance state to every incoming event.

Final Thoughts

Planned maintenance should reduce unnecessary operational activity without hiding events that are unrelated to the work being performed. When only one server, application function, or component is under maintenance, placing an entire service under maintenance may be broader than required.

Callgoose SQIBS Maintenance Tags allow teams to apply maintenance based on matching data within API request payloads or email bodies. By using OR-conditioned filters with AND conditions within each filter, teams can define which requests are considered under maintenance while allowing non-matching requests to continue through normal processing. Matching requests are not processed during maintenance and are retained in Maintenance Logs for future use.

With full and partial service maintenance options and Maintenance Logs, Callgoose SQIBS helps teams manage planned maintenance with greater control while maintaining visibility into relevant operational events.

🔗 Get Started with Callgoose SQIBS: Try Now

If you’re managing critical IT systems or have customer-facing platforms, Callgoose SQIBS is a game-changer!

💡 It’s designed to quickly fix issues, reduce downtime, and boost your support team’s productivity.

Callgoose SQIBS is a cutting-edge automation platform designed to elevate your organization’s resilience, reliability, and operational efficiency. With powerful On-Call scheduling, real-time Incident Management, SLA Tracker and Incident Response capabilities, it ensures your systems are always on and responsive. Whether you need Process Automation, Runbook Automation, Incident Auto-remediation, IT request automation, or Event-Driven Automation and Self-service portal, Callgoose SQIBS empowers you with comprehensive solutions. Stay connected and in control with notifications via Mobile App (Android, iPhone), Email, SMS, Phone Calls in over 30+ languages across 200+ countries, and seamless integrations with Slack & Microsoft Teams. Empower your team to Trigger, Acknowledge, Resolve Incidents and Run Automation Workflow directly from Slack & Microsoft Teams.

Check out these videos to see how it works:

• Watch our quick 30-second video : Watch Here

• What is Callgoose SQIBS? : Watch Here

• Process Automation : Watch Here

• Runbook Automation : Watch Here

• Self-Service Portal : Watch Here

• SLA Tracker : Watch Here

Additionally, here is a helpful blog post on

• why businesses choose Callgoose SQIBS: Why Business Need to Choose Callgoose SQIBS

• Transforming Business Operations with Callgoose SQIBS — Incident Management & Automation Platform

• How Callgoose SQIBS Automation Platform Enhances Efficiency

• Use Cases Industry Sector-wise

• Solutions — By Functionality

Ready to Transform Your Incident Response?

See Callgoose SQIBS in action by exploring our website visit www.callgoose.com, or book a demo to discover how Callgoose SQIBS can optimize your workflows and boost your team’s productivity.

Let’s Talk! Reach out to us today to learn more or get personalized support.

Take the next step toward seamless automation and efficiency. We’re here to assist you every step of the way.

Take Control of Incidents — Anytime, Anywhere!

Looking forward to connecting with you!