John, while on the subject of execution ID's and such, during the logging of a psensure, can we add the psensure key to the log so it always outputs what it is checking and validating? How it is now:
INFO : 2018-12-11 20:31:07Z - Configuration drift detected.
DEBUG: 2018-12-11 20:31:07Z - Adding to execution plan.
DEBUG: 2018-12-11 20:31:11Z - Collecting configuration...
DEBUG: 2018-12-11 20:31:11Z - Comparing configuration...
INFO : 2018-12-11 20:31:11Z - Configuration matches template.
DEBUG: 2018-12-11 20:31:14Z - Collecting configuration...
DEBUG: 2018-12-11 20:31:14Z - Comparing configuration...
INFO : 2018-12-11 20:31:14Z - Configuration matches template.
and so on. Maybe it could log something like "Collecting configuration <key>" and "<key> matches template". That way it would make each line meaningful and bring more value into keeping the logs. Eventually I would like to have a way to save a copy of the txt execution into servicenow so we have a record of it in change management system as well. The url you shared previously will help in doing that I think. This improvement would help as documentation for each change. Thanks!