Updates: Assertion Limits by Plan and Incident Response History

We’re excited to announce the latest updates to Crystade, focused on improving plan clarity, auditability, and collaboration controls. These changes affect how you use monitoring assertions and manage incident responses. Here’s what’s new.

Plan-Based Limits for Monitoring Assertions

Assertions are custom evaluation rules linked to a monitor. They let you define precise health criteria beyond simple reachability, such as checking specific JSON fields or validating TLS certificate details.

To ensure fair resource usage and provide clear expectations as your monitoring needs grow, we now enforce maximum assertion limits per team plan:

These limits apply across all monitors in a team. If you reach your limit, you’ll need to remove unused assertions or upgrade your plan. This change helps maintain consistent performance for all users.

Incident Response Versioning for Auditability

Incident responses are chronological entries in an incident’s timeline, each carrying a status (like investigating, identified, or resolved) and a message.

Previously, editing a response overwrote the original content, losing historical context. Now, every edit creates a new version. Old versions remain accessible as read-only records, allowing your team to audit what was communicated and when.

This improvement makes post-incident reviews easier, supports compliance requirements, and increases accountability. You can trace exactly how an incident status evolved over time.

Tighter Controls: Only Original Author Can Edit Responses

In another access control update, incident responses can now only be edited or updated by the user who originally created them. Previously, any team member could modify any response.

This reduces accidental modifications and ensures that the person responsible for a response maintains ownership. It also aligns with best practices for collaboration and accountability. Other access rules, such as deletion restrictions on the first response, remain unchanged.

What This Means for You

• Check your current assertion usage against the new plan limits and upgrade if you need more capacity.

• Review incident timelines to see the new version history in action.

• Coordinate with your team when edits to responses are needed, since only the original author can make changes.

These updates are part of our ongoing commitment to provide robust incident management and monitoring tools. We encourage you to explore the new features in your Crystade dashboard. As always, we welcome your feedback.