Shirly, can you please update the blog post pointing to an updated documentation page? 2018-05-17 9:35 GMT+02:00 Karli Sjöberg <karli(a)inparadise.se&gt;: > Heya! > > I've been whishing for reports in oVirt ever since the old 'Jasper > Reports' was removed. For an Enterprise, having pretty graphs to look > at is a must. > > Searching the subject, I've found this[*] and have managed to get it > installed OK but having issues trying to follow the guide setting it > up. > > First of all, I think the guide should have at least mentioned that > 'pg_hba.conf' needs to be edited for the read only user to be able to > connect to the database, I scratched my head around that for a while > before I got it. > > When I first type in the query example, I got syntax errors: > 'pq: syntax error at or near "$"'. I continued anyways since I figured > it would be solved at a later point, which turned out to be true, since > the next step is to use the "Templating feature" to add variables. > > Unfortunately this doesn't go so well, even though I followed the > instructions very carefully. After hitting save on the first variable I > am rewarded with the error message: > 'Template variables could not be initialized: pq: column "en_us" does > not exist.' > > Are the queries stated in the guide still correct? This is for > 'user_locale': > "SELECT DISTINCT language_code from enum_translator" > > [*]:https://www.ovirt.org/blog/2018/01/ovirt-report-using-grafana/ > > TIA > /K > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit> _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org

On Thu, 2018-05-17 at 10:37 -0700, Vincent Royer wrote: > These are the same issues I ran into. I did get it working, look up > my post history and you'll find some solutions to the errors Big thanks, now I understand what the problem was! But I must say, after reading that thread, I´m actually more interested in setting up the metrics store as it seems you get way more data out of it without having to access the database directly. The point being, the less manual stuff you do to alter the original setup in the engine, the less issues you are going to have later on, with upgrades and such. /K > > On Thu, May 17, 2018, 1:01 AM Sandro Bonazzola, <sbonazzo(a)redhat.com&gt; > wrote: > > Shirly, can you please update the blog post pointing to an updated > > documentation page? > > > > 2018-05-17 9:35 GMT+02:00 Karli Sjöberg <karli(a)inparadise.se&gt;: > > > Heya! > > > > > > I've been whishing for reports in oVirt ever since the old > > > 'Jasper > > > Reports' was removed. For an Enterprise, having pretty graphs to > > > look > > > at is a must. > > > > > > Searching the subject, I've found this[*] and have managed to get > > > it > > > installed OK but having issues trying to follow the guide setting > > > it > > > up. > > > > > > First of all, I think the guide should have at least mentioned > > > that > > > 'pg_hba.conf' needs to be edited for the read only user to be > > > able to > > > connect to the database, I scratched my head around that for a > > > while > > > before I got it. > > > > > > When I first type in the query example, I got syntax errors: > > > 'pq: syntax error at or near "$"'. I continued anyways since I > > > figured > > > it would be solved at a later point, which turned out to be true, > > > since > > > the next step is to use the "Templating feature" to add > > > variables. > > > > > > Unfortunately this doesn't go so well, even though I followed the > > > instructions very carefully. After hitting save on the first > > > variable I > > > am rewarded with the error message: > > > 'Template variables could not be initialized: pq: column "en_us" > > > does > > > not exist.' > > > > > > Are the queries stated in the guide still correct? This is for > > > 'user_locale': > > > "SELECT DISTINCT language_code from enum_translator" > > > > > > [*]:https://www.ovirt.org/blog/2018/01/ovirt-report-using-grafana > > > / > > > > > > TIA > > > /K > > > _______________________________________________ > > > Users mailing list -- users(a)ovirt.org > > > To unsubscribe send an email to users-leave(a)ovirt.org > > > > > >

Yes I agree, because the database contains so many version specific pointers, all of them will stop working when you upgrade. So that's no good!

If you ever get something decent working with Grafana, I'd be very interested. I'm still not happy with the integration with the engine history database, I was never really able to get predictable output from it, and spent way too many hours messing around with it.

