GCP Metrics
Overview
Google Cloud Platform provides built-in monitoring and observability tools that allow users to collect and analyze metrics and traces from their GCP resources. Send Google Cloud metrics and traces seamlessly to Coralogix. Search, analyze, and visualize your data, gaining insights into application behavior, identifying errors, and troubleshooting problems.
For more information about this integration, click here.
How to use with Terraform
To deploy this integration using Terraform, you can use the coralogix_integration
resource provided by the Coralogix Terraform provider. Below is an example configuration:
resource "coralogix_integration" "gcp-metrics-collector" {
integration_key = "gcp-metrics-collector"
version = "1.0.0"
parameters = {
IntegrationName = "<IntegrationName>"
MetricPrefixes = false
ServiceAccountKey = "<ServiceAccountKey>"
}
}
Replace the placeholder values with your actual configuration parameters. Refer to the parameter table below for required fields and their descriptions.
Revisions
1.0.0
Name | Type | Required | Description |
---|---|---|---|
IntegrationName | String | Yes | |
MetricPrefixes | Boolean | Yes | To limit unnecessary API calls that fetch no data but count towards the quota limit, specify only the GCP prefixes of the metrics that actually exist and you want to pull into Coralogix. |
ServiceAccountKey | String | Yes | |
ApplicationLabels | List | No | Select labels whose values will be used as the Application Name. If more than one label can be matched, the first match in the list will be used. |
ApplicationName | String | No | The default name of the application that the integration will be used with. This is used as a fallback when no labels match. |
ProjectId | String | No | The ID of the GCP project from which metrics should be collected. If not provided, the project ID of the service account will be used. |
SubsystemLabels | List | No | Select labels whose values will be used as the Subsystem Name. If more than one label can be matched, the first match in the list will be used. |
SubsystemName | String | No | The default name of the subsystem that the integration will be used with. This is used as a fallback when no labels match. |
0.0.2
Name | Type | Required | Description |
---|---|---|---|
IntegrationName | String | Yes | |
MetricPrefixes | Boolean | Yes | To limit unnecessary API calls that fetch no data but count towards the quota limit, specify only the GCP prefixes of the metrics that actually exist and you want to pull into Coralogix. |
ServiceAccountKey | String | Yes | |
ApplicationLabels | List | No | Select labels whose values will be used as the Application Name. If more than one label can be matched, the first match in the list will be used. |
ApplicationName | String | No | The default name of the application that the integration will be used with. This is used as a fallback when no labels match. |
ProjectId | String | No | The ID of the GCP project from which metrics should be collected. If not provided, the project ID of the service account will be used. |
SubsystemLabels | List | No | Select labels whose values will be used as the Subsystem Name. If more than one label can be matched, the first match in the list will be used. |
SubsystemName | String | No | The default name of the subsystem that the integration will be used with. This is used as a fallback when no labels match. |
Theme
Light