Connector Hub Metrics Reference
Review details about the metrics emitted for the metric namespace oci_service_connector_hub
(the Connector Hub service).
Before You Begin
IAM policies: To monitor resources, you must be granted the required type of access in a policy written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. The policy must give you access to the monitoring services as well as the resources being monitored. If you try to perform an action and get a message that you don't have permission or are unauthorized, contact the administrator to find out what type of access you were granted and which compartment you need to work in. For more information about user authorizations for monitoring, see IAM Policies.
Administrators: For common policies that give groups access to metrics, see Metric Access for Groups (Securing Monitoring). For common policies that give groups access to Connector Hub, see IAM Policies (Securing Connector Hub).
The metrics in oci_service_connector_hub
are automatically available for any connectors you create. You don't need to enable monitoring on the resource to get these metrics.
Available Metrics: oci_service_connector_hub
Dimensions
Connector Hub service metrics include the following dimensions :
- connectorId
- The OCID of the connector that the metrics apply to.
- connectorName
- The name of the connector that the metrics apply to.
- errorCode
- The error code. Examples:
404
,500
,-1
- errorType
- The type of error. Examples:
NotAuthorizedOrNotFound
,TooManyRequests
- region
- The region that the metrics apply to.
- sourceName
- The name of the source service that the metrics apply to.
- targetName
- The name of the target service that the metrics apply to.
- taskName
- The name of the task service that the metrics apply to.
Descriptions
Following are descriptions of the Connector Hub service metrics:
Metric | Metric Display Name | Unit | Description | Dimensions |
---|---|---|---|---|
BytesReadFromSource
|
Bytes read from source | Bytes |
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. |
|
BytesReadFromTask
|
Bytes read from task | Bytes |
Number of bytes moved from the task to Connector Hub. |
|
BytesWrittenToTarget
|
Bytes written to target | Bytes |
Number of bytes written to the target. Note:
|
|
BytesWrittenToTask
|
Bytes written to task | Bytes |
Number of bytes moved by Connector Hub to the task. |
|
DataFreshness
|
Data freshness | Milliseconds |
Indicates age of the latest processed record of the most recent set. For example, let's say that the connector received a set of five records at 10:00. Three records have a 09:55 timestamp, while the other two records have a 09:45 timestamp. Because the most recent record has a 09:55 timestamp, the calculated lag is 5 minutes. |
|
ErrorsAtSource
|
Errors at source | Count |
Number of errors that affect retrieving data from source. Tip:
To troubleshoot errors, view the |
|
ErrorsAtTarget
|
Errors at target | Count |
Number of errors that affect writing data to target. Tip:
To troubleshoot errors, view the |
|
ErrorsAtTask
|
Errors at task | Count |
Number of errors while writing to the task. Tip:
To troubleshoot errors, view the |
|
LatencyAtSource
|
Latency at source | Milliseconds |
Time-to-first-byte when retrieving data from source. Useful for customers to troubleshoot with complex tasks (log rules). |
|
LatencyAtTarget
|
Latency at target | Milliseconds |
Time-to-first-byte when writing data to target. |
|
LatencyAtTask
|
Latency at task | Milliseconds |
Time-to-first-byte for task; includes latency reading from the source, errors at the task, and errors writing to the target. |
|
MessagesReadFromSource
|
Messages read from source | Count |
Number of records read from the source. Note: The value for this metric is cumulative. For example, when a connector reads a single message from the source, the connector emits a |
|
MessagesReadFromTask
|
Messages read from task | Count |
Number of messages moved from the task to Connector Hub. |
|
MessagesWrittenToTask
|
Messages written to task | Count |
Number of messages moved by Connector Hub to the task. |
|
MessagesWrittenToTarget
|
Messages written to target | Count |
Number of records written to the target. |
|
ServiceConnectorHubErrors
|
Connector Hub Errors | Count |
Number of errors in Connector Hub that affect moving data from source to target. |
|