New in this Version:

• allquiet_integration

  • HTTP Monitors - Optional Attribute ignore_non_http_errors (Boolean):
    When true, connection and transport failures (non-HTTP errors) are ignored and do not trigger incidents

• allquiet_integration

  • Optional Attribute labels (List of String):
    Labels applied to the integration for filtering and organization

We added labels to the integration level. You can now manage labels for each integration, similar to how you use team labels.

Why this update matters

Effective incident management requires fast context. Integration-level labels attach metadata to incidents at the source. This helps your team understand the category of an incident before triage begins.

What is new

• Integration labels: Create and manage labels within each integration.

• Consistent experience: Use the label system you already know from teams.

• Layered metadata: Keep team-level labels for shared defaults. Use integration-level labels for source-specific data.

The benefits

• Faster classification: Classify incoming incidents automatically.

• Better consistency: All incidents from the same integration carry identical metadata.

Integration-level labels give you control where incidents begin.

All Quiet now integrates with Mattermost 🎉

Benefit from the flexible two-way integration

Send All Quiet incidents to your very own Mattermost servers
Benefit from secure collaboration on your sovereign infrastructure. Deploy anywhere, control everything. Trusted by governments, enterprises and militaries around the world.

Create new incidents directly from Mattermost
Use custom slash commands to trigger All Quiet incidents and escalations from your Mattermost channels. Team members can then assign, affect services, comment, and resolve incidents without leaving Mattermost.

Here’s how to ➡ set up everything in minutes.

New in this Version:

• allquiet_integration

  • HTTP Monitors - Optional Attribute override_accepted_status_codes (List of Number). If empty, 2xx status codes are accepted. If specified, only the specified HTTP status codes are considered 'up' (e.g. 200, 201, 204, 302). Each value must be between 100 and 599.

• allquiet_team_escalations

  • Optional Attribute auto_assign_to_teams_repeat_alerts (Boolean) - Default: true

    • If true, notify all on-call users when auto-assigning to teams (including those previously notified).

    • If false, only newly assigned teams are notified.

• allquiet_routing

  • Optional Attribute assign_to_teams_repeat_alerts (Boolean) - Default: true

    • If true, notify all assigned users and teams, including those previously notified.

    • If false, only newly assigned users / teams are notified.

• allquiet_services

  • Optional Attribute integrations (Attributes List): Link integrations to this service. Each entry links an integration to the service with optional severity filter. Incident from this integration will, if severity matches, auto affect this service

We’ve added new report views at Inbound Integration, Team and Organization level, giving you clearer insight into alert volume, response performance, and trends across your whole setup.

These reports make it easier to compare teams, track improvements over time, and identify where to focus your reliability efforts.

Learn more about the new reports in our documentation.

Pro and Enterprise customers can now create incidents directly through the Public All Quiet API.

This makes it easier to integrate incident creation into your existing workflows, automation pipelines, and third-party tools — no manual steps required.

Whether you’re triggering incidents from:

• Monitoring systems

• CI/CD pipelines

• Custom internal tooling

• Or external alerting platforms

You can now open and manage incidents programmatically in real time.

⚙️ What’s Included

• Create new incidents via REST API

• Define title, description, severity, and affected services

• Trigger incidents automatically based on your own logic

• Seamless integration into existing automation workflows

📘 Documentation

Full API details are available in our Swagger documentation:
EU: https://allquiet.eu/api/public/swagger-ui/index.html
US: https://allquiet.app/api/public/swagger-ui/index.html

Rate limits and usage guidelines can be found here:
https://docs.allquiet.app/essentials/inbound#api-and-webhook-rate-limits

We’ve enhanced our HTTP Monitor to give you more control over what counts as “up.”

What’s new?

You can now define the exact HTTP status codes that should be considered successful for your uptime checks.

✅ How it works

• If left empty: All 2xx status codes are treated as success (default behavior, unchanged).

• If specified: Only the status codes you list will be accepted as “up.”

💡 Why this matters

Not all healthy endpoints return a 2xx response. Some services intentionally use redirects (3xx) or other specific codes to indicate correct behavior. With this update, you can align monitoring with your application’s real-world logic.

This gives you:

• More accurate uptime reporting

• Fewer false alerts

• Greater flexibility for modern architectures

Learn more in our HTTP Monitor Setup Guide.

Let us know what you think!

Want to view your team’s on-call schedule in your personal Google, Apple, or Outlook calendar? Or share a live view with management for better visibility?

You can now subscribe to your team’s All Quiet on-call calendar from anywhere using a unique .ics subscription link. 🎉

Just like personal on-call calendar subscriptions, your team calendar can now be:

• Synced to your private calendar

• Shared with stakeholders

• Embedded into existing scheduling workflows

• Accessed across any calendar app that supports ICS
  

Once subscribed, updates happen automatically — so everyone always sees the latest schedule.

🔐 Who can use this?

This feature is available to:

• Team Administrators

• Organization Administrators

• Organization Owners
  
  

⚙️ How it works

Simply generate a unique .ics link for your team calendar and subscribe to it in your preferred calendar application.

That’s it — instant, always up-to-date team visibility wherever you need it.
Learn where to find the new feature in our documentation.