To investigate potential issues regarding Google Cloud Platform monitoring, follow the instructions below.
1. Verify installation
Check whether installation was successful.
- For the GKE integration, see Verify installation for the GKE integration
- For the GCP function, see Verify installation for the GCP function
2. Enable self-monitoring optional
Self-monitoring allows quick diagnosis to see if your monitoring function processes and sends logs to Dynatrace properly.
To enable self-monitoring for the GCP function deployment
- In the GCP console, go to Cloud Functions.
- Select dynatrace-gcp-function.
- Select Edit.
- Under Runtime, build and connection settings, change the value of the
SELF_MONITORING_ENABLEDruntime environment variable to
- Select Next, and then select Deploy to apply the new settings.
To enable self-monitoring for the GKE deployment
- Connect to the Kubernetes cluster where the GCP function is running.
- Edit the configmap.
kubectl -n dynatrace edit configmaps dynatrace-gcp-function-config
- Change the value of the
- Restart the GCP function.
kubectl -n dynatrace rollout restart deployment dynatrace-gcp-function
The Dynatrace GCP function reports self-monitoring metrics as Google Cloud metrics. See below the list of self-monitoring metrics for metric/log ingest.
Self-monitoring metrics for metric ingest (for GKE and GCP function deployments)
|MINT lines ingested||The number of data points (metrics with dimension or dimensions) ingested by Dynatrace Metrics API v2 in a given interval.|
|Dynatrace connectivity||The connectivity status (
|Dynatrace failed requests count||The number of requests rejected by Dynatrace Metrics API v2. The reason for failure can be that the data point value doesn't comply with the metric ingestion protocol syntax, or that the limit for metric ingestion is exceeded.|
|Dynatrace requests count||The number of requests sent to Dynatrace.|
Self-monitoring metrics for log ingest (for GKE deployment)
|All requests||All requests sent to Dynatrace|
|Dynatrace connectivity failures||The number of failed requests to connect to Dynatrace|
|Too old records||The number of log records that were invalid because the timestamp was too old|
|Too long content size||The number of records with content exceeding the maximum content length|
|Parsing errors||The number of errors that occurred while parsing logs|
|Processing time||The total amount of time for processing logs|
|Sending time||The total amount of time for sending logs|
|Sent logs entries||The number of log entries sent to Dynatrace|
|Log ingest payload size||The size of the log payload sent to Dynatrace (in kb)|
View self-monitoring metrics
The self-monitoring dashboards present multiple metrics related to the Dynatrace connectivity status, amount of data processed, and execution times.
To view the dashboards with self-monitoring metrics
- In your GCP console, go to the GCP Monitoring service.
- Select Dashboards.
- Depending on the type of deployment selected, search for
dynatrace-gcp-function log self monitoringdashboard (for logs)
dynatrace-gcp-function self monitoringdashboard (for metrics)