Implement GCP (Google Cloud) Monitoring Sensors with Azure-equivalent Functionality
As a Cloud/ DevOps engineer, I want to have sensors for Google Cloud Platform (GCP) similar to those available for Azure, so that I can monitor and manage my GCP infrastructure with the same level of visibility and control that I have for Azure environments.
Hi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time. This decision was made based on several factors, which may include:
- It doesn't align with our current product roadmap or strategic priorities.
- The resources required for implementation outweigh the current projected benefits for our user base.
- There are technical limitations that prevent us from moving forward.
- A similar feature is already available or planned in a different way.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
Paweł Bołdyn commented
Hi,
From an engineering standpoint, having native GCP sensors aligned with Azure functionality would significantly improve consistency and observability across multi-cloud environments.Specifically, it would be valuable to have first-class sensors for:
Compute Engine – instance state, CPU utilization, disk I/O, network throughput
Cloud Monitoring (Stackdriver) – direct consumption of metrics and alert policies
GKE – node/pod health, cluster state, resource utilization
Cloud SQL – performance metrics, connections, replication status
Load Balancing – backend health, latency, request rates
IAM / quotas / billing – visibility into limits, usage, and cost metricsKey technical expectations would include:
Native integration with GCP APIs (with proper authentication via service accounts / IAM roles)
Standardized sensor structure similar to Azure sensors (to ensure consistency in dashboards and alerts)
Support for tagging/label-based filtering (common in GCP resource organization)
Efficient polling and rate-limit awareness
Ability to map GCP metrics directly into PRTG channels without custom parsingWithout this, teams operating in GCP are forced to rely on less scalable and harder-to-maintain custom solutions, which reduces the overall effectiveness of PRTG as a unified monitoring platform.
This feature would close a significant gap in multi-cloud monitoring capabilities.