* Document security events route migration to Alerts in `UPGRADING.md`. * Improve `UPGRADING.md`. * Revert not needed change
3.2 KiB
Upgrading to Graylog 7.1.x
User Session Termination
All user sessions will be terminated when upgrading because the internal storage format for sessions has been changed. Users will have to log in again.
Breaking Changes
Plugins: Removal of Perspective Plugin API
This release includes frontend plugin API changes related to perspectives.
- The
perspectivesplugin export has been removed from core. - Plugin-provided
navigationandpageNavigationentities no longer support theperspectivekey.
Security Events UI Routes Consolidated into Alerts
The dedicated Security Events UI routes under /security/security-events/* have been removed in favor of the
existing Alerts routes.
If you have bookmarks, links, or runbooks pointing to old routes, update them as follows:
| Old route | New route |
|---|---|
/security/security-events/alerts |
/alerts |
/security/security-events/definitions |
/alerts/definitions |
/security/security-events/notifications |
/alerts/notifications |
/security/security-events/event-procedures/procedures |
/alerts/event-procedures/procedures |
/security/security-events/event-procedures/steps |
/alerts/event-procedures/steps |
/security/security-events/event-procedure-action |
/alerts/event-procedure-action |
External Authentication Services: Changed Default User Time Zone
The authentication backends for Active Directory, LDAP, OIDC, Okta, and SAML previously set the time zone for
newly synchronized users to the value of the root_timezone config file setting. ("UTC" by default)
Graylog 7.1 introduces a configurable "default user time zone" setting for all authentication backends. The default value is unset, meaning that the browser's time zone will be used by default.
Formatting Change of aggregation_conditions Field in Aggregation Events
The aggregation_conditions map previously used keys with parentheses on the aggregation type. These needed to be
escaped if they were used directly in Notification templates, e.g. ${aggregation_conditions.count\\(\\)},
${aggregation_conditions.sum\\(fieldname\\)}. To avoid the need for escaping, their format has been modified to use
underscores instead, e.g. ${aggregation_conditions.count}, ${aggregation_conditions.sum_fieldname}. Any
existing notifications using the escaping of parentheses in explicit aggregation_conditions key names will need to
be modified to instead use the underscore format.
Configuration File Changes
| Option | Action | Description |
|---|---|---|
tbd |
added |
Java API Changes
- tbd
REST API Endpoint Changes
The following REST API changes have been made.
| Endpoint | Description |
|---|---|
GET /<endpoint> |
Description of the endpoint change |