You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to config a vcenterreciver and got a stack trace of runtime error saying:
panic: runtime error: invalid memory address or nil pointer dereference.
Steps to Reproduce
Install otel-collector-contrib on your PC and use a config.yaml to receive metrics from vCenter in version 7.0.3
Expected Result
normal metrics of vcenter
Actual Result
panic: runtime error: invalid memory address or nil pointer dereference.
Thanks for filing @shacharSirotkin, is that the full stack trace from the panic? It would be helpful to have more specific information about where the panic occurred in buildVMMetrics.
Component(s)
vCenter receiver
What happened?
Description
I tried to config a vcenterreciver and got a stack trace of runtime error saying:
panic: runtime error: invalid memory address or nil pointer dereference.
Steps to Reproduce
Install otel-collector-contrib on your PC and use a config.yaml to receive metrics from vCenter in version 7.0.3
Expected Result
normal metrics of vcenter
Actual Result
panic: runtime error: invalid memory address or nil pointer dereference.
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/vcenterreceiver.(*vcenterMetricScraper).buildVMMetrics()
.....
Collector version
0.105.0
Environment information
Environment
Windows 10 Enterprise
OpenTelemetry Collector configuration
Log output
panic: runtime error: invalid memory address or nil pointer dereference. github.com/open-telemetry/opentelemetry-collector-contrib/receiver/vcenterreceiver.(*vcenterMetricScraper).buildVMMetrics() .....
Additional context
No response
The text was updated successfully, but these errors were encountered: