apex / apex/up

Ignore active warming for latency alerts

未关闭
#662 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
Feature Request
主要语言
Go
星标
8.8k
派生
383
PR 合并指标
30 天内没有已合并 PR

描述

## Prerequisites

* [x] I am running the latest version. (`up upgrade`)
* [x] I searched to see if the issue already exists.
* [x] I inspected the verbose debug output with the `-v, --verbose` flag.
* [x] Are you an Up Pro subscriber?

## Description

Hi, I have active warming enabled:
```
"lambda": {
"memory": 1024,
"runtime": "nodejs8.10",
"warm": true,
"warm_count": 15,
"warm_rate": "15m"
}
```

I also have an alert to notify me about latency > 500ms:
```
{
"metric": "http.latency",
"statistic": "avg",
"threshold": 500,
"period": "5m",
"operator": ">",
"description": "The request latency was higher than 500ms on average in the past 5 minutes."
},
```

How can I prevent the alert from triggering when the active warming Lambda runs? So just let the alert notify me when my actual application has latency issues.

## Love Up?

Yes :)

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。