What's New in 3.0
note
Before proceeding with an update, review the Before you upgrade guide for this release.
| New feature, enhancement, or change | Description |
|---|---|
| Overall Performance Improvements | Many improvements within the backend for faster processing of events |
| Event Title Copying | Users can copy event titles easily with a copy to the clipboard button. |
| Event Summary Data Tab | Data tab results are now in order of search results. |
| Event Summary Notable Fields | Notable fields order is kept if coming from only one configuration source |
| Event Summary Links to Configuration | Events have a link now to configuration pages for Notification Schemes and Templates |
| Event Summary Refresh-Timer location | The Refresh-Timer for the Event Summary is moved to the button bar. |
| Event Summary Filter Improvement | Apply a filter by hitting Ctrl-Enter. |
| Status Refactoring | Statuses are now defined per tenant. |
| Status Workflows | An admin can now enforce status transitions |
| Event Summary Deeplink | A deep link to an event is available in the Action Menu. |
| Template Improvements | When a user sets Time-to-live (TTL) for the event, he can set the target status. |
| Rule Improvements | Rules can now update additional attributes |
| Rule Condition Improvements | Rules allow more complex conditions such as wildcards, lists, and CIDR. |
| Rule Notifications | Matching rules can trigger notifications. |
| Notification Flows | Introducing the concept of Notification Flows, which trigger notifications based on conditions. A flow can have multiple targets, such as Mail, Teams, and Slack. |
| Notification Template Editor | A Notification Template Editor allows full control of the format of the notifications. |
| Event Resolutions | Resolved and Closed Events can now have a custom resolution assigned. |
| Health Check Improvment | Tenant Health Check improved |
| Object Consistency Improvement | Objects with existing references can not be deleted anymore |
| SHC Improvements | The migrations.conf and apps.conf files do not have to be redeployed by the admin after running through the setup |