Hello! We have been hard at work bringing you a massive wave of updates to SolarWinds Incident Response to make your incident management faster, smarter, and more integrated.
Here is a breakdown of all the newly released features and optimizations:
Mobile & Notification Upgrades
- Priority-Based Personal Notification Rules: You can now configure entirely different notification rules based on incident priority. For example, a P1 can trigger an immediate phone call and SMS, while a P3 simply sends an email. If an incident is upgraded (e.g., P3 to P1), pending notifications are cancelled and rebuilt using the new priority rules so you are always notified with the appropriate urgency.
- Secondary Phone Numbers: Users can now add a secondary phone number and configure their escalation policies, personal or priority-based notification rules to dictate which alerts go to their primary versus secondary number.
- Landline Phone Support: Users can now easily add a landline phone number to receive voice calls. SMS notifications will automatically be skipped for any user utilizing a landline. Verification of such numbers can be done simply by reaching out to the support team.
- Android Volume Override Revamp: To combat constraints introduced by Samsung's One UI 8, the volume override feature for Android has been entirely revamped. Push notifications will now play via the Alarm channel so the sound triggers even if the device is set to Silent, Vibrate, or Do Not Disturb. Furthermore, volume override support has been extended to OnePlus devices.
ChatOps: MS Teams & Slack Enhancements
- Direct MS Teams & Slack Actions: You can now instantly "Suppress" incidents or update an incident's priority directly from the MS Teams and Slack alert messages without needing to open the Incident Response platform separately.
- MS Teams Mobile App Rendering Fix: We fixed a formatting bug that was breaking the main incident message on the MS Teams mobile app; the entire message—including the resolution reason—now renders perfectly.
- Slack Bot Rebranding: The Squadcast Slack bot rebranding changes are now officially live in both the US and EU regions.
API & Integration Updates
- Bi-directional OSH API Tokens: We have shipped Organization-Scoped API Tokens (OSH tokens) to enable clean, least-privilege, bi-directional integration between SolarWinds Observability (OSH) and Incident Response. These tokens represent the organization as a whole rather than a specific user, and feature configurable expirations (30d, 90d, 1yr, or never) with a secure one-time reveal upon creation.
- Resolve Signals Optimization: API rate limits for resolve signals now match our limits for trigger signals. Additionally, batch resolutions are now capped at a maximum of 100 recent incidents per request, and we have implemented plan-based time-range filters (e.g., Free Plan incidents can be resolved up to 3 months old).
Other Updates
- Live Call Routing: Customers can now choose between two routing modes per routing number: "Simultaneous" (default, which rings all on-call engineers at once) or "Sequential" (rings engineers one-by-one in escalation order, rolling to the next if unanswered within 25 seconds). Both modes utilize a "Press 1 to accept" requirement, eliminating the issue of calls accidentally landing in a personal voicemail.
- Email Integration Updates: The email alert source ingestion handler has been upgraded to accept up to 5 recipients, creating an individual incident for each recipient. If an alert has more than 5 recipients, it caps at 5 incidents and logs the remaining recipients in the response metadata.
- Saved Filters for Analytics: You no longer need to manually re-select services, priorities, and time ranges every time you view Analytics. You can now save your filter combinations as named views, scope their visibility just for yourself or your whole team, and share them via unique URLs.
- Silent Onboarding: New customers setting up or onboarding onto the product can request for a quiet onboarding experience - to easily silence all notifications, which can be toggled back off to resume normal alerts once ready. This is especially helpful in situations where migrations are concerned, not all users need to be notified for every single change in the product until go-live, etc.
Drop your thoughts or questions below—we'd love to hear how these updates are improving your incident response workflows!
