Fiscit Remote Monitoring / Grafana bugs
* Listen_IP config parameter seems to be ignored by the mod
* Datasources are hardcoded which is pretty bad if someone (like me) decides to use dashoards in their own grafana installation. In that case a datasource name and/or ID (which is kinda even worse) mismatch occurs and you must search & replace all the datasource mentions in all the dashboards. A recommended approach is to use variables to select and template the datasource names into PromQL/SQL queries.
* frmcache seems to be misconfigured: there are no PG_* settings, so it cannot connect to the DB, also it cannot use standard pq library envvars to connect automagically. Need to specify
* frmcache seems to be unable to create a database when applying migrations (just for me?), which is easily fixed by adding a
* No dockerfiles, no cache, everything is being compiled on every launch by init scripts instead of only on code update.
And then there are dashboards:
* There are sort of harmless but still annoying errors regarding legacy queries.
* Drop pod dashboard didn't work or displayed only collected pods. AFAIK the error was due to the SQL query case. And it was probably a legacy query thing since I was not able to see the real query in the UI (!) unless I open a Query Inspector or go to the dashboard JSON.
* I've had to modify some queries to make Grafana visualizations and variables work. Unfortunately I don't remember which ones, but there's always the good old 'compare versions' thing. Not all dashboards were checked, but I see a lot of broken stuff (at least half of which was broken by me, no doubt).
P. S. I am willing to submit PRs later.
P. P. S. Yes, this is basically what I do for a living, so please try to forgive me if I'm too hard on authors and contributors
* Datasources are hardcoded which is pretty bad if someone (like me) decides to use dashoards in their own grafana installation. In that case a datasource name and/or ID (which is kinda even worse) mismatch occurs and you must search & replace all the datasource mentions in all the dashboards. A recommended approach is to use variables to select and template the datasource names into PromQL/SQL queries.
* frmcache seems to be misconfigured: there are no PG_* settings, so it cannot connect to the DB, also it cannot use standard pq library envvars to connect automagically. Need to specify
-pghost $PG_HOST -pgport $PG_PORT -pguser $PG_USER -pgpassword $PG_PASSWORD -pgdb $PG_DB args in the init script.* frmcache seems to be unable to create a database when applying migrations (just for me?), which is easily fixed by adding a
POSTGRES_DB envvar to the postgresql service. The missing depends_on is already added though.* No dockerfiles, no cache, everything is being compiled on every launch by init scripts instead of only on code update.
And then there are dashboards:
* There are sort of harmless but still annoying errors regarding legacy queries.
* Drop pod dashboard didn't work or displayed only collected pods. AFAIK the error was due to the SQL query case. And it was probably a legacy query thing since I was not able to see the real query in the UI (!) unless I open a Query Inspector or go to the dashboard JSON.
* I've had to modify some queries to make Grafana visualizations and variables work. Unfortunately I don't remember which ones, but there's always the good old 'compare versions' thing. Not all dashboards were checked, but I see a lot of broken stuff (at least half of which was broken by me, no doubt).
P. S. I am willing to submit PRs later.
P. P. S. Yes, this is basically what I do for a living, so please try to forgive me if I'm too hard on authors and contributors
