Monitor
OCI Logging and OCI Logging Analytics (optional) were used to monitor this solution.
OCI buckets can be configured to emit log messages when objects are read or written, or both. These messages can be stored using the OCI Logging service, which can store messages in a rolling log, which is configurable upto 6 months. In order to preserve and analyze these messages into meaningful trend data, we are able to send this and other log files via OCI Connector Hub to the OCI Logging Analytics service for further analysis. The most value here is in the ability to track object access events, such as GET or PUT. Logging Analytics easily allows for this type of grouping by client, VM name, object name, or any other indexable fields.
Additionally, OCI Object Storage metrics are automatically collected by the OCI Monitoring service, and can be used to fire alarms and send out notifications. Object Storage Events can optionally be emitted per bucket, which could be used to track and notify upon object or bucket creation, deletion, or updates.
The following diagram illustrates a potential monitoring workflow.
For more details, see the architecture diagram in the Architecture
section. Additional details can be extracted from metric data that is emitted at the
compartment level, with the oci_objectstorage namespace. For more
information, see the Object Storage Metrics link in the Explore More
section.