Replication policy configuration (destination)

Edit online

This log is generated for every internal replication allowed check request that is processed on the destination Accesser device. This request is made internally as part of the PutBucketReplication request (user-initiated).

Request type

REST.GET.CONTAINER_REPLICATION_ALLOWED

Table 1. Replication policy configuration (destination) log entry fields
Field name	Type	Required	Description
`replication`	Object	yes	Contains replication-related information. Always present on `REST.GET.CONTAINER_REPLICATION_ALLOWED` requests.
`replication.originating_request_id`	String	yes	ID of the `PutBucketReplication` request that performed this internal check request. Can be correlated with the `request_id` field in the `REST.PUT.CONTAINER_REPLICATION` log located in the source `access.log` .
`replication.originating_bucket_id`	String	yes	Source bucket that wants to check this destination. Corresponds to the bucket where `PutBucketReplication` was originally targeted, which in turn triggered this internal check request.

Sample log

{
  ... (some common fields omitted)
 
  "request_method": "GET",
  "request_uri": "/destination-bucket?ibm-replication-allowed",
  "status": 204,
  "request_id": "7b805407-9f7b-4ea6-9baf-6de92ef3f00f",
  "request_type": "REST.GET.CONTAINER_REPLICATION_ALLOWED",
  "container_name": "destination-bucket",
  "replication": {
    "originating_request_id": "36ae1b80-43c9-47c9-9166-6d79699375cc",
    "originating_bucket_id": "source-bucket"
  },
 
  ...
}