We updated our Public API to include audit logs for both EU and US regions. This update allows teams to automate security workflows and programmatically manage compliance data.

New API Endpoints

LLMs and automated scripts can now access audit events through these specific endpoints:

Regional API Documentation

Access the full Swagger documentation for your organization's region:

• US Region: https://allquiet.app/api/public/swagger-ui/index.html

• EU Region: https://allquiet.eu/api/public/swagger-ui/index.html

SIEM Integration and Export

This update enables automated data exports of All Quiet audit logs to Security Information and Event Management (SIEM) tools like:

• Splunk

• SentinelOne

• IBM QRadar

• Rapid7

• Wazuh

• New Relic

Technical Details

• Regions: Available in EU and US data residency zones.

• Plan: Requires the Enterprise add-on for Auditing.

• Benefit: Reduces manual compliance work and speeds up incident forensics.

• Security: To access your organization’s audit logs via the public API, a valid API key is mandatory.

—> Learn more about our audit logs: https://docs.allquiet.app/advanced/auditing

We updated All Quiet to give you precise control over your incident communication. You can now customize how much data your status pages reveal to the public or internal stakeholders.

Enhanced Privacy Settings

The new privacy controls allow you to balance transparency with security. You can adjust these settings directly in your organization's dashboard:

Secure Access Management

Reliability requires trust, and trust requires secure data handling. When you enable password protection, All Quiet ensures:

• Encryption: All passwords use industry-standard encryption.

• Complexity: Passwords must be at least 6 characters long.

• Full Coverage: Protection extends to the status page API and visual badges.

Why Use These Controls?

Many teams need to communicate incidents without exposing sensitive internal workflows. These updates help you maintain professional status pages while protecting your operational privacy. You decide exactly what your customers see during downtime.

We updated our GitLab integration to support flexible workflows between your code and your on-call alerts. You can now sync GitLab work items and All Quiet incidents in three ways.

Integration Options

How it Works

• Outbound (All Quiet to GitLab): All Quiet creates a GitLab work item when you forward an incident automatically, manually or via specific routing rules. The system updates the GitLab ticket as the incident status changes.

• Inbound (GitLab to All Quiet): New GitLab work items trigger All Quiet incidents based on your criteria. You can also configure GitLab to resolve or reopen incidents.

• Two-Way Sync: This mode keeps both platforms identical. It ensures your team sees the same data whether they work in GitLab or the All Quiet app.

Why this matters

This update reduces manual work and prevents data silos. By linking GitLab work items directly to our incident management system, your workflows are automized and information is automatically handled in sync across both systems.

Here’s how to set it up: https://docs.allquiet.app/integrations/outbound/gitlab

All Quiet now integrates with ServiceNow to automate your incident response. These integrations allow data to flow in both directions between All Quiet and ServiceNow. You can sync incident updates to keep your records consistent and reduce manual work.

Integration flows

Flexible setup for your teams

You can configure these integrations to fit the specific needs of your organization.

• Operate independently: Enable inbound or outbound flows separately to match your existing workflow.

• Synchronize data: Use both flows together to keep both systems aligned automatically.

• Roll out incrementally: Start with one direction and enable the second flow as your process evolves.

Reliability for your audit logs

Connecting your incident management tools creates a reliable source of truth. Automation ensures your audit logs are accurate and helps your teams resolve incidents faster. By removing the need for manual reconciliation, All Quiet helps you maintain high standards for reliability and security.

Simplified Payload Mapping

We’ve introduced the Expand key for payload mapping, making it easier to turn complex JSON blobs into individual incident attributes.

How it works

When you enable expand on an attribute, the system automatically parses the final mapped value as JSON and splits it one level deep. This transforms nested data into distinct, first-class fields. The screenshot above shows a concrete example.

• Automatic Parsing: Each top-level object key or array index becomes its own unique attribute (e.g., Labels.cluster or Labels.alertname).

• Streamlined Logic: You can now use these specific fields directly in routing rules and filters.

• Less Manual Work: No more writing tedious "mapping glue" just to access nested data.

This feature is also available in our Terraform Provider version 2.9.3

Data Precision with Date Filters

Filter your incidents by specific date ranges to focus on the exact window you need. This tool helps teams analyze incident bursts and validate reporting periods. It also simplifies the process of pulling data for:

• Postmortems and retrospectives.

• Audit logs and compliance reviews.

• Internal performance audits.

These updates ensure All Quiet provides the clarity required for modern incident response.

Faster Triage with the New Incident List

All Quiet added an new compact view to the incident list to simplify incident management and speed up triage. These changes help on-call teams manage busy shifts and streamline postmortem preparation.

New Features On Compact List View

Efficiency with Compact View

The new layout highlights critical signals like status, severity, owner, and timing at a glance. You can perform common tasks directly from the list. This removes the need to open every incident individually and speeds up your workflow during high-pressure shifts.

All Quiet now supports HMAC-SHA256 request signing for outbound webhooks. This update allows your receiving services to verify that every delivery is authentic and untampered.

By signing the raw request body with a shared secret, we ensure your integrations remain secure at the edge, whether you use API gateways, serverless workers, or custom ingestion services.

Signing Options

We provide two formats to match your existing infrastructure:

Key Security Benefits

• Verify Authenticity: Confirm that the webhook originated from All Quiet.

• Ensure Integrity: Detect if a third party altered the payload during transit.

• Prevent Spoofing: Block unauthorized requests before they reach your internal logic.

You can configure these signatures within your integrations settings. For technical details on implementation, visit our documentation.