We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
On Matsya module-metricshub, Wbem queries fail with some hosts.
Here is an example of a failing query sent by Hardware Sentry KM to Matsya module-metricshub (host : hp3par-san)
<MetricsHubOperation> <Host>hp3par-san</Host> <Id>hp3par-san</Id> <hostType>Storage</hostType> <ExcludedConnectors></ExcludedConnectors> <SelectedConnectors></SelectedConnectors> <WBEM> <Username>#########</Username> <Password>######### </Password> <Protocol>https</Protocol> <Port>5989</Port> <Timeout>120</Timeout> </WBEM> <OperationType>Discovery</OperationType> <LogFile></LogFile> </MetricsHubOperation>
No connectors detected on Metricshub CLI and MetricsHub Agent:
In Metricshub logs, here is a screenshot showing the exception found after running the above command:
The same problem was reported with the host eternus-i0
We have to double check Wbem processing on MetricsHub.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
On Matsya module-metricshub, Wbem queries fail with some hosts.
Here is an example of a failing query sent by Hardware Sentry KM to Matsya module-metricshub (host : hp3par-san)
No connectors detected on Metricshub CLI and MetricsHub Agent:
In Metricshub logs, here is a screenshot showing the exception found after running the above command:
The same problem was reported with the host eternus-i0
We have to double check Wbem processing on MetricsHub.
The text was updated successfully, but these errors were encountered: