...
Proposal 1 is too high level and doesn't get into the internals of what meters get mapped to what and what units should be associated with the meters/events - in essence it doesn't improve on what's there today for overlapping meters. However is good for new meters.
Proposal 2
...
involves 2 schema
| Code Block | ||||
|---|---|---|---|---|
| ||||
{
"$schema": "http://json-schema.org/draft-04/schema#",
"title": "Collectd Mapping Schema",
"description": "A mapping from collectd meters and events to *other* meters and events",
"type": "object",
"properties": {
"resource_id": {
"description": "Mappings from collectd resource_id to other framework resource_id",
"type": "object",
"items": {
"type": "array",
"items": {
"collectd_resource_id": "string",
"new_resource_id": "string"
}
}
},
"meters": {
"description": "Mappings from collectd meters to other framework meters",
"type": "object",
"items": {
"type": "array",
"items": {
"collectd_meter": "string",
"new_meter": "string",
"new_meter_unit": "string"
}
}
},
"events": {
"description": "Mappings from collectd events to other framework events",
"type": "object",
"items": {
"type": "array",
"items": {
"collectd_event": "string",
"new_event": "string",
"collectd_severity": "string",
"new_severity": "string"
}
}
}
}
} |
...