Score:0

GCP Monitoring Alerts - Can you take an average across metric attributes?

za flag

We're using Bluemedora BindPlane to send on-prem utilization metrics to GCP.

In so doing, we're trying to create a GCP monitoring alert that will alert us if the CPU % for a server goes and stays above 95% for 15 minutes.

But we're getting an alert incident for each core.

Is anyone familiar enough with MQL such that they could offer how I could restructure the below such that I obtain an average across cores, rather than an incident per core?

fetch generic_node
| metric 'external.googleapis.com/bluemedora/linux_host/cpu/utilization'
| filter (resource.node_id == 'hdn-tst-app06')
| group_by [metric.core], [value_utilization_mean: mean(value.utilization)]
| every 15m
| condition value_utilization_mean > 95 '%'
| window 15m
Score:0
cn flag

I would try to add a secondary aggregation, using another group_by.

| group_by [metric.core],
    [value_utilization_mean_mean: mean(value_utilization_mean)]
| group_by [],
    [value_utilization_mean_mean_mean: mean(value_utilization_mean_mean)]
| condition value_utilization_mean > 95 '%' 

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.