On Thu, May 17, 2018 at 11:21 PM Karli Sjöberg <karli(a)inparadise.se&gt; wrote: > On Thu, 2018-05-17 at 10:37 -0700, Vincent Royer wrote: > > These are the same issues I ran into. I did get it working, look up > > my post history and you'll find some solutions to the errors > > Big thanks, now I understand what the problem was! > > But I must say, after reading that thread, I´m actually more interested > in setting up the metrics store as it seems you get way more data out > of it without having to access the database directly. The point being, > the less manual stuff you do to alter the original setup in the engine, > the less issues you are going to have later on, with upgrades and such. > > /K > > > > > On Thu, May 17, 2018, 1:01 AM Sandro Bonazzola, <sbonazzo(a)redhat.com&gt; > > wrote: > > > Shirly, can you please update the blog post pointing to an updated > > > documentation page? > > > > > > 2018-05-17 9:35 GMT+02:00 Karli Sjöberg <karli(a)inparadise.se&gt;: > > > > Heya! > > > > > > > > I've been whishing for reports in oVirt ever since the old > > > > 'Jasper > > > > Reports' was removed. For an Enterprise, having pretty graphs to > > > > look > > > > at is a must. > > > > > > > > Searching the subject, I've found this[*] and have managed to get > > > > it > > > > installed OK but having issues trying to follow the guide setting > > > > it > > > > up. > > > > > > > > First of all, I think the guide should have at least mentioned > > > > that > > > > 'pg_hba.conf' needs to be edited for the read only user to be > > > > able to > > > > connect to the database, I scratched my head around that for a > > > > while > > > > before I got it. > > > > > > > > When I first type in the query example, I got syntax errors: > > > > 'pq: syntax error at or near "$"'. I continued anyways since I > > > > figured > > > > it would be solved at a later point, which turned out to be true, > > > > since > > > > the next step is to use the "Templating feature" to add > > > > variables. > > > > > > > > Unfortunately this doesn't go so well, even though I followed the > > > > instructions very carefully. After hitting save on the first > > > > variable I > > > > am rewarded with the error message: > > > > 'Template variables could not be initialized: pq: column "en_us" > > > > does > > > > not exist.' > > > > > > > > Are the queries stated in the guide still correct? This is for > > > > 'user_locale': > > > > "SELECT DISTINCT language_code from enum_translator" > > > > > > > > [*]:https://www.ovirt.org/blog/2018/01/ovirt-report-using-grafana > > > > / > > > > > > > > TIA > > > > /K > > > > _______________________________________________ > > > > Users mailing list -- users(a)ovirt.org > > > > To unsubscribe send an email to users-leave(a)ovirt.org > > > > > > > > >

