Skip to content

Latest commit

 

History

History
69 lines (50 loc) · 2.49 KB

catalog-audit-logs.md

File metadata and controls

69 lines (50 loc) · 2.49 KB
Raw
copyright lastupdated keywords subcollection
years
2020, 2021
2021-05-12
audit log
account

{:shortdesc: .shortdesc} {:codeblock: .codeblock} {:screen: .screen} {:tip: .tip} {:note: .note} {:important: .important} {:external: target="_blank" .external} {:ui: .ph data-hd-interface='ui'} {:cli: .ph data-hd-interface='cli'} {:api: .ph data-hd-interface='api'} {:java: .ph data-hd-programlang='java'} {:python: .ph data-hd-programlang='python'} {:javascript: .ph data-hd-programlang='javascript'} {:curl: .ph data-hd-programlang='curl'} {:go: .ph data-hd-programlang='go'}

Viewing changes to your private catalogs

{: #catalog-audit-logs}

With audit logs you can follow the changes that have been made to your private catalogs. Changes to your private catalog are associated with your account or enterprise account, products, and catalog. {: shortdesc}

To view the audit logs, you need to be a manager of the account the catalog is in or have write access to the catalog. For write access, you need at least editor access on the catalog and the account. See Assigning access to account management services for more information.

Viewing changes in the console

{: #audit-logs-table} {: ui}

  1. In the {{site.data.keyword.Bluemix_notm}} console, go to Manage > Catalogs from the console menu bar.
  2. Select Audit logs.
  3. Filter for the scope you want to see in the table.

Each event in the audit logs table by default identifies each change with the email of the user that made the change, the type of change, a description of the change, and the date that the change was made.

Viewing changes by using the CLI

{: #audit-logs-table-cli} {: cli}

This action can be done only through the console, API, or SDKs. To see the steps, switch to the UI or API instructions.

Viewing changes by using the API

{: #audit-logs-table-api} {: api}

You can view changes made to your private catalogs by calling the Catalog Management API as shown in the following sample request.

curl -X "GET" \ 
"https://cm.globalcatalog.cloud.ibm.com/api/v1-beta/catalogs/{catalog-id}/audit" 
-H "accept: application/json" 
-H "Authorization: {iam-bearer-token}"

{: codeblock}

Each event in the audit logs table by default identifies each change with the email of the user that made the change, the type of change, a description of the change, and the date that the change was made.