)]}'
{"telemetry_tempest_plugin/ceilometer/api/test_compute_metrics.py":[{"author":{"_account_id":36393,"name":"Callum Dickinson","email":"callum.dickinson@catalystcloud.nz","username":"Callum027","status":"Catalyst Cloud"},"change_message_id":"9b529239486b39e5d1d0a56f719903c758620f41","unresolved":true,"context_lines":[{"line_number":25,"context_line":""},{"line_number":26,"context_line":"class ComputeMetricsTest(base.BaseCeilometerMetricTest):"},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"    EXPECTED_METRICS \u003d ["},{"line_number":29,"context_line":"        \u0027cpu\u0027,"},{"line_number":30,"context_line":"        \u0027vcpus\u0027,"},{"line_number":31,"context_line":"        \u0027memory\u0027,"}],"source_content_type":"text/x-python","patch_set":1,"id":"ec3c2187_48d8848b","line":28,"updated":"2026-05-13 21:54:16.000000000","message":"Since Ceilometer is quite flexible in terms of what metrics can be configured to be published for resources, this should also be configurable to allow operators to select what metrics to check for.","commit_id":"ba1a2fedd2ef3f98b59a315c5e35f9856469ddc4"},{"author":{"_account_id":13177,"name":"Emma Foley","email":"efoley@redhat.com","username":"emma-l-foley"},"change_message_id":"4785b216619a3fd064fec743a992856f9d5363f9","unresolved":true,"context_lines":[{"line_number":25,"context_line":""},{"line_number":26,"context_line":"class ComputeMetricsTest(base.BaseCeilometerMetricTest):"},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"    EXPECTED_METRICS \u003d ["},{"line_number":29,"context_line":"        \u0027cpu\u0027,"},{"line_number":30,"context_line":"        \u0027vcpus\u0027,"},{"line_number":31,"context_line":"        \u0027memory\u0027,"}],"source_content_type":"text/x-python","patch_set":1,"id":"eb2aafb3_bea42a49","line":28,"in_reply_to":"a66184ff_00dd72c1","updated":"2026-05-26 11:57:26.000000000","message":"That makes sense, and IINM, we should be able to get devstack to populate the config with the values from ceilometer/polling.yaml!","commit_id":"ba1a2fedd2ef3f98b59a315c5e35f9856469ddc4"},{"author":{"_account_id":36393,"name":"Callum Dickinson","email":"callum.dickinson@catalystcloud.nz","username":"Callum027","status":"Catalyst Cloud"},"change_message_id":"bc13275e34078f0eed2c26ec8d4fbdc53e2de052","unresolved":true,"context_lines":[{"line_number":25,"context_line":""},{"line_number":26,"context_line":"class ComputeMetricsTest(base.BaseCeilometerMetricTest):"},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"    EXPECTED_METRICS \u003d ["},{"line_number":29,"context_line":"        \u0027cpu\u0027,"},{"line_number":30,"context_line":"        \u0027vcpus\u0027,"},{"line_number":31,"context_line":"        \u0027memory\u0027,"}],"source_content_type":"text/x-python","patch_set":1,"id":"a66184ff_00dd72c1","line":28,"in_reply_to":"c3b4face_b386c58b","updated":"2026-05-13 22:31:21.000000000","message":"The easiest way to do this would be to add a new list opt in `telemetry_tempest_plugin/config.py` for this, with the default value set to what Ceilometer is configured to poll by default (so all of the built-in ones).","commit_id":"ba1a2fedd2ef3f98b59a315c5e35f9856469ddc4"},{"author":{"_account_id":13177,"name":"Emma Foley","email":"efoley@redhat.com","username":"emma-l-foley"},"change_message_id":"003260f935b9ad69c0bc23479abcf8d1a1d2c69b","unresolved":true,"context_lines":[{"line_number":25,"context_line":""},{"line_number":26,"context_line":"class ComputeMetricsTest(base.BaseCeilometerMetricTest):"},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"    EXPECTED_METRICS \u003d ["},{"line_number":29,"context_line":"        \u0027cpu\u0027,"},{"line_number":30,"context_line":"        \u0027vcpus\u0027,"},{"line_number":31,"context_line":"        \u0027memory\u0027,"}],"source_content_type":"text/x-python","patch_set":1,"id":"c3b4face_b386c58b","line":28,"in_reply_to":"ec3c2187_48d8848b","updated":"2026-05-13 22:24:26.000000000","message":"Thank you for the feedback.  This is a first pass, and needs more refinement. There\u0027s more consideration needed for detection of what metrics can be expected.  Probably, the best default is assuming all pollsters are active (default with devstack, right?), and then check per service what\u0027s enabled.\nI\u0027ve tried checking polling.yaml if it\u0027s available, which cannot/should not be assumed. There should be a config to tell tempest which ones to check for, using a regex, similar to whats in polling.yaml.","commit_id":"ba1a2fedd2ef3f98b59a315c5e35f9856469ddc4"}]}