diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index 4861d2e058a20..e9f724fdb2480 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -3523,46 +3523,51 @@ menu: parent: cloud_cost_setup identifier: cloud_cost_saas_cost_integrations weight: 104 + - name: Snowflake + url: cloud_cost_management/setup/saas_costs/?tab=snowflake#setup + parent: cloud_cost_saas_cost_integrations + identifier: cloud_cost_saas_cost_integrations_snowflake + weight: 101 - name: Databricks url: cloud_cost_management/setup/saas_costs/?tab=databricks#setup parent: cloud_cost_saas_cost_integrations identifier: cloud_cost_saas_cost_integrations_databricks - weight: 101 + weight: 102 + - name: OpenAI + url: cloud_cost_management/setup/saas_costs/?tab=openai#setup + parent: cloud_cost_saas_cost_integrations + identifier: cloud_cost_saas_cost_integrations_openai + weight: 103 + - name: GitHub + url: cloud_cost_management/setup/saas_costs/?tab=github#setup + parent: cloud_cost_saas_cost_integrations + identifier: cloud_cost_saas_cost_integrations_github + weight: 104 - name: Confluent Cloud url: cloud_cost_management/setup/saas_costs/?tab=confluentcloud#setup parent: cloud_cost_saas_cost_integrations identifier: cloud_cost_saas_cost_integrations_confluentcloud - weight: 102 + weight: 105 - name: MongoDB url: cloud_cost_management/setup/saas_costs/?tab=mongodb#setup parent: cloud_cost_saas_cost_integrations identifier: cloud_cost_saas_cost_integrations_mongodb - weight: 103 - - name: Snowflake - url: cloud_cost_management/setup/saas_costs/?tab=snowflake#setup - parent: cloud_cost_saas_cost_integrations - identifier: cloud_cost_saas_cost_integrations_snowflake - weight: 104 + weight: 106 - name: Elastic Cloud url: cloud_cost_management/setup/saas_costs/?tab=elasticcloud#setup parent: cloud_cost_saas_cost_integrations identifier: cloud_cost_saas_cost_integrations_elasticcloud - weight: 105 - - name: OpenAI - url: cloud_cost_management/setup/saas_costs/?tab=openai#setup - parent: cloud_cost_saas_cost_integrations - identifier: cloud_cost_saas_cost_integrations_openai - weight: 106 + weight: 107 - name: Fastly url: cloud_cost_management/setup/saas_costs/?tab=fastly#setup parent: cloud_cost_saas_cost_integrations identifier: cloud_cost_saas_cost_integrations_fastly - weight: 107 + weight: 108 - name: Twilio url: cloud_cost_management/setup/saas_costs/?tab=twilio#setup parent: cloud_cost_saas_cost_integrations identifier: cloud_cost_saas_cost_integrations_twilio - weight: 108 + weight: 109 - name: Custom url: cloud_cost_management/setup/custom parent: cloud_cost_setup diff --git a/content/en/cloud_cost_management/setup/saas_costs.md b/content/en/cloud_cost_management/setup/saas_costs.md index e345cb8dbefea..338b5b2dc737f 100644 --- a/content/en/cloud_cost_management/setup/saas_costs.md +++ b/content/en/cloud_cost_management/setup/saas_costs.md @@ -57,55 +57,7 @@ Navigate to [**Cloud Cost** > **Settings**, select **Accounts**][8] and then cli {{< img src="cloud_cost/saas_costs/all_accounts.png" alt="Add your accounts with AWS, Azure, Google Cloud to collect cost data. You can also add your accounts for Fastly, Snowflake, Confluent Cloud, MongoDB, Databricks, OpenAI, Twilio, and GitHub" style="width:100%" >}} {{< tabs >}} -{{% tab "Databricks" %}} - -1. Navigate to the [Databricks integration tile][101] in Datadog and click **Configure**. -2. Enter the workspace name, url, and access token corresponding to your Databricks account. -3. Under the **Select products to set up integration** section, click the toggle for each account to enable Databricks `Cloud Cost Management`. -4. Enter a `System Tables SQL Warehouse ID` corresponding to your Databricks instance's warehouse to query for system table billing data. -5. Click **Save Databricks Workspace**. - -Your Databricks cost data for the past 15 months can be accessed in Cloud Cost Management after 24 hours. To access the available data collected by each SaaS Cost Integration, see the [Data Collected section](#data-collected). - -{{< img src="cloud_cost/saas_costs/databricks_setup_1.png" alt="Integrate with Databricks to collect cost data." style="width:100%" >}} - -[101]: https://app.datadoghq.com/integrations/databricks - -{{% /tab %}} -{{% tab "Confluent Cloud" %}} - -1. Create or acquire an API key with the [billing admin][102] role in Confluent Cloud. -2. Navigate to the [Confluent Cloud integration tile][101] in Datadog and click **Add Account**. -3. Enter your Confluent Cloud account name, API key, API secret, and optionally, specify tags. -4. Under the **Resources** section, click the toggle for `Collect cost data to view in Cloud Cost Management`. -5. Click **Save**. - -Your Confluent Cloud cost data becomes available in Cloud Cost Management 24 hours after setup. This data automatically includes 12 months of history, the maximum provided by the Confluent billing API. Over the next three months, the data gradually expands to cover 15 months of history. To access the available data collected by each SaaS Cost Integration, see the [Data Collected section](#data-collected). - -If you wish to collect cluster-level tags or business metadata tags for your costs, you can add a Schema Registry API key and secret. Please look into [Schema Management on Confluent Cloud][103] for more information. -{{< img src="cloud_cost/saas_costs/confluent_setup_1.png" alt="Integrate with Confluent to collect cost data." style="width:100%" >}} - -[101]: https://app.datadoghq.com/integrations/confluent-cloud -[102]: https://docs.confluent.io/cloud/current/security/access-control/rbac/predefined-rbac-roles.html#billingadmin-role -[103]: https://docs.confluent.io/cloud/current/get-started/schema-registry.html#quick-start-for-schema-management-on-ccloud - -{{% /tab %}} -{{% tab "MongoDB" %}} - -1. [Create an API token][101] in MongoDB with `Organizational Billing Viewer` permissions, and add `Organizational Read Only` permissions for cluster resource tags. -2. Navigate to the [MongoDB Cost Management integration tile][102] in Datadog and click **Add New**. -3. Enter your MongoDB account name, public key, private key, organizational ID, and optionally, specify tags. -4. Click **Save**. - -Your MongoDB cost data for the past 15 months can be accessed in Cloud Cost Management after 24 hours. To access the available data collected by each SaaS Cost Integration, see the [Data Collected section](#data-collected). - -{{< img src="cloud_cost/saas_costs/mongodb_setup.png" alt="Integrate with MongoDB to collect cost data." style="width:100%" >}} - -[101]: https://www.mongodb.com/docs/cloud-manager/reference/user-roles/#organization-roles -[102]: https://app.datadoghq.com/integrations/mongodb-cost-management - -{{% /tab %}} {{% tab "Snowflake" %}} 1. Navigate to the [Snowflake integration tile][101] in Datadog and click **Add Snowflake Account**. @@ -193,27 +145,23 @@ Notes: {{% /tab %}} +{{% tab "Databricks" %}} -{{% tab "Elastic Cloud" %}} - -1. Go to the [API Key][102] section in your Elastic Cloud organization's settings. -2. Click **Create New Key**. -3. Choose a **Name** and **Expiration Date** for your API key. -4. Select the **Billing Admin** role. -5. Click **Create Key** to generate the key. -6. Go to the [Elastic Cloud integration tile][101] in Datadog -7. Click **Add Account**. -8. Enter your **Elastic Cloud Organization ID** and **Billing API Key** in the account table. +1. Navigate to the [Databricks integration tile][101] in Datadog and click **Configure**. +2. Enter the workspace name, url, and access token corresponding to your Databricks account. +3. Under the **Select products to set up integration** section, click the toggle for each account to enable Databricks `Cloud Cost Management`. +4. Enter a `System Tables SQL Warehouse ID` corresponding to your Databricks instance's warehouse to query for system table billing data. +5. Click **Save Databricks Workspace**. -Your Elastic Cloud cost data for the past 15 months can be accessed in Cloud Cost Management after 24 hours. To access the available data collected by each SaaS Cost Integration, see the [Data Collected section](#data-collected). +Your Databricks cost data for the past 15 months can be accessed in Cloud Cost Management after 24 hours. To access the available data collected by each SaaS Cost Integration, see the [Data Collected section](#data-collected). -{{< img src="cloud_cost/saas_costs/elasticcloud_setup.png" alt="Integrate with Elastic Cloud to collect cost data." style="width:100%" >}} +{{< img src="cloud_cost/saas_costs/databricks_setup_1.png" alt="Integrate with Databricks to collect cost data." style="width:100%" >}} -[101]: https://app.datadoghq.com/integrations/elastic-cloud-ccm -[102]: https://cloud.elastic.co/account/keys +[101]: https://app.datadoghq.com/integrations/databricks {{% /tab %}} + {{% tab "OpenAI" %}} 1. Create a [project API key][101] or [admin API key][103] in your account settings in OpenAI. Make sure the key has read access to the Usage and Management API scopes. @@ -231,6 +179,79 @@ Your OpenAI cost data for the past 15 months can be accessed in Cloud Cost Manag [103]: https://platform.openai.com/docs/api-reference/admin-api-keys {{% /tab %}} + +{{% tab "GitHub" %}} + +1. Create a personal authorization token (classic), with the `manage_billing:enterprise` and `repo` scopes on the [Personal Access Tokens][109] page in GitHub. +2. Navigate to the Datadog [GitHub Costs tile][108]. +3. Click **Add New**. +4. Enter an account name, your personal access token, and your enterprise name (in `enterprise-name` format), as well as any appropriate tags. +5. Click the checkmark button to save this account. + +Your GitHub cost data for the past 15 months can be accessed in Cloud Cost Management within 24 hours. To access the available data collected by each SaaS Cost Integration, see the [Data Collected section](#data-collected). + +{{< img src="cloud_cost/saas_costs/github_setup.png" alt="Integrate with GitHub to collect cost data." style="width:100%" >}} + +[108]: https://app.datadoghq.com/integrations/github-costs +[109]: https://github.com/settings/tokens + +{{% /tab %}} + +{{% tab "Confluent Cloud" %}} + +1. Create or acquire an API key with the [billing admin][102] role in Confluent Cloud. +2. Navigate to the [Confluent Cloud integration tile][101] in Datadog and click **Add Account**. +3. Enter your Confluent Cloud account name, API key, API secret, and optionally, specify tags. +4. Under the **Resources** section, click the toggle for `Collect cost data to view in Cloud Cost Management`. +5. Click **Save**. + +Your Confluent Cloud cost data becomes available in Cloud Cost Management 24 hours after setup. This data automatically includes 12 months of history, the maximum provided by the Confluent billing API. Over the next three months, the data gradually expands to cover 15 months of history. To access the available data collected by each SaaS Cost Integration, see the [Data Collected section](#data-collected). + +If you wish to collect cluster-level tags or business metadata tags for your costs, you can add a Schema Registry API key and secret. Please look into [Schema Management on Confluent Cloud][103] for more information. + +{{< img src="cloud_cost/saas_costs/confluent_setup_1.png" alt="Integrate with Confluent to collect cost data." style="width:100%" >}} + +[101]: https://app.datadoghq.com/integrations/confluent-cloud +[102]: https://docs.confluent.io/cloud/current/security/access-control/rbac/predefined-rbac-roles.html#billingadmin-role +[103]: https://docs.confluent.io/cloud/current/get-started/schema-registry.html#quick-start-for-schema-management-on-ccloud + +{{% /tab %}} +{{% tab "MongoDB" %}} + +1. [Create an API token][101] in MongoDB with `Organizational Billing Viewer` permissions, and add `Organizational Read Only` permissions for cluster resource tags. +2. Navigate to the [MongoDB Cost Management integration tile][102] in Datadog and click **Add New**. +3. Enter your MongoDB account name, public key, private key, organizational ID, and optionally, specify tags. +4. Click **Save**. + +Your MongoDB cost data for the past 15 months can be accessed in Cloud Cost Management after 24 hours. To access the available data collected by each SaaS Cost Integration, see the [Data Collected section](#data-collected). + +{{< img src="cloud_cost/saas_costs/mongodb_setup.png" alt="Integrate with MongoDB to collect cost data." style="width:100%" >}} + +[101]: https://www.mongodb.com/docs/cloud-manager/reference/user-roles/#organization-roles +[102]: https://app.datadoghq.com/integrations/mongodb-cost-management + +{{% /tab %}} + +{{% tab "Elastic Cloud" %}} + +1. Go to the [API Key][102] section in your Elastic Cloud organization's settings. +2. Click **Create New Key**. +3. Choose a **Name** and **Expiration Date** for your API key. +4. Select the **Billing Admin** role. +5. Click **Create Key** to generate the key. +6. Go to the [Elastic Cloud integration tile][101] in Datadog +7. Click **Add Account**. +8. Enter your **Elastic Cloud Organization ID** and **Billing API Key** in the account table. + +Your Elastic Cloud cost data for the past 15 months can be accessed in Cloud Cost Management after 24 hours. To access the available data collected by each SaaS Cost Integration, see the [Data Collected section](#data-collected). + +{{< img src="cloud_cost/saas_costs/elasticcloud_setup.png" alt="Integrate with Elastic Cloud to collect cost data." style="width:100%" >}} + +[101]: https://app.datadoghq.com/integrations/elastic-cloud-ccm +[102]: https://cloud.elastic.co/account/keys + +{{% /tab %}} + {{% tab "Fastly" %}} 1. Create an API token with at least the `"global:read"` scope and `"Billing"` role on the [Personal API tokens][101] page in Fastly. @@ -259,22 +280,6 @@ Your Twilio cost data for the past 15 months can be accessed in Cloud Cost Manag [101]: https://app.datadoghq.com/integrations/twilio -{{% /tab %}} -{{% tab "GitHub" %}} - -1. Create a personal authorization token (classic), with the `manage_billing:enterprise` and `repo` scopes on the [Personal Access Tokens][109] page in GitHub. -2. Navigate to the Datadog [GitHub Costs tile][108]. -3. Click **Add New**. -4. Enter an account name, your personal access token, and your enterprise name (in `enterprise-name` format), as well as any appropriate tags. -5. Click the checkmark button to save this account. - -Your GitHub cost data for the past 15 months can be accessed in Cloud Cost Management within 24 hours. To access the available data collected by each SaaS Cost Integration, see the [Data Collected section](#data-collected). - -{{< img src="cloud_cost/saas_costs/github_setup.png" alt="Integrate with GitHub to collect cost data." style="width:100%" >}} - -[108]: https://app.datadoghq.com/integrations/github-costs -[109]: https://github.com/settings/tokens - {{% /tab %}} {{< /tabs >}} @@ -285,6 +290,30 @@ You can view cost data on the [**Cloud Cost Explorer** page][3], the [Cloud Cost The following table contains a non-exhaustive list of out-of-the-box tags associated with each SaaS Cost integration. {{< tabs >}} +{{% tab "Snowflake" %}} + +| Tag Name | Tag Description | +|---|---| +| `account_locator` | Locator for the account where the usage was consumed. | +| `account_name` | Name of the account where the usage was consumed. | +| `balance_source` | Source of the funds used to pay for the daily usage. The source can be one of the following:
- **capacity**: Usage paid with credits remaining on an organization's capacity commitment.
- **rollover**: Usage paid with rollover credits. When an organization renews a capacity commitment, unused credits are added to the balance of the new contract as rollover credits.
- **free usage**: Usage covered by the free credits provided to the organization.
- **overage**: Usage that was paid at on-demand pricing, which occurs when an organization has exhausted its capacity, rollover, and free credits.
- **rebate**: Usage covered by the credits awarded to the organization when it shared data with another organization. | +| `billing_type` | Indicates what is being charged or credited. Possible billing types include:
- **consumption**: Usage associated with compute credits, storage costs, and data transfer costs.
- **rebate**: Usage covered by the credits awarded to the organization when it shared data with another organization.
- **priority support**: Charges for priority support services. This charge is associated with a stipulation in a contract, not with an account.
- **vps_deployment_fee**: Charges for a Virtual Private Snowflake deployment.
- **support_credit**: Snowflake Support credited the account to reverse charges attributed to an issue in Snowflake. | +| `charge_description` | A description of the cost type associated with distinct line items. Descriptions differ for each cost type, represented by the `servicename` tag. | +| `contract_number` | Snowflake contract number for the organization. | +| `database_name` | Name of the database in which the query was executed (if applicable). Only found for **query attribution** costs. | +| `organization_name` | Name of the organization. | +| `query_hash` | Unique hash representing a parameterized version of the query for attribution purposes. Only found for **query attribution** costs. | +| `query_hash_version` | Version of the Snowflake query hash algorithm used to generate `query_hash`. Only found for **query attribution** costs. | +| `rating_type` | Indicates how the usage in the record is rated, or priced. Possible values include:
- **compute**
- **data_transfer**
- **storage**
- **Other** | +| `region` | Name of the region where the account is located. | +| `service_level` | Service level (edition) of the Snowflake account (Standard, Enterprise, or Business Critical). | +| `servicename` | Type of usage. Possible service types include:
- **automatic_clustering**: Refer to Automatic Clustering.
- **data_transfer**: Refer to Understanding data transfer cost.
- **logging**: Refer to Logging and Tracing Overview.
- **materialized_view**: Refer to Working with Materialized Views.
- **replication**: Refer to Introduction to replication and failover across multiple accounts.
- **query_acceleration**: Refer to Using the Query Acceleration Service.
- **search_optimization**: Refer to Search Optimization Service.
- **serverless_task**: Refer to Introduction to tasks.
- **snowpipe**: Refer to Snowpipe.
- **snowpipe_streaming**: Refer to Snowpipe Streaming.
- **storage**: Refer to Understanding storage cost.
- **warehouse_metering_query_attribution**: Refer to Virtual warehouse credit usage of queries with an execution time of 100ms or greater. Does not indicate usage of serverless or cloud services compute. **warehouse_metering_query_attribution**: Refer to Virtual warehouse credit usage of queries with execution time of 100ms or less, as well as idle warehouse time. Does not indicate usage of serverless or cloud services compute. | +| `user_name` | Name of the user or service account associated with the query. | +| `warehouse_id` | Identifier for the warehouse generating the cost. | +| `warehouse_name` | Name of the warehouse associated with this usage. | +| `warehouse_size` | Size of the warehouse (for example, Large, Medium). | + +{{% /tab %}} {{% tab "Databricks" %}} **Note**: The Databricks cost integration calculates costs using list prices and usage data. It does not reflect any negotiated or discounted rates. @@ -327,6 +356,35 @@ The following table contains a non-exhaustive list of out-of-the-box tags associ | `workspace_id` | ID of the Workspace this usage was associated with. | {{% /tab %}} + +{{% tab "OpenAI" %}} + +| Tag Name | Tag Description | +|---|---| +| `charge_description` | The name of the model whose costs are associated with the charge. | +| `organization_id` | The unique identifier of the organization. | +| `organization_name` | The name of the organization. | +| `project_id` | The unique identifier of the project. | +| `project_name` | The name of the project. | + +{{% /tab %}} + +{{% tab "GitHub" %}} + +**Note**: The GitHub cost integration estimates costs based on list prices and usage data, and includes discount values when available. It does not account for any negotiated rates. + +| Tag Name | Tag Description | +|---|---| +| `enterprise_name` | Alphanumeric string identifying the GitHub enterprise account. | +| `charge_description` | The description of the charge. | +| `product` | The product of usage, for example "actions" or "storage". | +| `organization_name` | The GitHub organization. | +| `repository_name` | The GitHub repository. | +| `billing_currency` | The billing currency, for example "USD". | +| `discount` | If the cost item is a discount. | + +{{% /tab %}} + {{% tab "Confluent Cloud" %}} | Tag Name | Tag Description | @@ -339,30 +397,7 @@ The following table contains a non-exhaustive list of out-of-the-box tags associ | `resource_name` | The name of the Confluent resource. | {{% /tab %}} -{{% tab "Snowflake" %}} - -| Tag Name | Tag Description | -|---|---| -| `account_locator` | Locator for the account where the usage was consumed. | -| `account_name` | Name of the account where the usage was consumed. | -| `balance_source` | Source of the funds used to pay for the daily usage. The source can be one of the following:
- **capacity**: Usage paid with credits remaining on an organization's capacity commitment.
- **rollover**: Usage paid with rollover credits. When an organization renews a capacity commitment, unused credits are added to the balance of the new contract as rollover credits.
- **free usage**: Usage covered by the free credits provided to the organization.
- **overage**: Usage that was paid at on-demand pricing, which occurs when an organization has exhausted its capacity, rollover, and free credits.
- **rebate**: Usage covered by the credits awarded to the organization when it shared data with another organization. | -| `billing_type` | Indicates what is being charged or credited. Possible billing types include:
- **consumption**: Usage associated with compute credits, storage costs, and data transfer costs.
- **rebate**: Usage covered by the credits awarded to the organization when it shared data with another organization.
- **priority support**: Charges for priority support services. This charge is associated with a stipulation in a contract, not with an account.
- **vps_deployment_fee**: Charges for a Virtual Private Snowflake deployment.
- **support_credit**: Snowflake Support credited the account to reverse charges attributed to an issue in Snowflake. | -| `charge_description` | A description of the cost type associated with distinct line items. Descriptions differ for each cost type, represented by the `servicename` tag. | -| `contract_number` | Snowflake contract number for the organization. | -| `database_name` | Name of the database in which the query was executed (if applicable). Only found for **query attribution** costs. | -| `organization_name` | Name of the organization. | -| `query_hash` | Unique hash representing a parameterized version of the query for attribution purposes. Only found for **query attribution** costs. | -| `query_hash_version` | Version of the Snowflake query hash algorithm used to generate `query_hash`. Only found for **query attribution** costs. | -| `rating_type` | Indicates how the usage in the record is rated, or priced. Possible values include:
- **compute**
- **data_transfer**
- **storage**
- **Other** | -| `region` | Name of the region where the account is located. | -| `service_level` | Service level (edition) of the Snowflake account (Standard, Enterprise, or Business Critical). | -| `servicename` | Type of usage. Possible service types include:
- **automatic_clustering**: Refer to Automatic Clustering.
- **data_transfer**: Refer to Understanding data transfer cost.
- **logging**: Refer to Logging and Tracing Overview.
- **materialized_view**: Refer to Working with Materialized Views.
- **replication**: Refer to Introduction to replication and failover across multiple accounts.
- **query_acceleration**: Refer to Using the Query Acceleration Service.
- **search_optimization**: Refer to Search Optimization Service.
- **serverless_task**: Refer to Introduction to tasks.
- **snowpipe**: Refer to Snowpipe.
- **snowpipe_streaming**: Refer to Snowpipe Streaming.
- **storage**: Refer to Understanding storage cost.
- **warehouse_metering_query_attribution**: Refer to Virtual warehouse credit usage of queries with an execution time of 100ms or greater. Does not indicate usage of serverless or cloud services compute. **warehouse_metering_query_attribution**: Refer to Virtual warehouse credit usage of queries with execution time of 100ms or less, as well as idle warehouse time. Does not indicate usage of serverless or cloud services compute. | -| `user_name` | Name of the user or service account associated with the query. | -| `warehouse_id` | Identifier for the warehouse generating the cost. | -| `warehouse_name` | Name of the warehouse associated with this usage. | -| `warehouse_size` | Size of the warehouse (for example, Large, Medium). | -{{% /tab %}} {{% tab "Elastic Cloud" %}} | Tag Name | Tag Description | |---|--- @@ -386,17 +421,7 @@ The following table contains a non-exhaustive list of out-of-the-box tags associ | `status` | State of the payment. | {{% /tab %}} -{{% tab "OpenAI" %}} -| Tag Name | Tag Description | -|---|---| -| `charge_description` | The name of the model whose costs are associated with the charge. | -| `organization_id` | The unique identifier of the organization. | -| `organization_name` | The name of the organization. | -| `project_id` | The unique identifier of the project. | -| `project_name` | The name of the project. | - -{{% /tab %}} {{% tab "Fastly" %}} | Tag Name | Tag Description | @@ -425,25 +450,6 @@ The following table contains a non-exhaustive list of out-of-the-box tags associ [101]: https://www.twilio.com/docs/usage/api/usage-record#usage-categories -{{% /tab %}} - - -{{% tab "GitHub" %}} - -**Note**: The GitHub cost integration estimates costs based on list prices and usage data, and includes discount values when available. It does not account for any negotiated rates. - - -| Tag Name | Tag Description | -|---|---| -| `enterprise_name` | Alphanumeric string identifying the GitHub enterprise account. | -| `charge_description` | The description of the charge. | -| `product` | The product of usage, for example "actions" or "storage". | -| `organization_name` | The GitHub organization. | -| `repository_name` | The GitHub repository. | -| `billing_currency` | The billing currency, for example "USD". | -| `discount` | If the cost item is a discount. | - - {{% /tab %}} {{< /tabs >}} diff --git a/layouts/partials/cloud_cost/cost-integrations.html b/layouts/partials/cloud_cost/cost-integrations.html index 288bb7a55c6db..12221d768184b 100644 --- a/layouts/partials/cloud_cost/cost-integrations.html +++ b/layouts/partials/cloud_cost/cost-integrations.html @@ -1,14 +1,14 @@ {{ $root := . }} {{ $saas_cost_integrations := slice + (dict "name" "snowflake" "href" "/cloud_cost_management/saas_costs/?tab=snowflake#configure-your-saas-accounts" "src" "integrations_logos/snowflake_small.svg") (dict "name" "databricks" "href" "/cloud_cost_management/saas_costs/?tab=databricks#configure-your-saas-accounts" "src" "integrations_logos/databricks_small.svg") + (dict "name" "openai" "href" "/cloud_cost_management/saas_costs/?tab=openai#configure-your-saas-accounts" "src" "integrations_logos/openai_small.svg") + (dict "name" "github" "href" "/cloud_cost_management/saas_costs/?tab=github#configure-your-saas-accounts" "src" "integrations_logos/github_small.svg") (dict "name" "confluent cloud" "href" "/cloud_cost_management/saas_costs/?tab=confluentcloud#configure-your-saas-accounts" "src" "integrations_logos/confluent-cloud_small.svg") (dict "name" "mongodb" "href" "/cloud_cost_management/saas_costs/?tab=mongodb#configure-your-saas-accounts" "src" "integrations_logos/mongodb_small.svg") - (dict "name" "snowflake" "href" "/cloud_cost_management/saas_costs/?tab=snowflake#configure-your-saas-accounts" "src" "integrations_logos/snowflake_small.svg") (dict "name" "elastic cloud" "href" "/cloud_cost_management/saas_costs/?tab=elasticcloud#configure-your-saas-accounts" "src" "integrations_logos/elastic-cloud_small.svg") - (dict "name" "openai" "href" "/cloud_cost_management/saas_costs/?tab=openai#configure-your-saas-accounts" "src" "integrations_logos/openai_small.svg") (dict "name" "fastly" "href" "/cloud_cost_management/saas_costs/?tab=fastly#configure-your-saas-accounts" "src" "integrations_logos/fastly_small.svg") (dict "name" "twilio" "href" "/cloud_cost_management/saas_costs/?tab=twilio#configure-your-saas-accounts" "src" "integrations_logos/twilio_small.svg") - (dict "name" "github" "href" "/cloud_cost_management/saas_costs/?tab=github#configure-your-saas-accounts" "src" "integrations_logos/github_small.svg") }}
@@ -26,7 +26,19 @@

- {{ range (last 4 $saas_cost_integrations) }} + {{ range first 4 (after 4 $saas_cost_integrations) }} +
+ +
+ {{ partial "img.html" (dict "root" $root "src" .src "class" "img-fluid" "alt" .name "width" "150") }} +
+ +
+ {{ end }} +
+
+
+ {{ range after 8 $saas_cost_integrations }}