Metrics Sample's resource_metadata missed instance's metadata field
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Except for meta_data name starts with "metering.", we find that discovered Instance's metadata field is missing in Metrics Sample's resource_metadata. We are not sure if it is designed or it is just a miss. This field is important to us for we want to leverage this field to populate more resource info to back-end storage(E.g. openTSDB) at method publish_
For usering facing perspective, it'd be more straightforward to get known VM's FQDN & related IP for each metrics.
E.g. below is current resource_matadata of Metric "cpu_util" sample.
"resource_metadata" : {
"cpu_number" : 1,
"display_name" : "test06",
"name" : "instance-
"disk_gb" : 1,
"image" : {
"id" : "92cf3554-
"links" : [
{
"href" : "http://
"rel" : "bookmark"
}
],
"name" : "oria_image"
},
"ephemeral_gb" : 0,
"host" : "073a87e7535bae
"memory_mb" : 512,
"instance_type" : "1",
"vcpus" : 1,
"root_gb" : 1,
"image_ref" : "92cf3554-
"flavor" : {
"name" : "m1.tiny",
"links" : [
{
"href" : "http://
"rel" : "bookmark"
}
],
"ram" : 512,
"ephemeral" : 0,
"vcpus" : 1,
"disk" : 1,
"id" : "1"
},
"OS-EXT-
"image_ref_url" : "http://
}
However, when I looked at nova show <uuid>, I found there is a metadata attribute which saves lots of information such as vm fqdn as below:
metadata | {"project_cos": "dev", "fqdn": "xxxx-327632.
For compute resource, If we explicitly populate discovered Instance's metadata field to Metrics Sample's resource_metadata, it will be very useful.
Changed in ceilometer: | |
status: | New → Confirmed |
description: | updated |
description: | updated |