Sporadic Metric
Agents may send metrics that are event based (i.e. are sent irregularly - sporadically). By default all alarms will be kept in UNDETERMINED state if a metric is not sent in a specific time interval. With having 'sporadic' information user/operator will be able to create appropriate alarm that will be suppressed from transitioning to UNDETERMINED state. Sporadic must be just a characteristic of the metric and not part of the metric identity. This approach is very useful for deterministic alarms
In order to do this, the metric creation in the REST request need to specify if the metric is sporadic or not using a flag. Something like:
POST /v2.0/metrics HTTP/1.1
Host: 192.168.10.4:8070
Content-Type: application/json
X-Auth-Token: 27feed73a0ce413
Cache-Control: no-cache
{
"name":"name1",
"dimensions":{
"
"
},
"timestamp"
"value":1.0,
"sporadic": True
}
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Igor Natanael
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by