Get started
The requested article is not available. Either it doesn't apply to this version of the product or the relevant information is organized differently in this version of the docs. You can search, browse, or go back to the other version.
A newer release of this product is available.
Object ingest transactions
Contributors
Suggest changes
-
PDF of this doc site
-
Install and maintain appliance hardware
-
SG100 and SG1000 services appliances
-
-
Install and upgrade software
-
Perform system administration
-
Monitor and maintain StorageGRID
-
Recover and maintain
-
Grid node recovery procedures
-
-
-
Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
You can identify client ingest transactions in the audit log by locating API-specific (S3 or Swift) audit messages.
Not all audit messages generated during an ingest transaction are listed in the following tables. Only the messages required to trace the ingest transaction are included.
S3 ingest audit messages
| Code | Name | Description | Trace | See |
|---|---|---|---|---|
SPUT |
S3 PUT transaction |
An S3 PUT ingest transaction has completed successfully. |
CBID, S3BK, S3KY |
|
ORLM |
Object Rules Met |
The ILM policy has been satisfied for this object. |
CBID |
Swift ingest audit messages
| Code | Name | Description | Trace | See |
|---|---|---|---|---|
WPUT |
Swift PUT transaction |
A Swift PUT ingest transaction has successfully completed. |
CBID, WCON, WOBJ |
|
ORLM |
Object Rules Met |
The ILM policy has been satisfied for this object. |
CBID |
