Closed Paul-Jazz closed 3 years ago
:tada: Thanks for opening your first issue here! Welcome to the community!
Thanks for the feedback. I think I found the cause. 'Working on it.
It turns out that "timeRangeType": "ALERT_UPDATED" is not a supported parameter. If it does happen to work, since it isn't supported, it might be removed at any time. You can do something like the following with POST /v2/alert, however, to get the same result:
{
"detailed": false,
"filters": [
{
"name": "alert.status",
"value": "resolved",
"operator": "="
},
{
"name": "alert.status",
"value": "open",
"operator": "="
},
{
"name": "timeRange.type",
"operator": "=",
"value": "ALERT_UPDATED"
}
],
"timeRange": {
"type": "relative",
"value": {
"amount": "24",
"unit": "hour"
}
},
"limit": 100
}
Thank you for taking the time to help us improve our documentation! Please describe the problem and a suggested fix below and we'll get back to you as soon as we can. --DevRel
Describe the problem
With alerts v2, I am told that you can specify :
But there is no information or detail on the "timeRangeType": "ALERT_UPDATED" parameter
Suggested fix