What are you passing under "id"?
You only pass id when editing existing silence (it must be an id of a valid
active silence), not when creating a new one.
On Monday, 11 May 2020 14:46:47 UTC+1, TechJunkie wrote:
>
> Hie all ,
> I am struck trying to POST a python dictionary as json for creating
You could also just tell grafana to render null values as zeros. There's a
"Null value" select on the visualisation tab:
[image: Screen Shot 2020-05-02 at 15.41.45.png]
On Saturday, 2 May 2020 11:26:12 UTC+1, Albert Aleksandrov wrote:
>
> Hi all!
> I have some areas with absent values
This is not valid json, paste it to https://jsonlint.com/ to verify.
Valid JSON body example would be:
[{
"status": "firing",
"labels": {
"alertname": "InstanceDown",
"instance": "localhost:9100",
"job": "node",
"severity": "warning"
},
"annotations": {},
"startsAt": "2020-04-06T19:57:38.628106884
Authentication, authorization and multi tenancy comes up a lot in questions
so I've decided to take a stab at it after a feature request (
https://github.com/prymitive/karma/issues/1347).
Starting with 0.56 karma will now have ability to block silences from being
added to alertmanager using ACL r
Did you try something like "changes(foo[30m]) > 10" ? That would alert if
the value changed 10 times in the last 30 minutes.
On Friday, 28 February 2020 16:21:53 UTC, Moses Moore wrote:
>
> (Looks like my previous ask of this question got spamblocked because I
> included a screenshot. c'est la
Did you see this post:
https://www.robustperception.io/using-time-series-as-alert-thresholds? That
pattern works well
On Tuesday, 18 February 2020 13:52:42 UTC, Saurabh Garg wrote:
>
> Hi All,
>
> Can anyone please share the configuration to apply an alert rule on
> different set of machines w
6 matches
Mail list logo
