From 17e2e0946c39e21b9123455b4926093763bc264f Mon Sep 17 00:00:00 2001 From: Matthew Treinish Date: Thu, 19 Nov 2015 18:57:45 -0500 Subject: [PATCH] Add a node_region field to the job metadata The node region can be figured out from the build_node very easily and having a discrete field will make filtering to a single region much simpler. This commit adds a new metadata field 'node_region' which is the cloud region that the build_node ran in. Change-Id: I06bbb62d21871ee61dbfb911143efff376992b98 --- log_processor/client.py | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/log_processor/client.py b/log_processor/client.py index d955c2f..4957fe7 100644 --- a/log_processor/client.py +++ b/log_processor/client.py @@ -126,6 +126,12 @@ class EventProcessor(threading.Thread): elif parameters.get("ZUUL_NEWREV"): fields["build_newrev"] = parameters.get("ZUUL_NEWREV", "UNKNOWN") + if ["build_node"] != "UNKNOWN": + node_region = '-'.join( + fields["build_node"].split('-')[-3:-1]) + fields["node_region"] = node_region or "UNKNOWN" + else: + fields["node_region"] = "UNKNOWN" return fields def _parse_event(self, event, fileopts):