-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add opid to log messages from our calls to vsphere #2739
Comments
@carlsone Has mentioned the utility of this opid for full stack performance analysis in the past. |
I could not find the exact opID listed in the |
I tracked this down a bit more. I spoke with Kira on our team about how VCQE is able to log the opid. It turns out, that VC supports client-generated OpIDs, so VCQE generates it and passes it as an “operationID” SOAP element in the SOAP header. My guess is that we could update the govmomi SOAP client (https://github.com/vmware/govmomi/tree/master/vim25/soap) to pass an OPID generated upstream. |
Blocked by vmware/govmomi#749 - zenhub doesn't seem to support cross repo linking for blockers. |
Increase use of trace.Operation as well as pass the operation.ID to vSphere for observability within the vSphere logs. Fixes vmware#2739
Increase use of trace.Operation as well as pass the operation.ID to vSphere for observability within the vSphere logs. Fixes vmware#2739
Increase use of trace.Operation as well as pass the operation.ID to vSphere for observability within the vSphere logs. Fixes vmware#2739
Increase use of trace.Operation as well as pass the operation.ID to vSphere for observability within the vSphere logs. Fixes vmware#2739
Increase use of trace.Operation as well as pass the operation.ID to vSphere for observability within the vSphere logs. Fixes vmware#2739
Increase use of trace.Operation as well as pass the operation.ID to vSphere for observability within the vSphere logs. Fixes vmware#2739
Increase use of trace.Operation as well as pass the operation.ID to vSphere for observability within the vSphere logs. Fixes vmware#2739
Increase use of trace.Operation as well as pass the operation.ID to vSphere for observability within the vSphere logs. Fixes vmware#2739
Increase use of trace.Operation as well as pass the operation.ID to vSphere for observability within the vSphere logs. Fixes vmware#2739
Increase use of trace.Operation as well as pass the operation.ID to vSphere for observability within the vSphere logs. Fixes vmware#2739
Increase use of trace.Operation as well as pass the operation.ID to vSphere for observability within the vSphere logs. Fixes #2739
Increase use of trace.Operation as well as pass the operation.ID to vSphere for observability within the vSphere logs. Fixes vmware#2739
Don't know if govmomi returns the OP ID but the api calls that it is using does according to @derekbeard
It would help future debugging efforts if we added this.
As an engineer on VIC, it would be useful for debugging purposes to include the OP ID on vsphere operations so that we can track operations through vsphere related logs while debugging.
The text was updated successfully, but these errors were encountered: