You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, KCIDB's Grafana is deployed to the staging host, and is doing just fine.
We're using an old Grafana version, because our data is public anyway (so not much security risk there), and because we're using a custom panel we implemented hacked together to support some of the features we need. Judging by the state of Grafana's API at the moment, we will likely need some work to port it to a new version.
At the moment Grafana is using the Google BigQuery datasource, and we might continue using that, but we would also like to try using PostgreSQL instead. The latter might be faster for smaller data sizes, improving user experience, and the price of using it grows much slower with the number of users.
It would be good to deploy Grafana to Google Cloud, because it's where the rest of KCIDB is, and because it could save us some maintenance effort and improve monitoring.
Here are the steps we could follow:
Deploy the current version of Grafana to Google Cloud. Preferably in a way, which would let us deploy it somewhere else if we choose (e.g. using a Docker container). The datasource would need to be created manually, as described in the README.md, and the dashboards will need to be loaded by hand as well.
Upgrade the Grafana to a latest stable version, in a separate branch for the start (since we might have a problem with the custom panel), so we could deploy it officially, once we're ready.
At a convenient point in the above plan, see if we could automate deployment of the dashboards as well (the current dashboards are kept up to date in the above-linked repository). Best way would be using a tool which would let us generate the dashboards programmatically, including the SQL queries, as there are a lot of repetitions and copy-paste between various panels and dashboards. There are multiple tools and ways available to do that, it seems.
At any point in the above plan, see if we could automate deployment of changes to Grafana deployment parameters and dashboards from a GitHub repository.
The text was updated successfully, but these errors were encountered:
Currently, KCIDB's Grafana is deployed to the staging host, and is doing just fine.
We're using an old Grafana version, because our data is public anyway (so not much security risk there), and because we're using a custom panel we
implementedhacked together to support some of the features we need. Judging by the state of Grafana's API at the moment, we will likely need some work to port it to a new version.At the moment Grafana is using the Google BigQuery datasource, and we might continue using that, but we would also like to try using PostgreSQL instead. The latter might be faster for smaller data sizes, improving user experience, and the price of using it grows much slower with the number of users.
It would be good to deploy Grafana to Google Cloud, because it's where the rest of KCIDB is, and because it could save us some maintenance effort and improve monitoring.
Here are the steps we could follow:
At a convenient point in the above plan, see if we could automate deployment of the dashboards as well (the current dashboards are kept up to date in the above-linked repository). Best way would be using a tool which would let us generate the dashboards programmatically, including the SQL queries, as there are a lot of repetitions and copy-paste between various panels and dashboards. There are multiple tools and ways available to do that, it seems.
At any point in the above plan, see if we could automate deployment of changes to Grafana deployment parameters and dashboards from a GitHub repository.
The text was updated successfully, but these errors were encountered: