Solved: Create automatic alerting for Key Visualizer

Nei11s · 03-21-2024 03:30 AM

Hi,

Does anyone know if its possible to setup some automatic email alerts for the Key Visualizer dependent on certain thresholds?

I can't see anything in the documentation, nor the GUI, that indicates this is possible.

ms4446

Unfortunately, you're correct. Key Visualizer doesn't have a native way to set up automatic email alerts based on thresholds. It's designed for diagnosing usage patterns and uncovering potential hotspots or schema design issues. Here are some workarounds to consider:

Cloud Monitoring and Alerts: While you can't mirror Key Visualizer's specific insights with Cloud Monitoring, you can monitor essential Bigtable metrics (like read/write latency and CPU usage). Setting alerts on these metrics can indirectly signal problems that might surface in a Key Visualizer analysis. The key here is to carefully identify which metrics strongly correlate with the types of issues you'd use Key Visualizer to detect.
Google Cloud Functions: Cloud Functions offer a way to automate the monitoring of metrics or analysis of exported data. You could write a function that periodically checks relevant metrics or processes Key Visualizer data and sends email alerts (via supported services) when predefined conditions are met.

Important Considerations:

Complexity: Custom solutions involving data export and analysis will increase the complexity of your setup.
Cost: Be mindful of potential costs associated with frequent API calls for Key Visualizer data or with utilizing Cloud Monitoring and Cloud Functions.
Alert Specificity: Carefully consider the exact conditions that meaningfully warrant an alert. Striking a balance between too many alerts (leading to fatigue) and overly specific alerts (potentially missing important issues) is crucial.

View solution in original post

ms4446

Unfortunately, you're correct. Key Visualizer doesn't have a native way to set up automatic email alerts based on thresholds. It's designed for diagnosing usage patterns and uncovering potential hotspots or schema design issues. Here are some workarounds to consider:

Cloud Monitoring and Alerts: While you can't mirror Key Visualizer's specific insights with Cloud Monitoring, you can monitor essential Bigtable metrics (like read/write latency and CPU usage). Setting alerts on these metrics can indirectly signal problems that might surface in a Key Visualizer analysis. The key here is to carefully identify which metrics strongly correlate with the types of issues you'd use Key Visualizer to detect.
Google Cloud Functions: Cloud Functions offer a way to automate the monitoring of metrics or analysis of exported data. You could write a function that periodically checks relevant metrics or processes Key Visualizer data and sends email alerts (via supported services) when predefined conditions are met.

Important Considerations:

Complexity: Custom solutions involving data export and analysis will increase the complexity of your setup.
Cost: Be mindful of potential costs associated with frequent API calls for Key Visualizer data or with utilizing Cloud Monitoring and Cloud Functions.
Alert Specificity: Carefully consider the exact conditions that meaningfully warrant an alert. Striking a balance between too many alerts (leading to fatigue) and overly specific alerts (potentially missing important issues) is crucial.