From f5b8428d02ca2f188a9701557a966bbc8c9571e1 Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Thu, 15 Jan 2026 09:47:42 +0000 Subject: [PATCH 1/5] getting-started: update local.mdx Bump the macOS manual installation example to download the 0.6.14 docker-compose release archive, matching the requested release version. --- getting-started/deployment/local.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/getting-started/deployment/local.mdx b/getting-started/deployment/local.mdx index b26a583..e7ab832 100644 --- a/getting-started/deployment/local.mdx +++ b/getting-started/deployment/local.mdx @@ -29,8 +29,8 @@ If you can't use the autoinstall script, follow the manual installation steps fo 2. Open a new terminal window and run the following command to create a folder and download the OpenOps release files: ```shell mkdir -p openops && cd openops && \ - curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.13/openops-dc-0.6.13.zip && \ - unzip openops-dc-0.6.13.zip && cp -n .env.defaults .env + curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.14/openops-dc-0.6.14.zip && \ + unzip openops-dc-0.6.14.zip && cp -n .env.defaults .env ``` 3. 4. Pull the images and run `docker compose`: From fa435903434abe93f7e6bf9354e77e68e4d22d40 Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Thu, 15 Jan 2026 09:47:50 +0000 Subject: [PATCH 2/5] getting-started: update local.mdx Bump the Ubuntu Server manual installation example to download the 0.6.14 docker-compose release archive, matching the requested release version. --- getting-started/deployment/local.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/getting-started/deployment/local.mdx b/getting-started/deployment/local.mdx index e7ab832..e777cdb 100644 --- a/getting-started/deployment/local.mdx +++ b/getting-started/deployment/local.mdx @@ -54,7 +54,7 @@ You can now access the application by navigating to http://localhost. # create and change directory mkdir -p openops && cd openops # download the release file - curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.13/openops-dc-0.6.13.zip + curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.14/openops-dc-0.6.14.zip # refresh package lists sudo apt update # install unzip From 525aa9fac6742bbeae9ac7fda8ee327a7eaa8774 Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Thu, 15 Jan 2026 09:48:01 +0000 Subject: [PATCH 3/5] getting-started: update local.mdx Bump the Windows manual installation example to download and expand the 0.6.14 docker-compose release archive, matching the requested release version. --- getting-started/deployment/local.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/getting-started/deployment/local.mdx b/getting-started/deployment/local.mdx index e777cdb..07a4701 100644 --- a/getting-started/deployment/local.mdx +++ b/getting-started/deployment/local.mdx @@ -99,8 +99,8 @@ You can now access the application by navigating to http://localhost. ``` 3. Download the OpenOps release files: ```powershell - Invoke-WebRequest -Uri "https://github.com/openops-cloud/openops/releases/download/0.6.13/openops-dc-0.6.13.zip" - Expand-Archive -Path "openops-dc-0.6.13.zip" -DestinationPath . + Invoke-WebRequest -Uri "https://github.com/openops-cloud/openops/releases/download/0.6.14/openops-dc-0.6.14.zip" + Expand-Archive -Path "openops-dc-0.6.14.zip" -DestinationPath . if (-Not (Test-Path ".env")) { Copy-Item ".env.defaults" ".env" } From 722d57a294588c1eedde419db403ed1fec0ee833 Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Thu, 15 Jan 2026 09:48:42 +0000 Subject: [PATCH 4/5] reporting-analytics: update analytics.mdx Add a concise prerequisites section to clarify that Analytics availability depends on instance configuration (public/private URLs) and user permissions, aligning with backend changes that allow running without analytics and that gate analytics access. --- reporting-analytics/analytics.mdx | 64 +++++++++++++++++++++++++++++++ 1 file changed, 64 insertions(+) diff --git a/reporting-analytics/analytics.mdx b/reporting-analytics/analytics.mdx index f7e1b16..dbefbe3 100644 --- a/reporting-analytics/analytics.mdx +++ b/reporting-analytics/analytics.mdx @@ -11,6 +11,11 @@ You can visualize data that you collect with [OpenOps tables](/reporting-analyti In addition to OpenOps tables, OpenOps Analytics can connect to and visualize your existing data sources, such as CSV files, Google Sheets, Postgres databases, and more. +## Prerequisites + +* OpenOps Analytics must be enabled and reachable from the OpenOps application (for example, via `OPS_ANALYTICS_PUBLIC_URL` and `OPS_ANALYTICS_PRIVATE_URL` in your `.env` file). +* Your OpenOps user must have permission to access Analytics in your OpenOps instance. + ## Analytics admin portal To configure data visualizations, click **Analytics** on the main navigation bar in OpenOps. When the **Analytics** view opens, click **Admin Panel** to proceed to the Analytics admin portal that is separate from the main OpenOps application. @@ -71,3 +76,62 @@ To upload CSV files into your database, click **+** in the top right corner, the You can now build charts based on the data from your external data source, similar to how you do it with OpenOps tables. When you add charts to the **FinOps** dashboard, they become available in the **Analytics** view in OpenOps. + +To configure data visualizations, click **Analytics** on the main navigation bar in OpenOps. When the **Analytics** view opens, click **Admin Panel** to proceed to the Analytics admin portal that is separate from the main OpenOps application. + +To sign in to the Analytics portal, use `admin` as the username and the password defined with the `OPS_ANALYTICS_ADMIN_PASSWORD` variable in the `.env` file in your OpenOps installation folder. (If you haven’t changed the password, the default is `please-change-this-password-1`.) + + +If you don't have access to the OpenOps installation folder: +* Contact your OpenOps instance administrator if you're using a self-managed OpenOps instance. +* [Contact OpenOps support](mailto:support@openops.com) if you're using an OpenOps-hosted instance. + + +Once you log in, you can see a built-in dashboard called **FinOps**. Modifying this dashboard will affect the **Analytics** tab in OpenOps. + +![Built-in dashboards in the analytics portal](/images/analytics-builtin-dashboards.png) + +Behind every OpenOps table, there is a Postgres database view that can be used to build charts and queries. + +When a new table is created in [OpenOps tables](/reporting-analytics/tables/), the system automatically creates a new database view with the naming convention _table name \_ table id \_ userfriendly_. You can use this view to create dashboards in OpenOps, as well as connect it to other BI systems. + +## Building new charts + +To configure a new chart based on an OpenOps table to display in the **Analytics** view in OpenOps, do the following: + +1. Navigate to **Datasets** and click **+ Dataset**: + ![Creating a dataset](/images/analytics-create-dataset.png) +2. Select `openops_tables_connection` for **Database** and `public` for **Schema**. In the **Table** dropdown, select a Postgres DB view corresponding to the OpenOps table you want to source data from. For example, here is what a view may be named for the *Opportunities* table: + +3. Click **Create dataset and create chart**. +4. In the **Create a new chart** view, select a chart type, then click **Create new chart**: + ![Selecting a chart type](/images/analytics-select-chart-type.png) +5. Configure your chart. Refer to [this Superset documentation page](https://superset.apache.org/docs/using-superset/creating-your-first-dashboard#creating-charts-in-explore-view) if you need help. To preview the configured chart, click **Create chart** in the right pane. + ![Chart preview](/images/analytics-chart-preview.png) +6. If you make further changes to the chart, click **Update chart** to refresh the preview. +7. When you're done, click **Save**. In the **Save chart** dialog, select **FinOps** in the **Add to dashboard** dropdown: + +8. Click **Save**. When you go back to the **Analytics** view in OpenOps, you can see that the chart is now displayed there: + ![Chart in OpenOps Analytics](/images/analytics-chart-in-openops.png) + +For more information on how to create charts, see the [Superset documentation](https://superset.apache.org/docs/intro/). + +## Connecting to external data sources + +Here's what you can do to connect OpenOps Analytics to external data sources such as CSV files: + +1. In the Analytics admin portal, in the top right corner, click **Settings**, then **Database Connections**. + +2. Click **+ Database** to connect to an external data source, such as your own Postgres instance or Google Sheets. +3. Once you have created a database connection, if you’d like to upload CSVs to it, click the **Edit** icon for the database connection: + ![Editing a database connection](/images/analytics-edit-db-connection.png) +4. In the popup that displays, go to **Advanced > Security**, scroll down, and enable **Allow file uploads to database**. + +5. Click **Finish**. + +To upload CSV files into your database, click **+** in the top right corner, then select **Data > Upload CSV to database**: + + +You can now build charts based on the data from your external data source, similar to how you do it with OpenOps tables. When you add charts to the **FinOps** dashboard, they become available in the **Analytics** view in OpenOps. + + From 31db5699fb2988227a9ab3969897780dedb066fd Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Thu, 15 Jan 2026 09:51:03 +0000 Subject: [PATCH 5/5] getting-started: update local.mdx Ubuntu Server manual install section references the 0.6.14 download URL but unzips 0.6.13. Update unzip command to match the downloaded 0.6.14 archive. --- getting-started/deployment/local.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/getting-started/deployment/local.mdx b/getting-started/deployment/local.mdx index 07a4701..9c62ac0 100644 --- a/getting-started/deployment/local.mdx +++ b/getting-started/deployment/local.mdx @@ -60,7 +60,7 @@ You can now access the application by navigating to http://localhost. # install unzip sudo apt install unzip # decompress release file - unzip openops-dc-0.6.13.zip + unzip openops-dc-0.6.14.zip # copy the defaults to env without overwriting existing files cp --update=none .env.defaults .env ```