oci.service_connector_hub.bytes_read_from_source
(count) | Number of bytes read from the source. Note: This value is emitted each time Connector Hub reads data from the source. If failures occur at the task or destination and Connector Hub needs to reread data from the source, the value is emitted again.
Shown as byte |
oci.service_connector_hub.bytes_read_from_task
(count) | Number of bytes moved from the task to Connector Hub.
Shown as byte |
oci.service_connector_hub.bytes_written_to_target
(count) | Number of bytes written to the target. Note: Use this metric as a general indicator of success. BytesWrittenToTarget might not match BytesReadFromSource or BytesReadFromTask. For example, consider a 10MB read intended for an Object Storage target. Connector Hub might compress the data, converting 10MB read into 1MB written.
Shown as byte |
oci.service_connector_hub.bytes_written_to_task
(count) | Number of bytes moved by Connector Hub to the task.
Shown as byte |
oci.service_connector_hub.data_freshness
(gauge) | Indicates age of the oldest processed record of the most recent set.
Shown as millisecond |
oci.service_connector_hub.errors_at_source
(count) | Number of errors that affect retrieving data from source. Tip: To troubleshoot errors, view the errorCode and errorType dimension values. For example, an errorCode value that starts with 5, such as 500, implies a partner service outage, while the errorCode value –1 implies a network outage or timeout.
Shown as error |
oci.service_connector_hub.errors_at_target
(count) | Number of errors that affect writing data to target. Tip: To troubleshoot errors, view the errorCode and errorType dimension values. For example, an errorCode value that starts with 5, such as 500, implies a partner service outage, while the errorCode value –1 implies a network outage or timeout.
Shown as error |
oci.service_connector_hub.errors_at_task
(count) | Number of errors while writing to the task. Tip: To troubleshoot errors, view the errorCode and errorType dimension values. For example, an errorCode value that starts with 5, such as 500, implies a partner service outage, while the errorCode value –1 implies a network outage or timeout.
Shown as error |
oci.service_connector_hub.latency_at_source
(gauge) | Time-to-first-byte when retrieving data from source. Useful for customers to troubleshoot with complex tasks (log rules).
Shown as millisecond |
oci.service_connector_hub.latency_at_target
(gauge) | Time-to-first-byte when writing data to target.
Shown as millisecond |
oci.service_connector_hub.latency_at_task
(gauge) | Time-to-first-byte for task; includes latency reading from the source, errors at the task, and errors writing to the target.
Shown as millisecond |
oci.service_connector_hub.messages_read_from_source
(count) | Number of records read from the source. Note: The value for this metric is cumulative.
Shown as message |
oci.service_connector_hub.messages_read_from_task
(count) | Number of messages moved from the task to Connector Hub.
Shown as message |
oci.service_connector_hub.messages_written_to_target
(count) | Number of records written to the target.
Shown as message |
oci.service_connector_hub.messages_written_to_task
(count) | Number of messages moved by Connector Hub to the task.
Shown as message |
oci.service_connector_hub.service_connector_hub_errors
(count) | Number of errors in Connector Hub that affect moving data from source to target.
Shown as error |
