You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: at-events-am.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,9 @@
1
1
---
2
2
3
3
copyright:
4
-
years: 2018, 2024
5
-
lastupdated: "2024-10-30"
4
+
5
+
years: 2018, 2025
6
+
lastupdated: "2025-01-28"
6
7
7
8
keywords:
8
9
@@ -604,4 +605,3 @@ The following table lists *requestData* fields that you can find in events that
604
605
| `team_directory_enabled` | Boolean | Defines the status of the *User list visibility restriction* IAM account setting. \n When it is set to `true`, users in your account can view other users from the Users page. |
605
606
| `mfa` | String | Defines the MFA method that is required for users to log in to the account. \n Valid values are *TOTP*, and *TOTP4ALL* \n This field is set to `TOTP` when the account requires MFA for non-federated users only. Users are required an ID, password, and a time-based one-time passcode to log in. \n This field is set to `TOTP4ALL` when the account requires MFA for all users. \n All users by requiring an ID, password, and a time-based one-time passcode. \n When this field is empty, MFA is not enabled in the account, and all users log in by using a standard ID and password. |
606
607
{: caption="Account IAM settings requestData fields" caption-side="top"}
@@ -156,7 +157,6 @@ The following table lists the actions that generate nerwork zone events:
156
157
| context-based-restrictions.zone.delete | An event is generated when an initiator deletes a CBR zone. |
157
158
{: caption="Events that are generated for network zone events" caption-side="top"}
158
159
159
-
160
160
## Context-based restrictions rules events
161
161
{: #restriction_rules_events}
162
162
@@ -171,7 +171,6 @@ The following table lists the actions that generate context-based restricitons r
171
171
| context-based-restrictions.policy.delete | An event is generated when an initiator deletes a CBR rule. |
172
172
{: caption="Events that are generated for context-based restrictions rules" caption-side="top"}
173
173
174
-
175
174
## Account settings events
176
175
{: #account_setting_events}
177
176
@@ -182,7 +181,6 @@ The following table lists the actions that generate account settings events:
182
181
| context-based-restrictions.account-settings.read | An event is generated when an initiator looks at information that is related with account settings. |
183
182
{: caption="Events that are generated for context-based restrictions account settings events" caption-side="top"}
Copy file name to clipboardexpand all lines: at-events-cm.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,9 @@
1
1
---
2
2
3
3
copyright:
4
-
years: 2018, 2024
5
-
lastupdated: "2024-10-30"
4
+
5
+
years: 2018, 2025
6
+
lastupdated: "2025-01-28"
6
7
7
8
keywords:
8
9
@@ -210,4 +211,3 @@ The following table lists the actions that generate an event for software instan
210
211
211
212
You can find the value `unavailable` in catalog events. This value indicates when an update is made, but specific details about the update aren't included.
Copy file name to clipboardexpand all lines: at-events-iam.md
+3-12
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,9 @@
1
1
---
2
2
3
3
copyright:
4
-
years: 2024
5
-
lastupdated: "2024-11-07"
4
+
5
+
years: 2024, 2025
6
+
lastupdated: "2025-01-28"
6
7
7
8
keywords: activity tracking, IAM events, Identity and Access Management, observibility
8
9
@@ -33,7 +34,6 @@ You can use {{site.data.keyword.logs_full_notm}} to visualize and alert on event
33
34
As of 28 March 2024, the {{site.data.keyword.at_full_notm}} service is deprecated and will no longer be supported as of 30 March 2025. Customers will need to migrate to {{site.data.keyword.logs_full_notm}} before 30 March 2025. During the migration period, customers can use {{site.data.keyword.at_full_notm}} along with {{site.data.keyword.logs_full_notm}}. Activity tracking events are the same for both services. For information about migrating from {{site.data.keyword.at_full_notm}} to {{site.data.keyword.logs_full_notm}} and running the services in parallel, see [migration planning](/docs/cloud-logs?topic=cloud-logs-migration-intro).
34
35
{: important}
35
36
36
-
37
37
## Locations where activity tracking events are sent to {{site.data.keyword.at_full_notm}} hosted event search
38
38
{: #at-legacy-locations-iam}
39
39
@@ -156,8 +156,6 @@ The following table lists the actions that generate an event:
156
156
|`iam-groups.account-settings.update`| An event is generated when an initiator updates their account settings for the access groups service. |
157
157
{: caption="Events that are generated for access groups" caption-side="top"}
158
158
159
-
160
-
161
159
### Access groups events
162
160
{: #at_events_iam_access_groups}
163
161
@@ -224,8 +222,6 @@ The following table lists the actions that generate an event:
224
222
|`iam-am.policy.delete`| An event is generated when an initiator deletes a policy that is assigned to a user or access group. |
225
223
{: caption="Events that are generated for policy actions" caption-side="top"}
226
224
227
-
228
-
229
225
## Service ID events
230
226
{: #at_events_iam_serviceids}
231
227
@@ -238,7 +234,6 @@ The following table lists the actions that generate an event:
238
234
|`iam-identity.account-serviceid.delete`| An event is generated when an initiator deletes a service ID. |
239
235
{: caption="Events that are generated for service IDs actions" caption-side="top"}
240
236
241
-
242
237
## API key events
243
238
{: #at_events_iam_apikeys}
244
239
@@ -360,11 +355,9 @@ The following fields include extra information:
360
355
* The `initiator.name` includes information about the user that logs in to the account.
361
356
* The `X-Global-Transaction-Id` includes an ID that you can use when you open a support ticket if you need to get more information.
362
357
363
-
364
358
#### Log in from the {{site.data.keyword.cloud_notm}} UI
365
359
{: #at_events_iam_analyze_login_events-1}
366
360
367
-
368
361
When a user logs in from the {{site.data.keyword.cloud_notm}} UI, you get an event in the account with action `iam-identity.user-refreshtoken.login`.
369
362
370
363
The following field includes extra information:
@@ -388,7 +381,6 @@ When a user [logs in with a federated ID by using trusted profiles](/docs/accoun
388
381
#### Failed log in actions
389
382
{: #at_events_iam_analyze_login_events-3}
390
383
391
-
392
384
When a user logs in to the {{site.data.keyword.cloud_notm}}, the user ID (IBMid) and credentiasls are validated first. At this point, the user has not selected an account. Notice that a user can belong to multiple accounts.
393
385
394
386
After the user ID is authenticated successfully in the {{site.data.keyword.cloud_notm}}, the user can choose an account. It is at this point in the process that an account is associated to the log in request, and an event with action `iam-identity.user-refreshtoken.login`, or `iam-identity.user-apikey.login` is generated in your account.
@@ -514,7 +506,6 @@ To find out the user who has tried to modify an API key or a service ID, complet
514
506
515
507
To get the API key on which the action has been requested and failed, see the field `prev_instance_name` in requestData.
516
508
517
-
518
509
### Resource is locked. Request to update Service ID or API key fails
Copy file name to clipboardexpand all lines: audit_log.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,9 @@
1
1
---
2
2
3
3
copyright:
4
-
years: 2018, 2023
5
-
lastupdated: "2023-12-29"
4
+
5
+
years: 2018, 2025
6
+
lastupdated: "2025-01-28"
6
7
7
8
keywords: audit log, user access, account log, system events, monitor system events, user access logs
8
9
@@ -18,7 +19,6 @@ subcollection: account
18
19
If you have a classic infrastructure account, you can monitor storage replication events by viewing audit logs. Audit logs track the interactions of each user, like login attempts, port speed updates, power restarts, and interactions made by {{site.data.keyword.BluSoftlayer_notm}} infrastructure support staff.
@@ -38,7 +38,6 @@ Multiply the two values together, and the result is the GB-hour.
38
38
39
39
{{site.data.keyword.cloud_notm}} systems monitor all inbound and outbound traffic for a server regardless of the type of traffic. Based on the allocated bandwidth for a server, overages are assessed for excess traffic, which is monitored at the network switch level. Monitor your bandwidth usage with bandwidth graphs. For more information, see [Viewing bandwidth graphs](/docs/bare-metal?topic=bare-metal-bm-view-bandwidth-graphs).
40
40
41
-
42
41
## How do I prevent bandwidth overages?
43
42
{: #bandwidth-usage-overages}
44
43
{: faq}
@@ -194,7 +193,6 @@ If you think your invoice didn't include your promotion credits, first determine
194
193
195
194
After you complete these steps, if you still believe that the invoice amount is an error, create a support case. Go to the [Support Center](/unifiedsupport/supportcenter) and click **Create a case**.
196
195
197
-
198
196
## How do I apply a feature code?
199
197
{: #entercode}
200
198
{: faq}
@@ -204,7 +202,6 @@ Feature codes add more capabilities in an account and are typically provided for
204
202
205
203
You might be looking for information about promo codes and subscription codes, which are available for certain account types. For more information, see [Managing promotions](/docs/account?topic=account-applying-promo-codes) and [Applying subscription codes](/docs/account?topic=account-subscription_code).
206
204
207
-
208
205
## Why did my account get billed for additional services charges?
209
206
{: #getting-billed}
210
207
{: faq}
@@ -221,7 +218,6 @@ If you believe that charges on your invoice are incorrect, [contact Support](/un
221
218
222
219
A [resource](#x2004267){: term} is anything that you can create from the catalog that is managed by and contained within a resource group. You're billed for resources in your account until you cancel them. If you deleted a resource or have resources in your account that are no longer used, make sure to cancel all billing items associated with those resources. Billing items can't be recovered after they are canceled. For more information, see [Cancelling your billing items](/docs/account?topic=account-cancel-billing-items).
223
220
224
-
225
221
## Can I add a tax identification number to my account?
226
222
{: #tax-assessment}
227
223
{: faq}
@@ -278,7 +274,6 @@ Credits for {{site.data.keyword.IBM_notm}} corporate programs, such as Startup w
278
274
1. Select an applicable invoice.
279
275
1. Find the name of the program listed in the Current Payment Method section to see the monthly credit, applied credit, and remaining credit information.
280
276
281
-
282
277
## How can I get help with billing and usage?
283
278
{: #contactsupport}
284
279
{: faq}
@@ -328,7 +323,6 @@ A manual credit is a credit that you receive from {{site.data.keyword.Bluemix_no
328
323
329
324
You might receive multiple invoices if you have an Enterprise Savings Plan and service commitment on different orders. If you have service commitments at multiple sites, you receive separate invoices for each.
330
325
331
-
332
326
## Why doesn't the usage report that I downloaded match what I see on the usage page?
Copy file name to clipboardexpand all lines: bp_account.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,9 @@
1
1
---
2
2
3
3
copyright:
4
+
4
5
years: 2018, 2025
5
-
lastupdated: "2025-01-17"
6
+
lastupdated: "2025-01-28"
6
7
7
8
keywords: organizing resources, organizing resource groups, account best practices, best practices account, access best practice, my resources, administrator, administrator role
0 commit comments