Hi Shirly, I went through your instructions just yesterday and they work but some troubleshooting was needed. This is what I have found: * When adding the graph I also got syntax errors: '*pq: syntax error at or near "$"'*, maybe add an "ignore this error" line to the docs would be an improvement * I am new to grafana then I could not understand about templating. Took me a few *trips* to http://docs.grafana.org/reference/templating/ to understand it. Maybe some simple instructions would make experience better. * Regarding tremplating: cluster_name - fails: SELECT cluster_name FROM v4_2_configuration_history_clusters WHERE datacenter_id = $datacenter_id - not fail: SELECT cluster_name FROM v4_2_configuration_history_clusters WHERE datacenter_id='$datacenter_id' cluster_id - fails: SELECT cluster_id FROM v4_2_configuration_history_clusters WHERE datacenter_id = $datacenter_id - not fail: SELECT cluster_id FROM v4_2_configuration_history_clusters WHERE datacenter_id ='$datacenter_id' there are many more. * Modifying DB, even DWH views are stable I think it would be better to instruct to make backup. Regarding modifying DB, Is it possible to revert these changes? Thanks! On Tue, May 22, 2018 at 6:09 PM, Shirly Radco <sradco(a)redhat.com&gt; wrote: > > > -- > > SHIRLY RADCO > > BI SENIOR SOFTWARE ENGINEER > > Red Hat Israel > > > TRIED. TESTED. TRUSTED. > > > > On Fri, May 18, 2018, 16:02 Vincent Royer <vincent(a)epicenergy.ca&gt; wrote: > >> Yes I agree, because the database contains so many version specific >> pointers, all of them will stop working when you upgrade. So that's no good! >> > > Not sure what you mean. The DWH views are stable and we currently > support 3.6 and above views. It means you do not have to update the version > of the view. > Also DWH is pretty stable. So you should not expect many changes. > > >> If you ever get something decent working with Grafana, I'd be very >> interested. I'm still not happy with the integration with the engine >> history database, I was never really able to get predictable output from >> it, and spent way too many hours messing around with it. >> > > Ill try and add a few more meaningful examples if that will help. > > Is the problem is how to join the tables together? > > >> >> On Thu, May 17, 2018 at 11:21 PM Karli Sjöberg <karli(a)inparadise.se&gt; >> wrote: >> >>> On Thu, 2018-05-17 at 10:37 -0700, Vincent Royer wrote: >>> > These are the same issues I ran into. I did get it working, look up >>> > my post history and you'll find some solutions to the errors >>> >>> Big thanks, now I understand what the problem was! >>> >>> But I must say, after reading that thread, I´m actually more interested >>> in setting up the metrics store as it seems you get way more data out >>> of it without having to access the database directly. The point being, >>> the less manual stuff you do to alter the original setup in the engine, >>> the less issues you are going to have later on, with upgrades and such. >>> >>> /K >>> >>> > >>> > On Thu, May 17, 2018, 1:01 AM Sandro Bonazzola, <sbonazzo(a)redhat.com&gt; >>> > wrote: >>> > > Shirly, can you please update the blog post pointing to an updated >>> > > documentation page? >>> > > >>> > > 2018-05-17 9:35 GMT+02:00 Karli Sjöberg <karli(a)inparadise.se&gt;: >>> > > > Heya! >>> > > > >>> > > > I've been whishing for reports in oVirt ever since the old >>> > > > 'Jasper >>> > > > Reports' was removed. For an Enterprise, having pretty graphs to >>> > > > look >>> > > > at is a must. >>> > > > >>> > > > Searching the subject, I've found this[*] and have managed to get >>> > > > it >>> > > > installed OK but having issues trying to follow the guide setting >>> > > > it >>> > > > up. >>> > > > >>> > > > First of all, I think the guide should have at least mentioned >>> > > > that >>> > > > 'pg_hba.conf' needs to be edited for the read only user to be >>> > > > able to >>> > > > connect to the database, I scratched my head around that for a >>> > > > while >>> > > > before I got it. >>> > > > >>> > > > When I first type in the query example, I got syntax errors: >>> > > > 'pq: syntax error at or near "$"'. I continued anyways since I >>> > > > figured >>> > > > it would be solved at a later point, which turned out to be true, >>> > > > since >>> > > > the next step is to use the "Templating feature" to add >>> > > > variables. >>> > > > >>> > > > Unfortunately this doesn't go so well, even though I followed the >>> > > > instructions very carefully. After hitting save on the first >>> > > > variable I >>> > > > am rewarded with the error message: >>> > > > 'Template variables could not be initialized: pq: column "en_us" >>> > > > does >>> > > > not exist.' >>> > > > >>> > > > Are the queries stated in the guide still correct? This is for >>> > > > 'user_locale': >>> > > > "SELECT DISTINCT language_code from enum_translator" >>> > > > >>> > > > [*]:https://www.ovirt.org/blog/2018/01/ovirt-report-using-grafana >>> > > > / >>> > > > >>> > > > TIA >>> > > > /K >>> > > > _______________________________________________ >>> > > > Users mailing list -- users(a)ovirt.org >>> > > > To unsubscribe send an email to users-leave(a)ovirt.org >>> > > >>> > > >>> > > >> >> > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > >