Bug 1475681

Do we have a way to push a dashboard into Kibana externally in the viaq setup?

According to what Rich said it will be possible in OpenShift 3.6.

Hi these would be few of the dashboard queries it would be interesting to see.

- some efficient queries from DWH report based on timeline (what was status of - DC, storage, VMs, hosts at specific time)
- API response avarage/actual times graph
- trend graph of disk space per storage / per DC / per cluster (future expectation of 1 month)
- parsable engine and vdsm logs based on Correlation-ID to easy seach cause of problem

Is that realistic to get into 4.2.1?

https://www.ovirt.org/develop/release-management/features/metrics/metrics-store-installation/#example-dashboards

Error while importing visualizations:

Error: Could not locate that index-pattern-field (id: ovirt.engine_fqdn.raw)
KbnError@https://kibana.example.com/bundles/commons.bundle.js?v=10229:57511:21
SavedObjectNotFound@https://kibana.example.com/bundles/commons.bundle.js?v=10229:57640:6
FieldAggParamFactory/FieldAggParam.prototype.deserialize@https://kibana.example.com/bundles/kibana.bundle.js?v=10229:49376:16
AggConfigFactory/AggConfig.prototype.fillDefaults/<@https://kibana.example.com/bundles/kibana.bundle.js?v=10229:53866:20
AggConfigFactory/AggConfig.prototype.fillDefaults@https://kibana.example.com/bundles/kibana.bundle.js?v=10229:53844:8
AggConfig@https://kibana.example.com/bundles/kibana.bundle.js?v=10229:53758:8
AggConfigs/<.initialSet<@https://kibana.example.com/bundles/kibana.bundle.js?v=10229:54464:19
AggConfigs@https://kibana.example.com/bundles/kibana.bundle.js?v=10229:54462:22
VisFactory/Vis.prototype.setState@https://kibana.example.com/bundles/kibana.bundle.js?v=10229:48822:20
__WEBPACK_AMD_DEFINE_RESULT__</</SavedVis.prototype._updateVis@https://kibana.example.com/bundles/kibana.bundle.js?v=10229:56374:8
__WEBPACK_AMD_DEFINE_RESULT__</</SavedVis.prototype._afterEsResp/<@https://kibana.example.com/bundles/kibana.bundle.js?v=10229:56317:28
processQueue@https://kibana.example.com/bundles/commons.bundle.js?v=10229:42452:29
scheduleProcessQueue/<@https://kibana.example.com/bundles/commons.bundle.js?v=10229:42468:28
$RootScopeProvider/this.$get</Scope.prototype.$eval@https://kibana.example.com/bundles/commons.bundle.js?v=10229:43696:17
$RootScopeProvider/this.$get</Scope.prototype.$digest@https://kibana.example.com/bundles/commons.bundle.js?v=10229:43507:16
$RootScopeProvider/this.$get</Scope.prototype.$apply@https://kibana.example.com/bundles/commons.bundle.js?v=10229:43804:14
link/</reader.onload@https://kibana.example.com/bundles/kibana.bundle.js?v=10229:62025:14

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

I added a step to the kibana dashboards import

https://github.com/sradco/ovirt-site/blob/aa2d653c543eb51571b22455ba1e497032971c7a/source/develop/release-management/features/metrics/metrics-store-installation.html.md

In order for field of type raw to be accessed, the index should be refreshed before loading the visualizations.
They are generated automatically when a sting fields are saved to the index.

Same result after the refresh of indices:


Saved Objects: Could not locate that index-pattern (id: project.ovirt-metrics-test-engine.d3a9f511-0508-11e8-9a49-001a4a013f0b.*)

Error: Could not locate that index-pattern (id: project.ovirt-metrics-test-engine.d3a9f511-0508-11e8-9a49-001a4a013f0b.*)
KbnError@https://kibana.tlv-metrics-store.eng.lab.tlv.redhat.com/bundles/commons.bundle.js?v=10229:57511:21
SavedObjectNotFound@https://kibana.tlv-metrics-store.eng.lab.tlv.redhat.com/bundles/commons.bundle.js?v=10229:57640:6
applyESResp@https://kibana.tlv-metrics-store.eng.lab.tlv.redhat.com/bundles/kibana.bundle.js?v=10229:45045:37
processQueue@https://kibana.tlv-metrics-store.eng.lab.tlv.redhat.com/bundles/commons.bundle.js?v=10229:42452:29
scheduleProcessQueue/<@https://kibana.tlv-metrics-store.eng.lab.tlv.redhat.com/bundles/commons.bundle.js?v=10229:42468:28
$RootScopeProvider/this.$get</Scope.prototype.$eval@https://kibana.tlv-metrics-store.eng.lab.tlv.redhat.com/bundles/commons.bundle.js?v=10229:43696:17
$RootScopeProvider/this.$get</Scope.prototype.$digest@https://kibana.tlv-metrics-store.eng.lab.tlv.redhat.com/bundles/commons.bundle.js?v=10229:43507:16
$RootScopeProvider/this.$get</Scope.prototype.$apply@https://kibana.tlv-metrics-store.eng.lab.tlv.redhat.com/bundles/commons.bundle.js?v=10229:43804:14
done@https://kibana.tlv-metrics-store.eng.lab.tlv.redhat.com/bundles/commons.bundle.js?v=10229:38253:37
completeRequest@https://kibana.tlv-metrics-store.eng.lab.tlv.redhat.com/bundles/commons.bundle.js?v=10229:38451:8
requestLoaded@https://kibana.tlv-metrics-store.eng.lab.tlv.redhat.com/bundles/commons.bundle.js?v=10229:38392:10

Target milestone is 4.2.2?

(In reply to Yaniv Kaul from comment #10)
> Target milestone is 4.2.2?

I see I moved it to 4.2.3 by mistake. Moved back to 4.2.3.

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Yes, all indices were refreshed.

Please make sure that you wait a minute and make sure that collectd and fluentd are running on the host with the vms. If the data about vms is not collected it can't be used in the widgets/dashboards.

What if there are no hosts/no Vms in the engine?

Kibana only works with existing fields in the indexes.
If the field is not in the index you will not be able to import the widgets using it and they will have an error in the dashboard for the specific missing widget.

tried with production engine, ~8 hosts, few hundreds of VMs

Error: Could not locate that index-pattern-field (id: ovirt.engine_fqdn.raw)

Please schedule a meeting with me and I can show you this issue, if you require some additional logs please let me know which ones.

Verified after consultation with DEV on BRQ production environment

Version: ovirt-engine-metrics-1.1.4.2-1.el7ev

Needed to rerun playbook at least with --scope-engine

This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.