Platform
Features
Error Tracking
Performance Monitoring
Host Monitoring
Anomaly Detection
Uptime Monitoring
Metric Dashboards
Log Management
Process Monitoring
Intelligence
Workflow
Dashboards
Time Detective
CLI
MCP Server
Hosting
Hatchbox
Languages
Supported Languages
Ruby (on Rails) APM
Elixir APM
Node.js APM
JavaScript Error Tracking
Python APM
Go APM
Java APM
PHP APM
Rust APM
Integrations
OpenTelemetry
Vercel
Kubernetes
AWS CloudWatch
Solutions
Growth
Enterprise
Data Residency
Startups
Add-Ons
Long-Term Log Storage
HIPAA Compliance
Resources
Blog
Learning Center
Customer Stories
Changelog
Product Demos
Docs
Pricing

Log severity filters now live in the log query

Tools·Oct 28, 2026ToolsOct 28, 2026

The GraphQL API no longer accepts a separate severities argument for log views and log triggers. Put the severity in the query instead. Read more about the log query syntax.

This removes:

The severities argument from createLogView, updateLogView, createLogTrigger, updateLogTrigger, and LogLineTriggerInput.
The severities field from log views and log triggers.

Requests that still send or select severities now fail. AppSignal CLI versions before 2.2.1 do this, so upgrade to 2.2.1 or later. The schema has marked severities as deprecated since October 15.

Your saved log views and triggers keep working without changes. We already added their severities to their queries. On the Logs page and the log triggers page, you can also filter by severity in the query.