Description of problem: ovirt-engine and ovirt-engine-dwh postgres processes do not support non default db names. If db name are different then "engine" and "ovirt_engine_history" metrics will be empty for the ovirt-engine and ovirt-engine-dwh in the processes plugin. Version-Release number of selected component (if applicable): 4.2 How reproducible: 100% Steps to Reproduce: 1.Change db names 2.Check results in kibana with filter collectd.plugin:processes AND ovirt.entity:engine and split by collectd.plugin_instance 3. Actual results: Values are empty for these metrics. Expected results: Should add support to non default names. Additional info:
I don't believe many customers change the default and this has a clear workaround with a manual edit.
Reproduction steps: 1. Migrate database to another one -> lsvaty 2. change vars in /etc/ovirt-engine/engine.conf.d/10-setup-database.conf ENGINE_DB_HOST="localhost" ENGINE_DB_PORT="5432" ENGINE_DB_USER="engine" ENGINE_DB_PASSWORD="password" ENGINE_DB_DATABASE="lsvaty" ENGINE_DB_SECURED="False" ENGINE_DB_SECURED_VALIDATION="False" ENGINE_DB_DRIVER="org.postgresql.Driver" ENGINE_DB_URL="jdbc:postgresql://localhost:5432/engine?sslfactory=org.postgresql.ssl.NonValidatingFactory" 3. Check if collectd configuration is updated? FAIL -> still the same credentials in: grep -R engine /etc/collectd.d ./20-builtins-conf-for-ovirt-engine.conf: ProcessMatch pg_engine "postgres: engine engine" 4. samples are still reported though -> Shirly why? 5. Rerun metrics configuration to align the configuration 6. Check collectd configuration grep -R engine /etc/collectd.d ./20-builtins-conf-for-ovirt-engine.conf: ProcessMatch pg_engine "postgres: engine lsvaty" samples ps_data are not being recorded by metrics store anymore tested in ovirt-engine-metrics-1.1.2.2-1.el7ev.noarch
I found out my migration of the engine actually broke the engine, thus I would like to reverify this one as of functionality. Moving back to ON_QA However, the metrics configuration script still should be triggered by migration of database. Shirly is there any way to support this? Maybe documentation update on the migration of DB?
verified in ovirt-engine-metrics-1.1.3.3-1.el7ev.noarch on both non-default engine and dwh db names
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 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.