google cloud platform - GCP Storage Transfer Service is not publishing error count metric for a transfer job - Stack Overflow

admin管理员组

文章数量:1289834

I'm using Google Cloud Storage Transfer Service to transfer data between Cloud Storage buckets via agentless transfer, and I've noticed that the error count metric (storage_transfer_job.error_count) is not being published for my transfer job. Even when the job encounters failures (e.g., due to missing objects or permission issues), the metric does not reflect any errors. Other related metrics, such as storage_transfer_job.found_bytes_count, are being updated correctly. This issue makes it difficult to monitor and alert on transfer failures programmatically.

I have verified that Cloud Monitoring is enabled and that other transfer-related metrics are being updated. However, despite these failures being logged, storage_transfer_job.error_count remains at zero. I expected this metric to increment when errors occur, allowing me to monitor and alert on failed transfers, but that is not happening. Is there any additional configuration required, or could this be a bug?

I'm using Google Cloud Storage Transfer Service to transfer data between Cloud Storage buckets via agentless transfer, and I've noticed that the error count metric (storage_transfer_job.error_count) is not being published for my transfer job. Even when the job encounters failures (e.g., due to missing objects or permission issues), the metric does not reflect any errors. Other related metrics, such as storage_transfer_job.found_bytes_count, are being updated correctly. This issue makes it difficult to monitor and alert on transfer failures programmatically.

I have verified that Cloud Monitoring is enabled and that other transfer-related metrics are being updated. However, despite these failures being logged, storage_transfer_job.error_count remains at zero. I expected this metric to increment when errors occur, allowing me to monitor and alert on failed transfers, but that is not happening. Is there any additional configuration required, or could this be a bug?

• google-cloud-platform
• google-cloud-data-transfer

Share Improve this question Follow asked Feb 21 at 7:26 Pranav BansalPranav Bansal 1111 bronze badge 2

• Please clarify your specific problem or provide additional details to highlight exactly what you need. As it's currently written, it's hard to tell exactly what you're asking. – Community Bot Commented Feb 21 at 8:11
• Try to look at more detailed logging this way: cloud.google/storage-transfer/docs/… – dany L Commented Feb 21 at 14:34

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

Despite not being able to provide additional details to highlight exactly what you need, I suspect that there may be an issue specifically with how error counts are being handled or reported.

Here’s my thoughts to troubleshoot why the storage_transfer_job.error_count metric isn't updating correctly:

1. If you're using the gcloud CLI or the API, ensure that you've configured your transfer job to store logs by using the --log-dir=logs-directory flag when creating the transfer job. Then you will be able to inspect your transfer logs to determine why these files failed. If you didn’t use this flag then you will need to run the transfer job again.

   Once you have logs, inspect them carefully to see the specific errors (e.g., permission issues, missing files). This can provide insight into why the error_count metric isn’t incrementing.

2. For common troubleshooting steps, refer to the troubleshooting guide for Cloud Storage Transfer to see if there are known issues or additional steps to resolve specific transfer failures.

3. Make sure that you have the Monitoring Viewer (roles.monitoring.viewer ) role, or equivalent permissions, to view metrics in Cloud Monitoring. You can check your permissions by going to the IAM & Admin page in the Google Cloud Console.

4. If you can’t find the source of the issue or need a deeper investigation into why the error count metric isn’t updating, it’s best to contact Google Cloud Support directly. They can provide more in-depth assistance.

I hope it helps!

本文标签：