1.0.85
July 29, 2025
Version 1.0.85Faster Recovery with Resource Contention Remediation
You can now remediate resource contention issues directly from the Causely UI. This helps you resolve incidents faster and restore service performance without breaking your flow.
Supported Root Causes:
- CPU Congested: Automatically adjust CPU limits when services are experiencing CPU saturation.
- Frequent Memory Failure: Resolve persistent out-of-memory issues caused by memory leaks or inefficient usage.
- Memory Failure: Increase memory allocations to resolve out-of-memory issues.
- Ephemeral Storage Noisy Neighbor: Isolate and manage containers that excessively consume ephemeral storage, impacting node stability.
- Memory Noisy Neighbor: Isolate and manage containers that excessively consume memory, impacting node stability.
- Congested Services: Scale service resources to handle increased load.
The remediation interface provides step-by-step guidance and Kubernetes configuration examples, making it easy to implement fixes with confidence.
Smarter Urgency Detection for Root Causes
We've improved how Causely flags urgent issues. Root causes that lead to SLO violations, or put your SLOs at risk, are now automatically marked as Urgent and sent to your alerting channels (for example, Slack) by default. Stay focused on what matters most.
This enhancement ensures that critical issues requiring immediate attention are automatically prioritized and routed to the right teams, reducing response times and improving incident management workflows.
Customizable SLO Settings
You can now fine-tune SLO targets and burn rate thresholds within Causely to align with your team's reliability goals. This helps improve the precision of urgency detection and alerting.
Key Features:
- Configure custom SLO targets for different services
- Set burn rate thresholds to control alert sensitivity
- Align reliability goals with business requirements
- Improve alert precision and reduce false positives
This feature is currently in preview. Check out our SLO Configuration documentation for detailed setup instructions.
Did you know?
Causely supports multiple sources for tracing out of the box. While our agents come with eBPF-based automatic instrumentation out of the box, you can also use Odigos, groundcover, Grafana Beyla, or existing OpenTelemetry data.
Additional service dependencies can be identified from Datadog or Dynatrace data, giving you flexibility to work with your existing observability stack.
Bug Fixes and Minor Improvements
- Load Balancer Support: Added support for Google Cloud internal load balancers, enabling better visibility into private service endpoints.
- Controller Discovery: Improved discovery of custom controllers such as GitLab Runner to enhance coverage of user-defined Kubernetes workloads.