From 87ad19f0d145a4491c4d145871170703bd0e9fdd Mon Sep 17 00:00:00 2001 From: Monika-Lydia Dreiucker Date: Tue, 9 Dec 2025 15:43:35 +0100 Subject: [PATCH] Add version update event --- at-events.md | 1 + 1 file changed, 1 insertion(+) diff --git a/at-events.md b/at-events.md index 72151b2..789203f 100644 --- a/at-events.md +++ b/at-events.md @@ -120,6 +120,7 @@ The following table lists the activity tracking event actions that {{site.data.k |`.deployment.update`|`.serviceendpoints.update` | A change was made to the service endpoints configuration. If the operation failed, a "-failure" flag is included in the message. | |`.deployment-group-autoscaling.update` | `.autoscaling.update` | An autoscaling configuration change or an autoscaling operation was performed. If an autoscaling operation was performed the message includes `autoscale resources for instance `. If the autoscaling operation or the configuration change failed, a "-failure" flag is included in the message. | |`.deployment-volumes.update`|`.volumes.update` | An activity was performed on the encryption key that is used by the database, such as rotation or shredding. Details of the action are in the event. | +|`.deployment-version.update`|`.version.update` | A version update operation was performed on your instance. If the update failed, a "-failure" flag is included in the message. | {: caption="List of events and event descriptions by {{site.data.keyword.databases-for}}" caption-side="bottom"} The `service_name` field indicates the type of {{site.data.keyword.databases-for}} instance. For example, `databases-for-postgresql` or `messages-for-rabbitmq`.