See the supported connectors for Application Integration.
Monitor Application Integration resources
This page provides details on how to monitor the usage and performance of Application Integration resources in your Google Cloud project.
Application Integration leverages Cloud Monitoring to provide visibility into the usage, performance, alerts, and the overall health of your integration resources. You can use Cloud Monitoring to create custom charts and dashboards to visualize the different performance metrics and resource usages of your integrations. Cloud Monitoring also lets you configure alerts and alert policies for these metrics. For example, you can create a chart to view and monitor the amount of data processed for a specific time period. In addition, you can also set up an alert to check if the total data processed exceeds a specified threshold value. For information about configuring alerts, see Alerts.
You can access and monitor all your integration metrics and resource usages in the following ways:
- Using Cloud Monitoring.
- Using the monitoring dashboard in Application Integration.
Available metrics and labels
Resource metrics
Labels
Labels are available for Application Integration in the Google Cloud console. You can group or filter each metric using these labels.
Labels for monitored resource
| Label | Description |
|---|---|
| resource_container | The Google Cloud project ID of the integration. |
| location | The region of the integration. |
| integration | Name of the integration. |
| version | The version ID of the integration. |
Labels for metric type
| Label | Description |
|---|---|
| status | Execution status of the integration or integration step (task or trigger). |
| trigger_name | Type of trigger used to execute the integration. For example: API trigger or Cloud Pub/Sub trigger. |
| trigger_id | The ID of the trigger used to invoke the integration. |
| step_type | Type of integration step, trigger or task. |
| step_name | Name of the task or trigger. For example: API Trigger or Data Mapping task. |
| step_id | For Trigger type: ID of the respective trigger.
For Task type: Task number of the respective task. |
| error_enum | The canonical code of the error that occurred during the integration or integration step execution |
| is_retry | A boolean value to determine if the integration or task execution was retried. |
| is_step_external | A boolean value to determine if the trigger or task execution was internal or external to the Application Integration execution engine.
For example, the Call REST Endpoint task is external, since the API call is made from outside the execution engine. In contrast, the Data Mapping task is internal. |
For a complete list of available Google Cloud metrics, see Google Cloud metrics.
What's next
- Monitor using Cloud Monitoring.
- Monitor using the monitoring dashboard in Application Integration.