I don't think there's any useful information hiding in the fact that cloud-init logs some messages as DataSourceAzure.py[DEBUG] and others as azure.py[DEBUG]. Look at:
See that some messages are logged with LOG.debug(), while others with report_diagnostic_event(). This latter function is defined in azure.py, hence the difference. It could have been LOG.debug() all the time, then we would always have DataSourceAzure.py[DEBUG]. I'm not sure of what was the rationale for the two ways of logging, maybe report_diagnostic_event() was used for "more useful" debugging messages? Anyway I doubt it will help debugging this issue.
Hi again Guilherme,
I don't think there's any useful information hiding in the fact that cloud-init logs some messages as DataSourceAzure .py[DEBUG] and others as azure.py[DEBUG]. Look at:
https:/ /github. com/canonical/ cloud-init/ blob/45db197cfc 7e3488baae7dc10 53c45da070248f6 /cloudinit/ sources/ DataSourceAzure .py#L691
See that some messages are logged with LOG.debug(), while others with report_ diagnostic_ event() . This latter function is defined in azure.py, hence the difference. It could have been LOG.debug() all the time, then we would always have DataSourceAzure .py[DEBUG] . I'm not sure of what was the rationale for the two ways of logging, maybe report_ diagnostic_ event() was used for "more useful" debugging messages? Anyway I doubt it will help debugging this issue.