From 471f18e8035ea00a1d2b12948060af4392be795e Mon Sep 17 00:00:00 2001 From: vansia43 Date: Tue, 22 Oct 2024 12:16:56 +0000 Subject: [PATCH] deploy: e88df95bcfb1b2f1387cee05bc37466d4054c9ea --- 404.html | 4 ++-- active_resources/index.html | 4 ++-- annotations/index.html | 4 ++-- api/index.html | 4 ++-- assets/js/07fcd452.588a9dcf.js | 1 - assets/js/07fcd452.9d68ce82.js | 1 + .../{runtime~main.e1390272.js => runtime~main.6e77adbf.js} | 2 +- autopilot/index.html | 4 ++-- aws_supported_services/index.html | 4 ++-- azure_supported_services/index.html | 4 ++-- budgets/index.html | 4 ++-- changelog/index.html | 4 ++-- connecting_aws/index.html | 4 ++-- connecting_azure/index.html | 4 ++-- connecting_confluent/index.html | 4 ++-- connecting_coralogix/index.html | 4 ++-- connecting_custom_providers/index.html | 4 ++-- connecting_databricks/index.html | 4 ++-- connecting_datadog/index.html | 4 ++-- connecting_fastly/index.html | 4 ++-- connecting_gcp/index.html | 4 ++-- connecting_github/index.html | 4 ++-- connecting_kubernetes/index.html | 4 ++-- connecting_mongodb-atlas/index.html | 4 ++-- connecting_new_relic/index.html | 4 ++-- connecting_open_ai/index.html | 4 ++-- connecting_oracle/index.html | 4 ++-- connecting_planetscale/index.html | 4 ++-- connecting_snowflake/index.html | 4 ++-- cost_anomaly_alerts/index.html | 4 ++-- cost_recommendations/index.html | 4 ++-- cost_reports/index.html | 4 ++-- dashboards/index.html | 4 ++-- data_dictionary/index.html | 4 ++-- enabling_gcp_billing_export/index.html | 4 ++-- executive_reporting/index.html | 4 ++-- financial_commitment_reports/index.html | 4 ++-- folders/index.html | 4 ++-- forecasting/index.html | 4 ++-- gcp_supported_services/index.html | 4 ++-- getting_started/index.html | 4 ++-- hidden_costs/index.html | 4 ++-- index.html | 4 ++-- issues/index.html | 4 ++-- kubernetes/index.html | 4 ++-- kubernetes_agent/index.html | 4 ++-- network_flow_reports/index.html | 4 ++-- overview/index.html | 4 ++-- partners/index.html | 4 ++-- per_unit_costs/index.html | 4 ++-- rbac/index.html | 4 ++-- report_notifications/index.html | 4 ++-- saved_filters/index.html | 4 ++-- savings_planner/index.html | 4 ++-- search/index.html | 4 ++-- security/index.html | 4 ++-- segments/index.html | 4 ++-- snowflake_cost_by_query/index.html | 4 ++-- sso/index.html | 4 ++-- team_accountability/index.html | 4 ++-- terraform/index.html | 4 ++-- usage_based_reporting/index.html | 6 +++--- vantage_account/index.html | 4 ++-- vantage_university/index.html | 4 ++-- vantage_university_account_management/index.html | 4 ++-- vantage_university_budgeting/index.html | 4 ++-- vantage_university_cost_allocation/index.html | 4 ++-- vantage_university_cost_reporting/index.html | 4 ++-- vantage_university_developer/index.html | 4 ++-- vantage_university_finance_manager/index.html | 4 ++-- vantage_university_finops_analyst/index.html | 4 ++-- vantage_university_integrations/index.html | 4 ++-- vantage_university_observability/index.html | 4 ++-- vantage_university_per_resource_costs/index.html | 4 ++-- vantage_university_unit_costs/index.html | 4 ++-- virtual_tagging/index.html | 4 ++-- vql/index.html | 4 ++-- vql_cost_report/index.html | 4 ++-- vql_resource_report/index.html | 4 ++-- workspaces/index.html | 4 ++-- 80 files changed, 157 insertions(+), 157 deletions(-) delete mode 100644 assets/js/07fcd452.588a9dcf.js create mode 100644 assets/js/07fcd452.9d68ce82.js rename assets/js/{runtime~main.e1390272.js => runtime~main.6e77adbf.js} (99%) diff --git a/404.html b/404.html index b650a74e..39ca6bb5 100644 --- a/404.html +++ b/404.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@
Skip to main content

Page Not Found

We could not find what you were looking for.

Please contact the owner of the site that linked you to the original URL and let them know their link is broken.

- + \ No newline at end of file diff --git a/active_resources/index.html b/active_resources/index.html index 8df4ea87..f7277862 100644 --- a/active_resources/index.html +++ b/active_resources/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@
Skip to main content

Resource Reports

For supported providers, Vantage profiles for active resources within your account. An active resource is a resource, such as a virtual machine, that is currently generating costs within a cloud account. This is in contrast to resources that are included in billing but may no longer be live. Examples of active resources include items like Amazon S3 buckets, Azure Load Balancers, Snowflake queries, Confluent clusters, etc.

You can create resource reports to see filtered views of your active resources. These reports provide visibility into all the currently operational resources within your account and the associated costs incurred by each resource. Reports include filterable dimensions, such as account, tag, region, service, and service-specific metadata.

note

Active resource views are currently supported for AWS, Azure, GCP, Kubernetes, Snowflake, MongoDB, Confluent, and PlanetScale.

AWS Active Resources​

Vantage shows only active resources that have an associated IAM role. One common source of confusion is when an organization has only a root/management account with an IAM role. To view active resources from each member account, create an IAM role for each member account. As you create each additional IAM role, the member account's resources are automatically added to the active resource inventory. See the AWS integration documentation for details.

Not every AWS service is supported for resource-level costs; however, most services that incur costs are supported. To see the full list of services for which there are resource-level costs, see the documentation on supported AWS services.

Azure Active Resources​

To see the full list of supported Azure services, see the Azure documentation.

GCP Active Resources​

To see the full list of supported GCP services, see the GCP documentation.

Kubernetes Active Resources​

A Kubernetes managed workload is a higher-level abstraction than a pod that automatically manages pod objects on your behalf. Vantage currently supports Deployments, StatefulSets, DaemonSets, Jobs, CronJobs, and ArgoCD Rollouts and syncs these managed worklods as active resources in your account. When available, pods are grouped by controller, and you can view and filter on the following metadata:

  • Controller name
  • Controller type
  • Cluster
  • Namespace
  • Controller labels

Other Available Active Resources​

The following active resources are available for the additional providers listed below.

ProviderAvailable Active Resources
SnowflakeSnowflake queries
MongoDB AtlasMongoDB Atlas clusters
ConfluentConfluent Kafka clusters
PlanetScalePlanetScale databases

View Active Resources​

note

Active resources are synced for each workspace at least once every 24 hours. Vantage syncs all tags specific to a service.

  1. From the top navigation, click Active Resources.
  2. The Services screen is displayed, which contains each resource by name (e.g., CloudFront Distributions, Azure Databricks Workspaces, etc.), the total number of active resources, and accrued costs for each resource. Select a resource from the parent list to see a list of all resources within that resource group. In the below example, the NAT Gateways resource is selected from the list.
    A sample resource report with a box around the NAT Gateways resource in the list
  3. Select an individual resource from the filtered list.
    A sample resource report with a box around the NAT Gateways resource in the list
  4. The resource is displayed along with a detailed view of its costs over time. In the below image, the selected AWS NAT Gateway resource is displayed, with current and previous costs incurred. Costs for corresponding categories, like Data Transfer, are also provided per resource.
    Resource Report Drill Down

Create a Resource Report​

Create a resource report to filter by specific resources or groups of resources. Create detailed reports, including reports that show:

  • Resources across AWS services that match a certain AWS tag
  • Resources within a specific AWS member account
  • All Amazon EC2 instances that are a certain type, like m5.large
  • All Snowflake queries belonging to a specific label

To create a resource report:

  1. From the top navigation, click Active Resources.
  2. From the left navigation, click Resource Reports. You can create new reports and rename your existing reports from this page. The All Active Resources Report is provided by default.
    A full list of active resources for an account. The resource's label, type, costs, provider, region, and account are listed.
  3. From the top right of the page, click New Report.
  4. From the type right of the resource list, click Filters. The Filters panel is displayed.
    • Select a Provider (e.g., AWS).
    • Click New Rule, then select a filter category, like Region. (See the section below for details on available filter options.)
    • Depending on the filter criteria, select an operator (e.g., is, is not, contains).
    • Select a value (e.g., Region is eu-west-1 ).
    • Click New Rule to add additional criteria to the same filter. Results are displayed where both rule 1 AND rule 2 are true.
    • Click + Add Filter to add a new filter set. Results are displayed where either filter 1 OR filter 2 are true.
    • At the top of the Filters panel, click Apply Changes.
      A resource report filter with sample filter criteria for Snowflake and AWS
  5. At the top of the report, click Save. The report name is displayed in the breadcrumbs above the report. To rename the report, click the pencil icon next to the default report name. Then, update the name and click Save.

Resource Report Filters​

The following filters are available for resource reports.

FilterProviderExamples
AccountAWS, GCPAWS or GCP account name (e.g., production)
Billing AccountAWSAWS billing account name
LabelAll providersThe resource's label (i.e., name)
MetadataAll providersSpecific to each resource type (e.g., AWS S3 buckets object count; Azure Load Balancers provisioning state; GCP Dataflow Jobs create time; Confluent Kafka cluster type; MongoDB Atlas cluster deployed region; PlanetScale database branches count; Snowflake query invocations; Kubernetes workload namespace)
Not TaggedAll providersFilter to see resources not tagged with a specific tag key or any tag key
RegionAWS, Azure, GCPus-east-1, ap-northeast-2, eastus, us-east4
Resource groupAzureThe Azure resource group name
Resource typeAll providersEC2 instances, S3 buckets, Confluent Kafka clusters, Snowflake queries, etc.
SubscriptionAzureThe Azure subscription name
TagAll providersFilter to see resource by a specific tag key or tag key/value
UUID (ARN for AWS)All providersThe unique provider ID (i.e., ARN for AWS) for the resource

Export Resource Report​

To export a resource report, click the export button (looks like an arrow pointing down) on the top right of a saved resource report. The resources in the report are exported in a ZIP file with a CSV file per active resource type. Each row includes an active resource along with its cost and metadata. Select one or more Vantage user emails to send the report. Then, click Export. It may take a few minutes for the email to be sent.

Additional Active Resource Views​

The following tabs are available for specific resources on the Active Resources screen. These tabs provide additional resource-specific information.

Resource Relationships​

You can view relationships between specific resources on the Relationships tab.

The Relationships tab with an example EBS volume displayed

Below are some examples of relationships you may see within your active resources.

ResourceRelationship
Amazon EBS VolumesSee associated EC2 instances, with accrued cost, account, instance ID, region, instance type, launch time, and lifecycle
Amazon EC2 InstancesSee associated EBS volumes, with accrued cost, account, volume type, size, IOPs, and state
Azure DisksSee associated Azure Virtual Machines with accrued costs, account, resource ID, admin username, virtual machine size, boot diagnostics enabled, secure boot enabled, date/time created
Azure Virtual MachinesSee associated disk resources with accrued cost, account, resource ID, disk size, OS type, disk IOPs read/write, disk state, encryption type, network access policy, provisioning state, public network access, zones, and date/time created

S3 Storage Summary​

For S3 buckets, a Storage Summary tab is available that provides a list of storage classes, their corresponding storage sizes, and approximate monthly costs for objects in the S3 bucket.

An example of the S3 Storage Summary screen with Intelligent Tiering suggestions

When available, this screen also includes S3 Intelligent Tiering Considerations with a table of possible maximum savings you can potentially yield as a result of implementing S3 Intelligent Tiering across all objects in the bucket with Standard Storage.

S3 Request Metrics and Egress​

AWS charges you on a per-request basis for S3 with potentially different rates for each request type. The Request Metrics & Egress tab provides a summary of request metrics for the bucket and each metric's cost for the trailing 30 days.

An example of the S3 Storage Summary screen with Intelligent Tiering suggestions

A graph of each request type (GET, PUT, HEAD, POST, SELECT, and LIST) is provided, which visualizes the total number of requests. The total cost for each request type is also provided.

info

See the AWS documentation for information on how to enable ingress and egress request metrics. Note that it takes roughly 15 minutes for AWS to begin delivering these metrics after they are enabled.

EC2 Rightsizing Recommendations​

For EC2 instances where Vantage identifies rightsizing opportunities, the Rightsizing tab is displayed with recommendations. See the Cost Recommendations documentation for details.

CloudWatch Metrics​

For certain resources, you can view high-fidelity charts for CloudWatch metrics. On resources that support CloudWatch metrics, the CloudWatch Metrics tab is displayed. These metrics are useful for rightsizing servers and databases based on utilization.

Resource Report Drill Down

When you connect an AWS account to Vantage, CloudWatch metrics are configured automatically, per resource. The following services support CloudWatch metrics:

  • EC2
  • RDS
  • S3
  • ECS
  • Fargate
note

To inquire about support for Cloudwatch metrics for other services, or for monitoring support for GCP contact support@vantage.sh.

VPC Flow Logs​

For active resources that generate network traffic costs, such as NAT Gateways and EC2 instances, the VPC Flow Logs tab is displayed. Select this tab to view peer resources and the associated traffic category (e.g., public). A Sankey diagram of each associated network flow is provided. See the Network Flow Reports documentation for details on network flow reporting.

Network Flow Report provider resource view

GCP Compute Rightsizing Recommendations​

For GCP Compute resources where Vantage identifies rightsizing opportunities, the Rightsizing tab is displayed with recommendations. See the Cost Recommendations documentation for details.

Kubernetes Rightsizing Recommendations​

For Kubernetes workloads where Vantage identifies rightsizing opportunities, the Rightsizing tab is displayed with recommendations. See the Cost Recommendations documentation for details on how to view and use this information.

Datadog Host Costs​

For cloud resources that have the Datadog agent installed, Vantage can associate Datadog per-host fees along with the primary cloud resources from AWS, Azure, and Google Cloud that drive those costs.

note

To view these costs and agent information, you need to have a Datadog integration, along with either an AWS, Azure, or GCP integration.

On Active Resource views for resources like EC2 instances or Virtual Machines, the Associated Datadog Costs section is displayed and provides a service breakdown of costs.

The following resources are supported:

  • Compute resources with the Datadog agent installed, such as virtual machines or container services
  • Databases that are monitored by Datadog’s DBM

The following Datadog services are supported:

  • Infrastructure Monitoring
  • Database Monitoring
  • APM (Hosts)

For eligible resources, the Datadog Agent Installed dimension, indicates whether the agent is installed. The below image shows resource data for a particular EC2 instance. On the right information panel, the Datadog Agent Installed dimension displays True. Observe associated Datadog costs for Infrastructure Monitoring and APM in the table at the bottom.

The Associated Datadog Costs section is displayed on an active resource

You can also create a Resource Report that filters for resources where the Datadog agent is installed. In the below image, the filter looks for EC2 instances where the agent is installed.

tip

Vantage automatically generates this type of report when it finds the Datadog Agent installed on relevant resources. Navigate to the Resource Reports screen. Autogenerated reports will have a name similar to AWS EC2 Instances with the Datadog Agent Installed.

  1. Select the Metadata filter option.
  2. For Resource Type, select an eligible resource, like EC2 Instances or RDS Instances.
  3. For Select a Key, select Datadog Agent Installed.
  4. For Value, select true.
Metadata filter for Datadog Agent costs
- + \ No newline at end of file diff --git a/annotations/index.html b/annotations/index.html index ebcfb00a..163e04b0 100644 --- a/annotations/index.html +++ b/annotations/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@
Skip to main content

Annotations

Annotations add context to events or data points within Cost Reports or Segment Reports. The annotation consists of a date and a comment. Annotations are particularly useful for describing the infrastructure or cost event that occurred on a particular date.

Add an Annotation​

You can add annotations directly from the chart on a report or from the Annotations sidebar.

  1. From any report chart or graph, hover over the chart's bars or line and select any date point you want to annotate.
  2. The Annotations sidebar is displayed on the right side of the screen. Your username is displayed as well as the date that corresponds with the selected date point on the chart. Enter a comment for the annotation.
  3. To save the annotation, click the arrow icon on the bottom right of the comment box.
Add Annotation From Graph
note

When an annotation is created, a corresponding issue is also created.

View and Edit Annotations​

  1. To view an annotation, from the top right of any Cost Report, click the Annotation icon (looks like a word bubble).
  2. The Annotations sidebar is displayed, with the most recently added annotation at the top of the list. A vertical line is also displayed on the Cost Report chart or graph for dates that have an existing annotation.
  3. To edit the annotation, click the ellipses (...) on the top right of the annotation, then select Edit.
  4. Select a new date from the date picker and/or edit the text in the comment field.
  5. To save the annotation, click the arrow icon on the bottom right of the comment box.

Delete an Annotation​

  1. To delete an annotation, from the top right of any Cost Report, click the Annotation icon (looks like a word bubble).
  2. The Annotations sidebar is displayed. Click the ellipses (...) on the top right of the annotation, then select Remove > OK.
    tip

    Instead of deleting an annotation, consider resolving the annotation, as described below.

Resolve an Annotation​

  1. To resolve an annotation, from the top right of any Cost Report, click the Annotation icon (looks like a word bubble).
  2. The Annotations sidebar is displayed. Click the ellipses (...) on the top right of the annotation, then select Mark as Resolved.
    tip

    To unresolve an annotation, repeat the previous steps, but instead, select the Unresolve option.

View Resolved Annotations​

By default, Cost Reports are filtered to hide resolved annotations from the annotations list and the chart/graph.

  1. To view resolved annotations, click the Annotation icon at the top right of the screen.
  2. From the Annotations sidebar, click the filter icon (next to the New button), then click Show Resolved. Resolved annotations are displayed in both views.

Share an Annotation​

  1. To share an annotation with a teammate, from the top right of any Cost Report, click the Annotation icon.
  2. The Annotations sidebar is displayed. Click the ellipses (...) on the top right of the annotation, then select Copy Link. A link is added to your clipboard, which you can use to share with a teammate.

View Corresponding Issues​

When an annotation is created, a corresponding issue is also automatically created.

  1. To open the corresponding issue, click the ellipses (...) on the top right of the annotation.
  2. Then, select Go to Issue.
View of issue created by an annotation

The issue is automatically created with the Annotation category label attached and a link to the annotated report. The issue's title will default to the report name and annotation's date. You can use the comment function in the issue to also comment on the annotation.

When an annotation is resolved, the corresponding issue will become a closed issue. Unresolving an issue reopens the corresponding issue.

- + \ No newline at end of file diff --git a/api/index.html b/api/index.html index a9b9d792..8530d5ef 100644 --- a/api/index.html +++ b/api/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@
Skip to main content

Vantage API

The Vantage API allows users to programmatically access their cost data as well as create cost resources, such as Cost Reports, Folders, Saved Filters, and Dashboards.

You can access the API documentation to read more about available endpoints and associated endpoint parameters. You can also perform API calls directly from the documentation.

Important

Keep in mind that when using the API reference tool to perform API calls, you are working with your live data.

When viewing an endpoint, all available parameters will be listed on the corresponding API documentation page, along with any requirements.

API documentation

The above image shows a sample POST call to the /folders endpoint.

  • To get started, enter your API token in the Authorization field.
  • The body parameters title, parent_folder_token, saved_filter_token, and workspace_token are displayed, along with a sample request.
  • You can choose to display the request in numerous programming languages, such as Python, Ruby, or JavaScript.
  • Click the Try It! button. The Response and any errors are displayed below the request.

API Versions​

Two versions of the API are available in the documentation:

  • v1.1.0: With v1 of the API, you can view providers (AWS only for this version), services, and products. You can also view Cost Reports. See the v1 API documentation for more information.
  • v2.0: v2 of the API offers expanded functionality. You can automate the management and creation of Cost Reports, Folders, Dashboards, and Saved Filters. You can also create and manage teams and resource access grants. See the v2 API documentation for more information.

Get Started with the API​

Start icon

API Quickstart

Get started with the Vantage API. Understand the API schema and how to call various endpoints.

View Documentation
API icon

API Authentication

Learn how to authenticate and access the Vantage API. Create an API access token with Read and Write scopes enabled.

View Documentation
Query logo

Vantage Query Language (VQL)

Vantage Query Language (VQL) is a SQL-like language designed to filter cloud cost data. VQL provides a normalized schema across various cloud providers.

View Documentation
Dictionary icon

Data Dictionary

Consult the Data Dictionary to view the normalized field names used to create VQL statements. Each provider that Vantage integrates with makes different fields available in their billing data.

View Documentation
- + \ No newline at end of file diff --git a/assets/js/07fcd452.588a9dcf.js b/assets/js/07fcd452.588a9dcf.js deleted file mode 100644 index 0934a451..00000000 --- a/assets/js/07fcd452.588a9dcf.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkdocs_vantage_sh=self.webpackChunkdocs_vantage_sh||[]).push([[720],{3905:(e,t,a)=>{a.d(t,{Zo:()=>d,kt:()=>m});var r=a(7294);function n(e,t,a){return t in e?Object.defineProperty(e,t,{value:a,enumerable:!0,configurable:!0,writable:!0}):e[t]=a,e}function s(e,t){var a=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),a.push.apply(a,r)}return a}function o(e){for(var t=1;t=0||(n[a]=e[a]);return n}(e,t);if(Object.getOwnPropertySymbols){var s=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,a)&&(n[a]=e[a])}return n}var l=r.createContext({}),p=function(e){var t=r.useContext(l),a=t;return e&&(a="function"==typeof e?e(t):o(o({},t),e)),a},d=function(e){var t=p(e.components);return r.createElement(l.Provider,{value:t},e.children)},g="mdxType",u={inlineCode:"code",wrapper:function(e){var t=e.children;return r.createElement(r.Fragment,{},t)}},c=r.forwardRef((function(e,t){var a=e.components,n=e.mdxType,s=e.originalType,l=e.parentName,d=i(e,["components","mdxType","originalType","parentName"]),g=p(a),c=n,m=g["".concat(l,".").concat(c)]||g[c]||u[c]||s;return a?r.createElement(m,o(o({ref:t},d),{},{components:a})):r.createElement(m,o({ref:t},d))}));function m(e,t){var a=arguments,n=t&&t.mdxType;if("string"==typeof e||n){var s=a.length,o=new Array(s);o[0]=c;var i={};for(var l in t)hasOwnProperty.call(t,l)&&(i[l]=t[l]);i.originalType=e,i[g]="string"==typeof e?e:n,o[1]=i;for(var p=2;p{a.r(t),a.d(t,{assets:()=>l,contentTitle:()=>o,default:()=>u,frontMatter:()=>s,metadata:()=>i,toc:()=>p});var r=a(7462),n=(a(7294),a(3905));const s={id:"usage_based_reporting",title:"Usage-Based Reporting",description:"This page describes how to view and manage Usage-Based Reports in Vantage.",keywords:["Usage-Based Reporting","Usage-Based Reports","Cost Reports"]},o="Usage-Based Reporting",i={unversionedId:"usage_based_reporting",id:"usage_based_reporting",title:"Usage-Based Reporting",description:"This page describes how to view and manage Usage-Based Reports in Vantage.",source:"@site/docs/usage_based_reporting.md",sourceDirName:".",slug:"/usage_based_reporting",permalink:"/usage_based_reporting",draft:!1,editUrl:"https://github.com/vantage-sh/docs.vantage.sh/blob/master/docs/usage_based_reporting.md",tags:[],version:"current",frontMatter:{id:"usage_based_reporting",title:"Usage-Based Reporting",description:"This page describes how to view and manage Usage-Based Reports in Vantage.",keywords:["Usage-Based Reporting","Usage-Based Reports","Cost Reports"]},sidebar:"someSidebar",previous:{title:"Dashboards",permalink:"/dashboards"},next:{title:"Annotations",permalink:"/annotations"}},l={},p=[{value:"Create Usage-Based Reports",id:"create-usage-based-reports",level:2},{value:"Export Usage Reports",id:"export-usage-reports",level:3},{value:"View Usage Data for Custom Costs",id:"view-usage-data-for-custom-costs",level:3},{value:"Understand Usage Units",id:"understand-usage-units",level:2},{value:"Use Virtual Tags with Usage-Based Reporting",id:"use-virtual-tags-with-usage-based-reporting",level:2},{value:"Usage-Based Reporting on Dashboards",id:"dashboards",level:2},{value:"Usage Reports Examples",id:"usage-reports-examples",level:2},{value:"Understand EC2 Running Hours",id:"understand-ec2-running-hours",level:3},{value:"View S3 Storage by Tier",id:"view-s3-storage-by-tier",level:3}],d={toc:p},g="wrapper";function u(e){let{components:t,...a}=e;return(0,n.kt)(g,(0,r.Z)({},d,a,{components:t,mdxType:"MDXLayout"}),(0,n.kt)("h1",{id:"usage-based-reporting"},"Usage-Based Reporting"),(0,n.kt)("p",null,"Usage-Based Reporting provides infrastructure consumption in non-monetary metrics, such as virtual machine running hours, stored gigabytes of data, and read/write units consumed. These reports are available within ",(0,n.kt)("a",{parentName:"p",href:"/cost_reports"},"Cost Reports"),", where you can toggle between viewing consumption by spend or by usage."),(0,n.kt)("admonition",{type:"note"},(0,n.kt)("p",{parentName:"admonition"},"Usage-Based Reporting is currently available for AWS, GCP, Azure, and Oracle. Vantage plans to add support for\xa0other providers. Please contact\xa0",(0,n.kt)("a",{parentName:"p",href:"mailto:support@vantage.sh"},"support@vantage.sh"),"\xa0with other providers you\u2019d like to see added.")),(0,n.kt)("h2",{id:"create-usage-based-reports"},"Create Usage-Based Reports"),(0,n.kt)("p",null,"You can view usage from any Cost Report."),(0,n.kt)("ol",null,(0,n.kt)("li",{parentName:"ol"},"Navigate to any Cost Report, or create a new report. By default, the report displays ",(0,n.kt)("strong",{parentName:"li"},"Spend"),"."),(0,n.kt)("li",{parentName:"ol"},"Apply any desired filters and ",(0,n.kt)("strong",{parentName:"li"},"Group By")," criteria. Then, click the ",(0,n.kt)("strong",{parentName:"li"},"Usage")," toggle to the right of the ",(0,n.kt)("strong",{parentName:"li"},"Settings")," menu.")),(0,n.kt)("admonition",{type:"tip"},(0,n.kt)("p",{parentName:"admonition"},"To get the most value from these reports, create a filter that represents a single unit of measure, comparing like resources (e.g., GB or Hours).")),(0,n.kt)("div",{style:{display:"flex",justifyContent:"center"}},(0,n.kt)("img",{alt:"Toggle to show Usage-Based Reporting",width:"80%",src:"/img/usage-toggle.png"})),(0,n.kt)("ol",{start:3},(0,n.kt)("li",{parentName:"ol"},"The following elements are displayed on the ",(0,n.kt)("strong",{parentName:"li"},"Usage")," view:",(0,n.kt)("ul",{parentName:"li"},(0,n.kt)("li",{parentName:"ul"},"The graph and chart display usage over the selected timeframe."),(0,n.kt)("li",{parentName:"ul"},"The total cost is displayed as a trendline on the chart."),(0,n.kt)("li",{parentName:"ul"},"In the table below the graph, the ",(0,n.kt)("strong",{parentName:"li"},"Usage Unit")," (e.g., GB-Hours or Metrics) and ",(0,n.kt)("strong",{parentName:"li"},"Accrued Usage (a numerical value of calculated usage for that unit)")," columns are displayed to show accrued usage for each grouping. The ",(0,n.kt)("strong",{parentName:"li"},"Usage Unit")," column is normalized for consistency across usage type for spelling, abbreviation, and capitalization."),(0,n.kt)("li",{parentName:"ul"},(0,n.kt)("strong",{parentName:"li"},"Accrued Cost, Previous Period Cost"),", and ",(0,n.kt)("strong",{parentName:"li"},"Change")," between these cost values are also displayed. Click the ",(0,n.kt)("strong",{parentName:"li"},"By Date")," option above the table to see the usage data split out by date."))),(0,n.kt)("li",{parentName:"ol"},"Save the report.")),(0,n.kt)("admonition",{type:"note"},(0,n.kt)("p",{parentName:"admonition"},"Usage data refreshes daily in the Vantage console. At this time, you cannot view retroactive usage metrics. Contact\xa0",(0,n.kt)("a",{parentName:"p",href:"mailto:support@vantage.sh"},"support@vantage.sh"),"\xa0if you want to view historical usage data.")),(0,n.kt)("h3",{id:"export-usage-reports"},"Export Usage Reports"),(0,n.kt)("p",null,"To export usage reports, ",(0,n.kt)("a",{parentName:"p",href:"/cost_reports#exporting-cost-reports"},"follow the steps")," provided in the Cost Reports documentation. Ensure you are on the ",(0,n.kt)("strong",{parentName:"p"},"Usage")," view and ",(0,n.kt)("strong",{parentName:"p"},"Usage Unit")," is selected."),(0,n.kt)("div",{style:{display:"flex",justifyContent:"center"}},(0,n.kt)("img",{alt:"Exporting a Cost Report on the Usage view",width:"60%",src:"/img/export-usage.png"})),(0,n.kt)("h3",{id:"view-usage-data-for-custom-costs"},"View Usage Data for Custom Costs"),(0,n.kt)("p",null,"When you create a ",(0,n.kt)("a",{parentName:"p",href:"https://docs.vantage.sh/connecting_custom_providers"},"Custom Provider"),", you can add usage data to your CSV upload files. Ensure you complete the ",(0,n.kt)("inlineCode",{parentName:"p"},"ConsumedQuantity")," and ",(0,n.kt)("inlineCode",{parentName:"p"},"ConsumedUnit")," columns. See the ",(0,n.kt)("a",{parentName:"p",href:"https://docs.vantage.sh/connecting_custom_providers#data-format"},"Custom Providers documentation")," for information on the required schema."),(0,n.kt)("h2",{id:"understand-usage-units"},"Understand Usage Units"),(0,n.kt)("p",null,"The Usage Units displayed on Usage-Based Reporting include any dimension that a supported provider (e.g., AWS) meters and bills. Vantage standardizes these dimensions for inconsistencies in unit case and spelling across providers. For example, Vantage standardized ",(0,n.kt)("inlineCode",{parentName:"p"},"Hours"),", ",(0,n.kt)("inlineCode",{parentName:"p"},"hrs"),", ",(0,n.kt)("inlineCode",{parentName:"p"},"Hrs"),", and ",(0,n.kt)("inlineCode",{parentName:"p"},"hours")," to ",(0,n.kt)("inlineCode",{parentName:"p"},"Hours"),"."),(0,n.kt)("admonition",{type:"note"},(0,n.kt)("p",{parentName:"admonition"},"If a provider does not have usage data, the Usage Unit column is empty and the Accrued Usage column displays 0.00.")),(0,n.kt)("h2",{id:"use-virtual-tags-with-usage-based-reporting"},"Use Virtual Tags with Usage-Based Reporting"),(0,n.kt)("p",null,(0,n.kt)("a",{parentName:"p",href:"https://docs.vantage.sh/virtual_tagging"},"Virtual Tags")," work across both cost and usage consumption for supported providers. If you created Virtual Tags based on cost, the associated usage consumption will inherit the same Virtual Tag. You can use Virtual Tags within your filter criteria to apply Virtual Tags based on usage."),(0,n.kt)("h2",{id:"dashboards"},"Usage-Based Reporting on Dashboards"),(0,n.kt)("p",null,"You can add Usage-Based Reports to dashboards. Ensure you are on the ",(0,n.kt)("strong",{parentName:"p"},"Usage")," toggle, save the report, and then add it to a dashboard. Follow the ",(0,n.kt)("a",{parentName:"p",href:"/dashboards"},"Dashboards")," documentation for details on how to add a report to a dashboard. "),(0,n.kt)("h2",{id:"usage-reports-examples"},"Usage Reports Examples"),(0,n.kt)("p",null,"The following examples provide some common use cases for working with Usage-Based Reporting."),(0,n.kt)("h3",{id:"understand-ec2-running-hours"},"Understand EC2 Running Hours"),(0,n.kt)("p",null,"As an Engineering Manager, you want to view your Amazon EC2 usage by instance hours, so that you can get a profile of your compute usage. This is important because it helps you identify patterns in compute resource consumption. This type of report can help you create more efficient resource planning and cost optimization based on your team's workload needs."),(0,n.kt)("p",null,"You create the following Usage-Based Report in Vantage:"),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},"Filter: All costs from ",(0,n.kt)("strong",{parentName:"li"},"AWS")," where Category ",(0,n.kt)("strong",{parentName:"li"},"Amazon Elastic Compute Cloud - Compute")," is ",(0,n.kt)("strong",{parentName:"li"},"Compute Instance")),(0,n.kt)("li",{parentName:"ul"},"Group By: ",(0,n.kt)("strong",{parentName:"li"},"Subcategory"))),(0,n.kt)("div",{style:{display:"flex",justifyContent:"center"}},(0,n.kt)("img",{alt:"Example of Usage-Based Report displaying EC2 instance running hours",width:"80%",src:"/img/usage-ec2-running-hours.png"})),(0,n.kt)("p",null,"The table below the chart includes the accrued usage and the unit of measure for each line item being viewed, such as EC2 instance bill code. To get the most value from this report, focus on identifying high-usage instance families and regions to optimize compute resources and explore opportunities for cost-saving strategies, like instance rightsizing or transitioning to Savings Plans."),(0,n.kt)("h3",{id:"view-s3-storage-by-tier"},"View S3 Storage by Tier"),(0,n.kt)("p",null,"As a Storage Admin or Engineering Manager, you want to view detailed storage metrics across specific AWS services, such as the total data stored in S3 by tier. With this report, you can better understand the overall profile and efficiency of stored assets and potentially determine whether additional storage policies are required to optimize storage usage and growth."),(0,n.kt)("p",null,"You create the following Usage-Based report to see total data stored in S3 in Vantage:"),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},"Filter: All costs from ",(0,n.kt)("strong",{parentName:"li"},"AWS")," where Category ",(0,n.kt)("strong",{parentName:"li"},"Amazon Simple Storage Service")," is ",(0,n.kt)("strong",{parentName:"li"},"Storage")),(0,n.kt)("li",{parentName:"ul"},"Group By: ",(0,n.kt)("strong",{parentName:"li"},"Subcategory"))),(0,n.kt)("div",{style:{display:"flex",justifyContent:"center"}},(0,n.kt)("img",{alt:"Example of Usage-Based Report displaying S3 storage options",width:"80%",src:"/img/usage-s3-storage.png"})),(0,n.kt)("p",null,"In the table below the graph, usage data is displayed in GB-Months for subcategories like:"),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},(0,n.kt)("strong",{parentName:"li"},"TimedStorage-INT-AIA-ByteHrs")," (Infrequent Access Tier)"),(0,n.kt)("li",{parentName:"ul"},(0,n.kt)("strong",{parentName:"li"},"TimedStorage-INT-IA-ByteHrs")," (Intelligent Tiering)"),(0,n.kt)("li",{parentName:"ul"},(0,n.kt)("strong",{parentName:"li"},"TimedStorage-ByteHrs")," (Standard Tier)")),(0,n.kt)("p",null,"These metrics provide an overview of how data is distributed across different S3 storage tiers. Next steps could include analyzing whether data in the ",(0,n.kt)("strong",{parentName:"p"},"Infrequent Access")," and ",(0,n.kt)("strong",{parentName:"p"},"Intelligent Tiering")," categories is optimally stored, or you could decide whether more aggressive lifecycle policies are needed to move infrequently accessed data to cheaper storage tiers, like Glacier. You could also use this usage information to identify potential cost savings by reducing the storage volume in higher-cost tiers, such as the ",(0,n.kt)("strong",{parentName:"p"},"Standard Tier"),"."))}u.isMDXComponent=!0}}]); \ No newline at end of file diff --git a/assets/js/07fcd452.9d68ce82.js b/assets/js/07fcd452.9d68ce82.js new file mode 100644 index 00000000..0667f5d4 --- /dev/null +++ b/assets/js/07fcd452.9d68ce82.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkdocs_vantage_sh=self.webpackChunkdocs_vantage_sh||[]).push([[720],{3905:(e,t,a)=>{a.d(t,{Zo:()=>d,kt:()=>m});var r=a(7294);function n(e,t,a){return t in e?Object.defineProperty(e,t,{value:a,enumerable:!0,configurable:!0,writable:!0}):e[t]=a,e}function o(e,t){var a=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),a.push.apply(a,r)}return a}function s(e){for(var t=1;t=0||(n[a]=e[a]);return n}(e,t);if(Object.getOwnPropertySymbols){var o=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,a)&&(n[a]=e[a])}return n}var l=r.createContext({}),p=function(e){var t=r.useContext(l),a=t;return e&&(a="function"==typeof e?e(t):s(s({},t),e)),a},d=function(e){var t=p(e.components);return r.createElement(l.Provider,{value:t},e.children)},g="mdxType",u={inlineCode:"code",wrapper:function(e){var t=e.children;return r.createElement(r.Fragment,{},t)}},c=r.forwardRef((function(e,t){var a=e.components,n=e.mdxType,o=e.originalType,l=e.parentName,d=i(e,["components","mdxType","originalType","parentName"]),g=p(a),c=n,m=g["".concat(l,".").concat(c)]||g[c]||u[c]||o;return a?r.createElement(m,s(s({ref:t},d),{},{components:a})):r.createElement(m,s({ref:t},d))}));function m(e,t){var a=arguments,n=t&&t.mdxType;if("string"==typeof e||n){var o=a.length,s=new Array(o);s[0]=c;var i={};for(var l in t)hasOwnProperty.call(t,l)&&(i[l]=t[l]);i.originalType=e,i[g]="string"==typeof e?e:n,s[1]=i;for(var p=2;p{a.r(t),a.d(t,{assets:()=>l,contentTitle:()=>s,default:()=>u,frontMatter:()=>o,metadata:()=>i,toc:()=>p});var r=a(7462),n=(a(7294),a(3905));const o={id:"usage_based_reporting",title:"Usage-Based Reporting",description:"This page describes how to view and manage Usage-Based Reports in Vantage.",keywords:["Usage-Based Reporting","Usage-Based Reports","Cost Reports"]},s="Usage-Based Reporting",i={unversionedId:"usage_based_reporting",id:"usage_based_reporting",title:"Usage-Based Reporting",description:"This page describes how to view and manage Usage-Based Reports in Vantage.",source:"@site/docs/usage_based_reporting.md",sourceDirName:".",slug:"/usage_based_reporting",permalink:"/usage_based_reporting",draft:!1,editUrl:"https://github.com/vantage-sh/docs.vantage.sh/blob/master/docs/usage_based_reporting.md",tags:[],version:"current",frontMatter:{id:"usage_based_reporting",title:"Usage-Based Reporting",description:"This page describes how to view and manage Usage-Based Reports in Vantage.",keywords:["Usage-Based Reporting","Usage-Based Reports","Cost Reports"]},sidebar:"someSidebar",previous:{title:"Dashboards",permalink:"/dashboards"},next:{title:"Annotations",permalink:"/annotations"}},l={},p=[{value:"Create Usage-Based Reports",id:"create-usage-based-reports",level:2},{value:"Export Usage Reports",id:"export-usage-reports",level:3},{value:"View Usage Data for Custom Costs",id:"view-usage-data-for-custom-costs",level:3},{value:"Understand Usage Units",id:"understand-usage-units",level:2},{value:"Use Virtual Tags with Usage-Based Reporting",id:"use-virtual-tags-with-usage-based-reporting",level:2},{value:"Usage-Based Reporting on Dashboards",id:"dashboards",level:2},{value:"Usage Reports Examples",id:"usage-reports-examples",level:2},{value:"Understand EC2 Running Hours",id:"understand-ec2-running-hours",level:3},{value:"View S3 Storage by Tier",id:"view-s3-storage-by-tier",level:3},{value:"Usage-Based Reporting Video Demonstration",id:"usage-based-reporting-video-demonstration",level:2}],d={toc:p},g="wrapper";function u(e){let{components:t,...a}=e;return(0,n.kt)(g,(0,r.Z)({},d,a,{components:t,mdxType:"MDXLayout"}),(0,n.kt)("h1",{id:"usage-based-reporting"},"Usage-Based Reporting"),(0,n.kt)("p",null,"Usage-Based Reporting provides infrastructure consumption in non-monetary metrics, such as virtual machine running hours, stored gigabytes of data, and read/write units consumed. These reports are available within ",(0,n.kt)("a",{parentName:"p",href:"/cost_reports"},"Cost Reports"),", where you can toggle between viewing consumption by spend or by usage."),(0,n.kt)("admonition",{type:"note"},(0,n.kt)("p",{parentName:"admonition"},"Usage-Based Reporting is currently available for AWS, GCP, Azure, and Oracle. Vantage plans to add support for\xa0other providers. Please contact\xa0",(0,n.kt)("a",{parentName:"p",href:"mailto:support@vantage.sh"},"support@vantage.sh"),"\xa0with other providers you\u2019d like to see added.")),(0,n.kt)("h2",{id:"create-usage-based-reports"},"Create Usage-Based Reports"),(0,n.kt)("p",null,"You can view usage from any Cost Report."),(0,n.kt)("ol",null,(0,n.kt)("li",{parentName:"ol"},"Navigate to any Cost Report, or create a new report. By default, the report displays ",(0,n.kt)("strong",{parentName:"li"},"Spend"),"."),(0,n.kt)("li",{parentName:"ol"},"Apply any desired filters and ",(0,n.kt)("strong",{parentName:"li"},"Group By")," criteria. Then, click the ",(0,n.kt)("strong",{parentName:"li"},"Usage")," toggle to the right of the ",(0,n.kt)("strong",{parentName:"li"},"Settings")," menu.")),(0,n.kt)("admonition",{type:"tip"},(0,n.kt)("p",{parentName:"admonition"},"To get the most value from these reports, create a filter that represents a single unit of measure, comparing like resources (e.g., GB or Hours).")),(0,n.kt)("div",{style:{display:"flex",justifyContent:"center"}},(0,n.kt)("img",{alt:"Toggle to show Usage-Based Reporting",width:"80%",src:"/img/usage-toggle.png"})),(0,n.kt)("ol",{start:3},(0,n.kt)("li",{parentName:"ol"},"The following elements are displayed on the ",(0,n.kt)("strong",{parentName:"li"},"Usage")," view:",(0,n.kt)("ul",{parentName:"li"},(0,n.kt)("li",{parentName:"ul"},"The graph and chart display usage over the selected timeframe."),(0,n.kt)("li",{parentName:"ul"},"The total cost is displayed as a trendline on the chart."),(0,n.kt)("li",{parentName:"ul"},"In the table below the graph, the ",(0,n.kt)("strong",{parentName:"li"},"Usage Unit")," (e.g., GB-Hours or Metrics) and ",(0,n.kt)("strong",{parentName:"li"},"Accrued Usage (a numerical value of calculated usage for that unit)")," columns are displayed to show accrued usage for each grouping. The ",(0,n.kt)("strong",{parentName:"li"},"Usage Unit")," column is normalized for consistency across usage type for spelling, abbreviation, and capitalization."),(0,n.kt)("li",{parentName:"ul"},(0,n.kt)("strong",{parentName:"li"},"Accrued Cost, Previous Period Cost"),", and ",(0,n.kt)("strong",{parentName:"li"},"Change")," between these cost values are also displayed. Click the ",(0,n.kt)("strong",{parentName:"li"},"By Date")," option above the table to see the usage data split out by date."))),(0,n.kt)("li",{parentName:"ol"},"Save the report.")),(0,n.kt)("admonition",{type:"note"},(0,n.kt)("p",{parentName:"admonition"},"Usage data refreshes daily in the Vantage console. At this time, you cannot view retroactive usage metrics. Contact\xa0",(0,n.kt)("a",{parentName:"p",href:"mailto:support@vantage.sh"},"support@vantage.sh"),"\xa0if you want to view historical usage data.")),(0,n.kt)("h3",{id:"export-usage-reports"},"Export Usage Reports"),(0,n.kt)("p",null,"To export usage reports, ",(0,n.kt)("a",{parentName:"p",href:"/cost_reports#exporting-cost-reports"},"follow the steps")," provided in the Cost Reports documentation. Ensure you are on the ",(0,n.kt)("strong",{parentName:"p"},"Usage")," view and ",(0,n.kt)("strong",{parentName:"p"},"Usage Unit")," is selected."),(0,n.kt)("div",{style:{display:"flex",justifyContent:"center"}},(0,n.kt)("img",{alt:"Exporting a Cost Report on the Usage view",width:"60%",src:"/img/export-usage.png"})),(0,n.kt)("h3",{id:"view-usage-data-for-custom-costs"},"View Usage Data for Custom Costs"),(0,n.kt)("p",null,"When you create a ",(0,n.kt)("a",{parentName:"p",href:"https://docs.vantage.sh/connecting_custom_providers"},"Custom Provider"),", you can add usage data to your CSV upload files. Ensure you complete the ",(0,n.kt)("inlineCode",{parentName:"p"},"ConsumedQuantity")," and ",(0,n.kt)("inlineCode",{parentName:"p"},"ConsumedUnit")," columns. See the ",(0,n.kt)("a",{parentName:"p",href:"https://docs.vantage.sh/connecting_custom_providers#data-format"},"Custom Providers documentation")," for information on the required schema."),(0,n.kt)("h2",{id:"understand-usage-units"},"Understand Usage Units"),(0,n.kt)("p",null,"The Usage Units displayed on Usage-Based Reporting include any dimension that a supported provider (e.g., AWS) meters and bills. Vantage standardizes these dimensions for inconsistencies in unit case and spelling across providers. For example, Vantage standardized ",(0,n.kt)("inlineCode",{parentName:"p"},"Hours"),", ",(0,n.kt)("inlineCode",{parentName:"p"},"hrs"),", ",(0,n.kt)("inlineCode",{parentName:"p"},"Hrs"),", and ",(0,n.kt)("inlineCode",{parentName:"p"},"hours")," to ",(0,n.kt)("inlineCode",{parentName:"p"},"Hours"),"."),(0,n.kt)("admonition",{type:"note"},(0,n.kt)("p",{parentName:"admonition"},"If a provider does not have usage data, the Usage Unit column is empty and the Accrued Usage column displays 0.00.")),(0,n.kt)("h2",{id:"use-virtual-tags-with-usage-based-reporting"},"Use Virtual Tags with Usage-Based Reporting"),(0,n.kt)("p",null,(0,n.kt)("a",{parentName:"p",href:"https://docs.vantage.sh/virtual_tagging"},"Virtual Tags")," work across both cost and usage consumption for supported providers. If you created Virtual Tags based on cost, the associated usage consumption will inherit the same Virtual Tag. You can use Virtual Tags within your filter criteria to apply Virtual Tags based on usage."),(0,n.kt)("h2",{id:"dashboards"},"Usage-Based Reporting on Dashboards"),(0,n.kt)("p",null,"You can add Usage-Based Reports to dashboards. Ensure you are on the ",(0,n.kt)("strong",{parentName:"p"},"Usage")," toggle, save the report, and then add it to a dashboard. Follow the ",(0,n.kt)("a",{parentName:"p",href:"/dashboards"},"Dashboards")," documentation for details on how to add a report to a dashboard. "),(0,n.kt)("h2",{id:"usage-reports-examples"},"Usage Reports Examples"),(0,n.kt)("p",null,"The following examples provide some common use cases for working with Usage-Based Reporting."),(0,n.kt)("h3",{id:"understand-ec2-running-hours"},"Understand EC2 Running Hours"),(0,n.kt)("p",null,"As an Engineering Manager, you want to view your Amazon EC2 usage by instance hours, so that you can get a profile of your compute usage. This is important because it helps you identify patterns in compute resource consumption. This type of report can help you create more efficient resource planning and cost optimization based on your team's workload needs."),(0,n.kt)("p",null,"You create the following Usage-Based Report in Vantage:"),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},"Filter: All costs from ",(0,n.kt)("strong",{parentName:"li"},"AWS")," where Category ",(0,n.kt)("strong",{parentName:"li"},"Amazon Elastic Compute Cloud - Compute")," is ",(0,n.kt)("strong",{parentName:"li"},"Compute Instance")),(0,n.kt)("li",{parentName:"ul"},"Group By: ",(0,n.kt)("strong",{parentName:"li"},"Subcategory"))),(0,n.kt)("div",{style:{display:"flex",justifyContent:"center"}},(0,n.kt)("img",{alt:"Example of Usage-Based Report displaying EC2 instance running hours",width:"80%",src:"/img/usage-ec2-running-hours.png"})),(0,n.kt)("p",null,"The table below the chart includes the accrued usage and the unit of measure for each line item being viewed, such as EC2 instance bill code. To get the most value from this report, focus on identifying high-usage instance families and regions to optimize compute resources and explore opportunities for cost-saving strategies, like instance rightsizing or transitioning to Savings Plans."),(0,n.kt)("h3",{id:"view-s3-storage-by-tier"},"View S3 Storage by Tier"),(0,n.kt)("p",null,"As a Storage Admin or Engineering Manager, you want to view detailed storage metrics across specific AWS services, such as the total data stored in S3 by tier. With this report, you can better understand the overall profile and efficiency of stored assets and potentially determine whether additional storage policies are required to optimize storage usage and growth."),(0,n.kt)("p",null,"You create the following Usage-Based report to see total data stored in S3 in Vantage:"),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},"Filter: All costs from ",(0,n.kt)("strong",{parentName:"li"},"AWS")," where Category ",(0,n.kt)("strong",{parentName:"li"},"Amazon Simple Storage Service")," is ",(0,n.kt)("strong",{parentName:"li"},"Storage")),(0,n.kt)("li",{parentName:"ul"},"Group By: ",(0,n.kt)("strong",{parentName:"li"},"Subcategory"))),(0,n.kt)("div",{style:{display:"flex",justifyContent:"center"}},(0,n.kt)("img",{alt:"Example of Usage-Based Report displaying S3 storage options",width:"80%",src:"/img/usage-s3-storage.png"})),(0,n.kt)("p",null,"In the table below the graph, usage data is displayed in GB-Months for subcategories like:"),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},(0,n.kt)("strong",{parentName:"li"},"TimedStorage-INT-AIA-ByteHrs")," (Infrequent Access Tier)"),(0,n.kt)("li",{parentName:"ul"},(0,n.kt)("strong",{parentName:"li"},"TimedStorage-INT-IA-ByteHrs")," (Intelligent Tiering)"),(0,n.kt)("li",{parentName:"ul"},(0,n.kt)("strong",{parentName:"li"},"TimedStorage-ByteHrs")," (Standard Tier)")),(0,n.kt)("p",null,"These metrics provide an overview of how data is distributed across different S3 storage tiers. Next steps could include analyzing whether data in the ",(0,n.kt)("strong",{parentName:"p"},"Infrequent Access")," and ",(0,n.kt)("strong",{parentName:"p"},"Intelligent Tiering")," categories is optimally stored, or you could decide whether more aggressive lifecycle policies are needed to move infrequently accessed data to cheaper storage tiers, like Glacier. You could also use this usage information to identify potential cost savings by reducing the storage volume in higher-cost tiers, such as the ",(0,n.kt)("strong",{parentName:"p"},"Standard Tier"),"."),(0,n.kt)("h2",{id:"usage-based-reporting-video-demonstration"},"Usage-Based Reporting Video Demonstration"),(0,n.kt)("p",null,"The below video talks about how to get started with Usage-Based Reporting."),(0,n.kt)("div",{style:{position:"relative",paddingBottom:"56.25%",height:0}},(0,n.kt)("iframe",{src:"https://www.youtube.com/embed/B-1pqTMffrI?si=4S_MJzWRL-jFWj6r?rel=0&color=white&modestbranding=1&showinfo=0&wmode=transparent",frameborder:"0",webkitallowfullscreen:"true",mozallowfullscreen:"true",allowfullscreen:"true",style:{position:"absolute",top:0,left:0,width:"100%",height:"100%",borderRadius:"10px"}})),(0,n.kt)("br",null))}u.isMDXComponent=!0}}]); \ No newline at end of file diff --git a/assets/js/runtime~main.e1390272.js b/assets/js/runtime~main.6e77adbf.js similarity index 99% rename from assets/js/runtime~main.e1390272.js rename to assets/js/runtime~main.6e77adbf.js index 0b60caba..66c56299 100644 --- a/assets/js/runtime~main.e1390272.js +++ b/assets/js/runtime~main.6e77adbf.js @@ -1 +1 @@ -(()=>{"use strict";var e,a,d,c,b,r={},t={};function f(e){var a=t[e];if(void 0!==a)return a.exports;var d=t[e]={id:e,loaded:!1,exports:{}};return r[e].call(d.exports,d,d.exports,f),d.loaded=!0,d.exports}f.m=r,f.c=t,e=[],f.O=(a,d,c,b)=>{if(!d){var r=1/0;for(n=0;n=b)&&Object.keys(f.O).every((e=>f.O[e](d[o])))?d.splice(o--,1):(t=!1,b0&&e[n-1][2]>b;n--)e[n]=e[n-1];e[n]=[d,c,b]},f.n=e=>{var a=e&&e.__esModule?()=>e.default:()=>e;return f.d(a,{a:a}),a},d=Object.getPrototypeOf?e=>Object.getPrototypeOf(e):e=>e.__proto__,f.t=function(e,c){if(1&c&&(e=this(e)),8&c)return e;if("object"==typeof e&&e){if(4&c&&e.__esModule)return e;if(16&c&&"function"==typeof e.then)return e}var b=Object.create(null);f.r(b);var r={};a=a||[null,d({}),d([]),d(d)];for(var t=2&c&&e;"object"==typeof t&&!~a.indexOf(t);t=d(t))Object.getOwnPropertyNames(t).forEach((a=>r[a]=()=>e[a]));return r.default=()=>e,f.d(b,r),b},f.d=(e,a)=>{for(var d in a)f.o(a,d)&&!f.o(e,d)&&Object.defineProperty(e,d,{enumerable:!0,get:a[d]})},f.f={},f.e=e=>Promise.all(Object.keys(f.f).reduce(((a,d)=>(f.f[d](e,a),a)),[])),f.u=e=>"assets/js/"+({53:"935f2afb",80:"9beb87c2",141:"6ae0e5c3",197:"958b6263",261:"reactPlayerKaltura",683:"14a25b0c",696:"106c4e08",720:"07fcd452",764:"bcb2e534",954:"a19b572e",1009:"b70bdc6d",1055:"9b4cd6e8",1086:"10b55b48",1206:"d403c0c7",1207:"5fbc5cf1",1372:"1db64337",1425:"983de4bd",1448:"1b2e4e77",1466:"3d3ae0f6",1539:"a297be8d",1571:"7656156b",1668:"8a8102b1",2088:"194683cf",2121:"reactPlayerFacebook",2493:"271b4122",2544:"c4d53b63",2546:"reactPlayerStreamable",2606:"6ea424a8",2887:"bf9376bc",2976:"126f319d",3081:"cfdeb1a3",3172:"46924e09",3318:"58f0e1ad",3483:"9c7e9bd9",3704:"f33e8706",3743:"reactPlayerVimeo",3796:"770ab7d1",4098:"e281e012",4116:"fdb26a74",4258:"reactPlayerMux",4439:"reactPlayerYouTube",4456:"0168ab4d",4523:"e95a379c",4667:"reactPlayerMixcloud",4910:"df24eda7",5037:"91dacde3",5118:"576d83e5",5136:"d180fdb3",5394:"694f3ac8",5455:"c159e321",5563:"5abe798b",5577:"22ddcaed",5598:"52ddbe2b",5735:"51254b79",5962:"29947905",6011:"reactPlayerFilePlayer",6125:"reactPlayerSoundCloud",6200:"b969777d",6216:"reactPlayerTwitch",6318:"46bb3a7a",6341:"7ef59e88",6347:"92bb876c",6518:"e19aab9a",6566:"5cfcab96",6653:"db32d859",6670:"4052c661",6679:"a6c29cc5",6971:"c377a04b",7051:"8e8d56de",7201:"727323a3",7266:"bc2906f6",7550:"cfe551de",7563:"67f6a168",7567:"5f8a1ed0",7596:"reactPlayerDailyMotion",7664:"reactPlayerPreview",7918:"17896441",7920:"1a4e3797",8055:"reactPlayerWistia",8123:"6b4b5ee6",8134:"f71d46d9",8338:"44ace016",8762:"fc1b33fd",8888:"reactPlayerVidyard",8963:"19e4ddbe",9186:"8b0758b0",9265:"4bf03302",9269:"8d46d109",9281:"15001d55",9336:"c3569567",9468:"77955793",9514:"1be78505",9627:"aeb58552",9800:"64de6e85",9847:"f5fd0e79"}[e]||e)+"."+{53:"064d9d55",80:"66e24c8d",141:"186e6af6",197:"0144574f",261:"1845f3ed",683:"9c785c04",696:"7e54805d",720:"588a9dcf",764:"db195c61",954:"d826904d",1009:"e47bb394",1055:"dbf59841",1068:"b9586640",1086:"1fc9a832",1206:"856f025e",1207:"3450c056",1372:"20b32224",1425:"b8aad8df",1448:"2f32ad0f",1466:"d6d56b36",1539:"42be4300",1571:"9fde84fe",1668:"c6e5c8d4",2088:"b4e8a251",2121:"b1194eea",2493:"06cca55c",2544:"a8992ed2",2546:"6d68519b",2606:"74781382",2887:"9488e2c0",2976:"e7dff422",3081:"e098ba96",3172:"e7b9c0e3",3318:"21ca84d4",3483:"77600ac0",3704:"8e5b822f",3743:"2132f8f2",3796:"724a3e4b",4098:"68b8803c",4116:"940a86ea",4258:"8de3aaa8",4439:"183508d9",4441:"ab35a31b",4456:"c11cb33c",4523:"632c4cf5",4667:"8baa2bdf",4910:"45f8c01b",4972:"d3a30f03",5037:"5f61ca6f",5118:"c12514fd",5136:"f8567ef0",5394:"b58905eb",5455:"b5d26f66",5563:"94fea226",5577:"28dec779",5598:"170f8ca8",5735:"b5962174",5962:"22596add",6011:"8f13aaf8",6125:"11ce6cfa",6200:"6e4ddcfd",6216:"1cb3bf13",6318:"e0be9795",6341:"39160141",6347:"87bb9e3e",6518:"24f2eeca",6566:"b9190082",6653:"62dc07b7",6670:"1fb938e4",6679:"f3fd6fa2",6780:"4c92e39d",6945:"1138d4b8",6971:"2902d20b",7051:"ba5fd218",7201:"b197e51d",7266:"5a5a33eb",7550:"cc1e65c2",7563:"01483431",7567:"00519ffd",7596:"c5dbe4ff",7664:"28ca8077",7918:"b2bc52b2",7920:"407f6d9b",8055:"4065476c",8123:"77542abb",8134:"15b1432e",8278:"96b6f419",8338:"742728fb",8762:"af687e8f",8888:"528e5277",8894:"ed30f19c",8963:"0da69a55",9186:"83e7e3ba",9265:"53dfa18d",9269:"21b045d0",9281:"a5183957",9336:"8af67991",9468:"98ca0625",9514:"e725fda3",9627:"e6fa4158",9800:"63b202a5",9847:"a86fcb5e"}[e]+".js",f.miniCssF=e=>{},f.g=function(){if("object"==typeof globalThis)return globalThis;try{return this||new Function("return this")()}catch(e){if("object"==typeof window)return window}}(),f.o=(e,a)=>Object.prototype.hasOwnProperty.call(e,a),c={},b="docs-vantage-sh:",f.l=(e,a,d,r)=>{if(c[e])c[e].push(a);else{var t,o;if(void 0!==d)for(var l=document.getElementsByTagName("script"),n=0;n{t.onerror=t.onload=null,clearTimeout(s);var b=c[e];if(delete c[e],t.parentNode&&t.parentNode.removeChild(t),b&&b.forEach((e=>e(d))),a)return a(d)},s=setTimeout(u.bind(null,void 0,{type:"timeout",target:t}),12e4);t.onerror=u.bind(null,t.onerror),t.onload=u.bind(null,t.onload),o&&document.head.appendChild(t)}},f.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},f.p="/",f.gca=function(e){return e={17896441:"7918",29947905:"5962",77955793:"9468","935f2afb":"53","9beb87c2":"80","6ae0e5c3":"141","958b6263":"197",reactPlayerKaltura:"261","14a25b0c":"683","106c4e08":"696","07fcd452":"720",bcb2e534:"764",a19b572e:"954",b70bdc6d:"1009","9b4cd6e8":"1055","10b55b48":"1086",d403c0c7:"1206","5fbc5cf1":"1207","1db64337":"1372","983de4bd":"1425","1b2e4e77":"1448","3d3ae0f6":"1466",a297be8d:"1539","7656156b":"1571","8a8102b1":"1668","194683cf":"2088",reactPlayerFacebook:"2121","271b4122":"2493",c4d53b63:"2544",reactPlayerStreamable:"2546","6ea424a8":"2606",bf9376bc:"2887","126f319d":"2976",cfdeb1a3:"3081","46924e09":"3172","58f0e1ad":"3318","9c7e9bd9":"3483",f33e8706:"3704",reactPlayerVimeo:"3743","770ab7d1":"3796",e281e012:"4098",fdb26a74:"4116",reactPlayerMux:"4258",reactPlayerYouTube:"4439","0168ab4d":"4456",e95a379c:"4523",reactPlayerMixcloud:"4667",df24eda7:"4910","91dacde3":"5037","576d83e5":"5118",d180fdb3:"5136","694f3ac8":"5394",c159e321:"5455","5abe798b":"5563","22ddcaed":"5577","52ddbe2b":"5598","51254b79":"5735",reactPlayerFilePlayer:"6011",reactPlayerSoundCloud:"6125",b969777d:"6200",reactPlayerTwitch:"6216","46bb3a7a":"6318","7ef59e88":"6341","92bb876c":"6347",e19aab9a:"6518","5cfcab96":"6566",db32d859:"6653","4052c661":"6670",a6c29cc5:"6679",c377a04b:"6971","8e8d56de":"7051","727323a3":"7201",bc2906f6:"7266",cfe551de:"7550","67f6a168":"7563","5f8a1ed0":"7567",reactPlayerDailyMotion:"7596",reactPlayerPreview:"7664","1a4e3797":"7920",reactPlayerWistia:"8055","6b4b5ee6":"8123",f71d46d9:"8134","44ace016":"8338",fc1b33fd:"8762",reactPlayerVidyard:"8888","19e4ddbe":"8963","8b0758b0":"9186","4bf03302":"9265","8d46d109":"9269","15001d55":"9281",c3569567:"9336","1be78505":"9514",aeb58552:"9627","64de6e85":"9800",f5fd0e79:"9847"}[e]||e,f.p+f.u(e)},(()=>{var e={1303:0,532:0};f.f.j=(a,d)=>{var c=f.o(e,a)?e[a]:void 0;if(0!==c)if(c)d.push(c[2]);else if(/^(1303|532)$/.test(a))e[a]=0;else{var b=new Promise(((d,b)=>c=e[a]=[d,b]));d.push(c[2]=b);var r=f.p+f.u(a),t=new Error;f.l(r,(d=>{if(f.o(e,a)&&(0!==(c=e[a])&&(e[a]=void 0),c)){var b=d&&("load"===d.type?"missing":d.type),r=d&&d.target&&d.target.src;t.message="Loading chunk "+a+" failed.\n("+b+": "+r+")",t.name="ChunkLoadError",t.type=b,t.request=r,c[1](t)}}),"chunk-"+a,a)}},f.O.j=a=>0===e[a];var a=(a,d)=>{var c,b,r=d[0],t=d[1],o=d[2],l=0;if(r.some((a=>0!==e[a]))){for(c in t)f.o(t,c)&&(f.m[c]=t[c]);if(o)var n=o(f)}for(a&&a(d);l{"use strict";var e,a,d,c,b,r={},t={};function f(e){var a=t[e];if(void 0!==a)return a.exports;var d=t[e]={id:e,loaded:!1,exports:{}};return r[e].call(d.exports,d,d.exports,f),d.loaded=!0,d.exports}f.m=r,f.c=t,e=[],f.O=(a,d,c,b)=>{if(!d){var r=1/0;for(n=0;n=b)&&Object.keys(f.O).every((e=>f.O[e](d[o])))?d.splice(o--,1):(t=!1,b0&&e[n-1][2]>b;n--)e[n]=e[n-1];e[n]=[d,c,b]},f.n=e=>{var a=e&&e.__esModule?()=>e.default:()=>e;return f.d(a,{a:a}),a},d=Object.getPrototypeOf?e=>Object.getPrototypeOf(e):e=>e.__proto__,f.t=function(e,c){if(1&c&&(e=this(e)),8&c)return e;if("object"==typeof e&&e){if(4&c&&e.__esModule)return e;if(16&c&&"function"==typeof e.then)return e}var b=Object.create(null);f.r(b);var r={};a=a||[null,d({}),d([]),d(d)];for(var t=2&c&&e;"object"==typeof t&&!~a.indexOf(t);t=d(t))Object.getOwnPropertyNames(t).forEach((a=>r[a]=()=>e[a]));return r.default=()=>e,f.d(b,r),b},f.d=(e,a)=>{for(var d in a)f.o(a,d)&&!f.o(e,d)&&Object.defineProperty(e,d,{enumerable:!0,get:a[d]})},f.f={},f.e=e=>Promise.all(Object.keys(f.f).reduce(((a,d)=>(f.f[d](e,a),a)),[])),f.u=e=>"assets/js/"+({53:"935f2afb",80:"9beb87c2",141:"6ae0e5c3",197:"958b6263",261:"reactPlayerKaltura",683:"14a25b0c",696:"106c4e08",720:"07fcd452",764:"bcb2e534",954:"a19b572e",1009:"b70bdc6d",1055:"9b4cd6e8",1086:"10b55b48",1206:"d403c0c7",1207:"5fbc5cf1",1372:"1db64337",1425:"983de4bd",1448:"1b2e4e77",1466:"3d3ae0f6",1539:"a297be8d",1571:"7656156b",1668:"8a8102b1",2088:"194683cf",2121:"reactPlayerFacebook",2493:"271b4122",2544:"c4d53b63",2546:"reactPlayerStreamable",2606:"6ea424a8",2887:"bf9376bc",2976:"126f319d",3081:"cfdeb1a3",3172:"46924e09",3318:"58f0e1ad",3483:"9c7e9bd9",3704:"f33e8706",3743:"reactPlayerVimeo",3796:"770ab7d1",4098:"e281e012",4116:"fdb26a74",4258:"reactPlayerMux",4439:"reactPlayerYouTube",4456:"0168ab4d",4523:"e95a379c",4667:"reactPlayerMixcloud",4910:"df24eda7",5037:"91dacde3",5118:"576d83e5",5136:"d180fdb3",5394:"694f3ac8",5455:"c159e321",5563:"5abe798b",5577:"22ddcaed",5598:"52ddbe2b",5735:"51254b79",5962:"29947905",6011:"reactPlayerFilePlayer",6125:"reactPlayerSoundCloud",6200:"b969777d",6216:"reactPlayerTwitch",6318:"46bb3a7a",6341:"7ef59e88",6347:"92bb876c",6518:"e19aab9a",6566:"5cfcab96",6653:"db32d859",6670:"4052c661",6679:"a6c29cc5",6971:"c377a04b",7051:"8e8d56de",7201:"727323a3",7266:"bc2906f6",7550:"cfe551de",7563:"67f6a168",7567:"5f8a1ed0",7596:"reactPlayerDailyMotion",7664:"reactPlayerPreview",7918:"17896441",7920:"1a4e3797",8055:"reactPlayerWistia",8123:"6b4b5ee6",8134:"f71d46d9",8338:"44ace016",8762:"fc1b33fd",8888:"reactPlayerVidyard",8963:"19e4ddbe",9186:"8b0758b0",9265:"4bf03302",9269:"8d46d109",9281:"15001d55",9336:"c3569567",9468:"77955793",9514:"1be78505",9627:"aeb58552",9800:"64de6e85",9847:"f5fd0e79"}[e]||e)+"."+{53:"064d9d55",80:"66e24c8d",141:"186e6af6",197:"0144574f",261:"1845f3ed",683:"9c785c04",696:"7e54805d",720:"9d68ce82",764:"db195c61",954:"d826904d",1009:"e47bb394",1055:"dbf59841",1068:"b9586640",1086:"1fc9a832",1206:"856f025e",1207:"3450c056",1372:"20b32224",1425:"b8aad8df",1448:"2f32ad0f",1466:"d6d56b36",1539:"42be4300",1571:"9fde84fe",1668:"c6e5c8d4",2088:"b4e8a251",2121:"b1194eea",2493:"06cca55c",2544:"a8992ed2",2546:"6d68519b",2606:"74781382",2887:"9488e2c0",2976:"e7dff422",3081:"e098ba96",3172:"e7b9c0e3",3318:"21ca84d4",3483:"77600ac0",3704:"8e5b822f",3743:"2132f8f2",3796:"724a3e4b",4098:"68b8803c",4116:"940a86ea",4258:"8de3aaa8",4439:"183508d9",4441:"ab35a31b",4456:"c11cb33c",4523:"632c4cf5",4667:"8baa2bdf",4910:"45f8c01b",4972:"d3a30f03",5037:"5f61ca6f",5118:"c12514fd",5136:"f8567ef0",5394:"b58905eb",5455:"b5d26f66",5563:"94fea226",5577:"28dec779",5598:"170f8ca8",5735:"b5962174",5962:"22596add",6011:"8f13aaf8",6125:"11ce6cfa",6200:"6e4ddcfd",6216:"1cb3bf13",6318:"e0be9795",6341:"39160141",6347:"87bb9e3e",6518:"24f2eeca",6566:"b9190082",6653:"62dc07b7",6670:"1fb938e4",6679:"f3fd6fa2",6780:"4c92e39d",6945:"1138d4b8",6971:"2902d20b",7051:"ba5fd218",7201:"b197e51d",7266:"5a5a33eb",7550:"cc1e65c2",7563:"01483431",7567:"00519ffd",7596:"c5dbe4ff",7664:"28ca8077",7918:"b2bc52b2",7920:"407f6d9b",8055:"4065476c",8123:"77542abb",8134:"15b1432e",8278:"96b6f419",8338:"742728fb",8762:"af687e8f",8888:"528e5277",8894:"ed30f19c",8963:"0da69a55",9186:"83e7e3ba",9265:"53dfa18d",9269:"21b045d0",9281:"a5183957",9336:"8af67991",9468:"98ca0625",9514:"e725fda3",9627:"e6fa4158",9800:"63b202a5",9847:"a86fcb5e"}[e]+".js",f.miniCssF=e=>{},f.g=function(){if("object"==typeof globalThis)return globalThis;try{return this||new Function("return this")()}catch(e){if("object"==typeof window)return window}}(),f.o=(e,a)=>Object.prototype.hasOwnProperty.call(e,a),c={},b="docs-vantage-sh:",f.l=(e,a,d,r)=>{if(c[e])c[e].push(a);else{var t,o;if(void 0!==d)for(var l=document.getElementsByTagName("script"),n=0;n{t.onerror=t.onload=null,clearTimeout(s);var b=c[e];if(delete c[e],t.parentNode&&t.parentNode.removeChild(t),b&&b.forEach((e=>e(d))),a)return a(d)},s=setTimeout(u.bind(null,void 0,{type:"timeout",target:t}),12e4);t.onerror=u.bind(null,t.onerror),t.onload=u.bind(null,t.onload),o&&document.head.appendChild(t)}},f.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},f.p="/",f.gca=function(e){return e={17896441:"7918",29947905:"5962",77955793:"9468","935f2afb":"53","9beb87c2":"80","6ae0e5c3":"141","958b6263":"197",reactPlayerKaltura:"261","14a25b0c":"683","106c4e08":"696","07fcd452":"720",bcb2e534:"764",a19b572e:"954",b70bdc6d:"1009","9b4cd6e8":"1055","10b55b48":"1086",d403c0c7:"1206","5fbc5cf1":"1207","1db64337":"1372","983de4bd":"1425","1b2e4e77":"1448","3d3ae0f6":"1466",a297be8d:"1539","7656156b":"1571","8a8102b1":"1668","194683cf":"2088",reactPlayerFacebook:"2121","271b4122":"2493",c4d53b63:"2544",reactPlayerStreamable:"2546","6ea424a8":"2606",bf9376bc:"2887","126f319d":"2976",cfdeb1a3:"3081","46924e09":"3172","58f0e1ad":"3318","9c7e9bd9":"3483",f33e8706:"3704",reactPlayerVimeo:"3743","770ab7d1":"3796",e281e012:"4098",fdb26a74:"4116",reactPlayerMux:"4258",reactPlayerYouTube:"4439","0168ab4d":"4456",e95a379c:"4523",reactPlayerMixcloud:"4667",df24eda7:"4910","91dacde3":"5037","576d83e5":"5118",d180fdb3:"5136","694f3ac8":"5394",c159e321:"5455","5abe798b":"5563","22ddcaed":"5577","52ddbe2b":"5598","51254b79":"5735",reactPlayerFilePlayer:"6011",reactPlayerSoundCloud:"6125",b969777d:"6200",reactPlayerTwitch:"6216","46bb3a7a":"6318","7ef59e88":"6341","92bb876c":"6347",e19aab9a:"6518","5cfcab96":"6566",db32d859:"6653","4052c661":"6670",a6c29cc5:"6679",c377a04b:"6971","8e8d56de":"7051","727323a3":"7201",bc2906f6:"7266",cfe551de:"7550","67f6a168":"7563","5f8a1ed0":"7567",reactPlayerDailyMotion:"7596",reactPlayerPreview:"7664","1a4e3797":"7920",reactPlayerWistia:"8055","6b4b5ee6":"8123",f71d46d9:"8134","44ace016":"8338",fc1b33fd:"8762",reactPlayerVidyard:"8888","19e4ddbe":"8963","8b0758b0":"9186","4bf03302":"9265","8d46d109":"9269","15001d55":"9281",c3569567:"9336","1be78505":"9514",aeb58552:"9627","64de6e85":"9800",f5fd0e79:"9847"}[e]||e,f.p+f.u(e)},(()=>{var e={1303:0,532:0};f.f.j=(a,d)=>{var c=f.o(e,a)?e[a]:void 0;if(0!==c)if(c)d.push(c[2]);else if(/^(1303|532)$/.test(a))e[a]=0;else{var b=new Promise(((d,b)=>c=e[a]=[d,b]));d.push(c[2]=b);var r=f.p+f.u(a),t=new Error;f.l(r,(d=>{if(f.o(e,a)&&(0!==(c=e[a])&&(e[a]=void 0),c)){var b=d&&("load"===d.type?"missing":d.type),r=d&&d.target&&d.target.src;t.message="Loading chunk "+a+" failed.\n("+b+": "+r+")",t.name="ChunkLoadError",t.type=b,t.request=r,c[1](t)}}),"chunk-"+a,a)}},f.O.j=a=>0===e[a];var a=(a,d)=>{var c,b,r=d[0],t=d[1],o=d[2],l=0;if(r.some((a=>0!==e[a]))){for(c in t)f.o(t,c)&&(f.m[c]=t[c]);if(o)var n=o(f)}for(a&&a(d);lwindow.dataLayer=window.dataLayer||[] - + @@ -20,7 +20,7 @@

Autopilot for AWS Savings Plans

Autopilot for AWS Savings Plans allows Vantage to purchase Compute Savings Plans commitments on your behalf, with manual and automated options. Autopilot continuously evaluates your compute workloads, and when enabled, can automatically purchase the most suitable Compute Savings Plans to maximize your savings. Compute Savings Plans provide broad coverage, applying to all instance types across any AWS Region. Autopilot also provides savings recommendations for RDS, ElastiCache, Redshift, and OpenSearch Reserved Instances.

note

At this time, Autopilot supports only AWS; however, there are plans to expand this functionality to GCP and Azure.

How Autopilot Works​

Autopilot works along with the AWS APIs by ingesting and analyzing Cost and Usage Report data. Autopilot will group your compute workloads on the dashboard by instance hour for each respective compute class. A compute class is defined as compute instance usage structured by instance type (e.g., t3.xlarge, r5.large), Region (e.g., us-east-1, us-west-2), and platform (e.g., Linux, Windows), tracked hourly.

Coverage Determination​

Autopilot looks at historical compute usage (up to 3 months) to understand your average compute usage. This method is intended to help find a relatively steady-state compute footprint to base the coverage percentage, avoiding accidentally purchasing too much coverage because of a temporary spike in compute usage. Compute Savings Plans provide flexibility and apply to EC2, Fargate, and Lambda.

Configurable Lookback Period and Savings Plan Type​

Autopilot allows customers to set a lookback period of either 7, 30, or 60 days, which will generate different effective discounts based on actual usage during that period. You can configure the lookback period that most accurately captures your compute usage to ensure the correct coverage level is purchased. Consider the following general suggestions for lookback periods:

  • 7 days is a good selection for linearly increasing, steady-state workloads.
  • 60 days is a good selection for workloads with higher peak-to-average variation.

You can configure your Savings Plans settings for Autopilot to use 1- or 3-year term lengths and All Upfront, Partial Upfront, or No Upfront payment plans.

Existing Savings Plans​

Autopilot will account for your existing AWS Savings Plans and Reserved Instances. You will not be charged for existing AWS Savings Plans. Even if you feel that you have good coverage with existing AWS Savings Plans, you can consider enabling Autopilot as an insurance policy if they expire or your usage footprint changes.

Legacy Autopilot (EC2 Reserved Instances)​

Because of changes to the underlying Reserved Instance (RI) market, the way Autopilot initially worked changed from supporting AWS Reserved Instances to instead supporting AWS Savings Plans. See the Migrate from Autopilot (EC2 RIs) to Autopilot for AWS Savings Plans section below for details on how to get started. Consult the following resources for additional information:

Autopilot Permissions​

Review the VantageAutoPilot policy on the public AWS CloudFormation template, where you can audit the template's list of required permissions. This template is the same one that’s used when you configure your Vantage and AWS connection.

note

Autopilot cannot and will never change your underlying infrastructure

Enable Autopilot (New Users)​

To use Autopilot, ensure that you’ve connected AWS as a provider. Then, from the top navigation, select Financial Planning > Autopilot. If this is your first time using Autopilot, you will need to complete the onboarding workflow for Autopilot.

  1. From the top right of the Autopilot dashboard, click the Autopilot Enabled toggle to access the onboarding workflow.
    The enable toggle on the Autopilot dashboard
  2. Click Get Started. Vantage performs a permissions check to ensure you have the right permissions configured for Autopilot. These permissions are used to view billing data, generate Savings Plans recommendations, and purchase them on your behalf. See the Autopilot Permissions section above for details. If you fail the permissions check, click Upgrade Integration to configure the correct permissions.
  3. Click Continue.
  4. Review the provided Autopilot Master Services Agreement and click the checkbox to acknowledge that you accept the terms. Click Accept and Continue.
  5. Click Go to Autopilot Dashboard to begin reviewing your savings.

Autopilot will automatically start to analyze your compute trends and can apply savings within days. Typically, you can expect to wait about one week before you start to see material savings on the Autopilot dashboard.

You can also disable Autopilot at any time. To disable Autopilot, click the Autopilot Enabled toggle on the top right of the Autopilot dashboard.

Migrate from Autopilot (EC2 RIs) to Autopilot for AWS Savings Plans​

Autopilot no longer supports purchasing and selling Reserved Instances. If you are a customer that uses Autopilot to manage Reserved Instances, you have three options:

  • Continue to use your Reserved Instances until they expire: Vantage will continue to charge you for 5% of savings realized from the original purchase of these RIs.
  • Opt in to Autopilot for AWS Savings Plans: When you opt in, Vantage will list your Reserved Instances for sale on the Reserved Instance marketplace; however, there is no guarantee that these Reserved Instances will sell. If they sell, Autopilot will automatically backfill your Reserved Instances with new Savings Plans coverage.
  • Contact your AWS account team to discuss a migration from Reserved Instances to Savings Plans: It’s been noted that some customers could negotiate with AWS to replace Reserved Instances with Savings Plans, depending on the specifics of the request. Vantage does not have any details about what makes this more likely to succeed with AWS, and it does not seem to be a guarantee that AWS will perform a swap.

If you have any questions, contact support@vantage.sh. If you're a current Autopilot customer, a message is displayed at the top of the console to migrate to Autopilot for AWS Savings Plans. Click Get Started, and the onboarding workflow previously described will be displayed.

Migration banner on the Autopilot dashboard

Review Autopilot for AWS Savings Plans Dashboards​

From the Autopilot dashboard, you can toggle between the Compute, RDS, ElastiCache, Redshift, and OpenSearch tabs. This section describes the actions you can take on the Compute tab.

Configuration Screen​

After you onboard to Autopilot, the Compute Configuration page is displayed. By default, Autopilot is configured to a 60-day lookback with 3-year No Upfront payment types. You can also access this page by selecting Configuration from the left menu of the Compute tab. On this page, you can configure the following options.

Configuration screen on the Autopilot dashboard providing options for lookback, payment type, and term

Toggle Automatic Purchases​

Automatic Savings Plans purchases are initially disabled. If you want to have Autopilot make Savings Plans purchases on your behalf, click the toggle and acknowledge the displayed confirmation message. You can leave this toggle disabled if you would rather manually approve or decline recommendations. See the Review Coverage Recommendations section below for details on how to manually approve purchases.

Lookback Period​

Autopilot allows customers to set a lookback period of either 7, 30, or 60 days, which will generate different effective discounts based on actual usage during that period. You can configure the lookback period that most accurately captures your usage to ensure the correct coverage level is purchased.

Savings Plan Purchase Configuration​

Configure the length of time and payment options for your purchases. For Term Length, select either 1- or 3-year term lengths. For Payment, select either All Upfront, Partial Upfront, or No Upfront payment plans.

info

For more information about term lengths and payment options, see this Vantage blog on Savings Plans.

Based on your configured inputs, Autopilot provides a recommended Compute Savings Plan for purchase to cover the remaining spend. You can view your recommended coverage to get a better idea of how you are currently committed along with Autopilot’s recommendations.

Coverage Overview​

As Autopilot adjusts the commitment level, this tab includes a graph that displays your On-Demand, Savings Plans, and (if applicable) Reserved and Spot Instance usage. The graph shows daily usage, and you can use the date option above the graph to change the month that’s shown.

Coverage Overview screen on the Autopilot dashboard

Above the graph, your savings are displayed, along with the percentage decrease or increase between this and last month. Your Coverage is also displayed, which shows your coverage across all commitment types. Finally, your All Time Savings found by Autopilot are displayed.

note

This page includes all commitments, regardless of whether they’re covered by Autopilot.

On the Recommended Coverage screen, a graph with On-Demand vs. Recommended Coverage is displayed. Above the chart, the Projected On-Demand Cost is displayed. This is the remaining On-Demand cost that’s estimated to not be covered by the recommended Savings Plans, over the lookback period. On the graph, you can filter by the following options:

  • Service: Amazon EC2, ECS, Fargate, or Lambda
  • Category: A compute category that is a representation of your normalized compute workloads (e.g., USE1-Fargate-GB-Hours)
  • Region: AWS Region (e.g., us-east-1)

The table displays the On-Demand Cost for each combination of service and compute category. Recommended Coverage is displayed as a trendline you can toggle on and off, as shown in the example below. You can also change the date range displayed above the chart.

Review Coverage Recommendations​

The per-hour Recommended Coverage is also displayed in the section above the graph, along with projected savings. Click Review the recommendation to review currently active recommendations. The Review Recommendation panel is displayed on the right. From this panel, you can view the recommendation based on your term length, lookback, and payment configuration. If you do not have automatic purchases enabled on Autopilot, you can click Approve Purchase and Autopilot will make the purchase.

note

The Approve Purchase button will not be visible if automatic purchases are enabled.

Coverage Overview screen on the Autopilot dashboard

Purchase Window​

Note that Vantage generates recommendations daily. When Autopilot makes a purchase, there is a short window where Autopilot doesn’t generate additional proposed recommendations so that the recently accepted recommendation can take effect. Ensure that you have not already made a purchase that would cover this recommendation. Autopilot purchases Savings Plans in increments that are eligible for AWS’s 7-day return policy threshold, so if there's a mistake or a change in your plans, Vantage can request a return for the unneeded Savings Plans. Autopilot specifically follows AWS’s policy regarding Savings Plan returns:

Any Savings Plan with an hourly commitment of $100 or less that has been purchased in the last seven days and in the same calendar month can be returned. Once the calendar month ends (UTC time), these purchased Savings Plans can no longer be returned.

In addition, Autopilot also purchases Savings Plans from AWS with a start date that’s 24 hours from the time it’s manually approved or automatically purchased in Autopilot. During the 24-hour window, the plan is queued. The plan can be deleted at any time within the 24-hour window without restriction. To request a return, contact support@vantage.sh.

note

When a purchase is made, either manually or via an automatic purchase, all account owners will receive an email notification indicating that a purchase was made and will be finalized in 24 hours.

RDS, ElastiCache, Redshift, and OpenSearch Autopilot Graphs​

Autopilot also provides recommendations and the option to purchase Reserved Instances for RDS, ElastiCache, Redshift, and OpenSearch. A tab for each of these services is displayed on top of the Autopilot dashboard.

note

The EC2 tab was previously displayed for legacy Autopilot for EC2 Reserved Instances customers. On this tab, you could control the buying and selling of each compute category displayed. These controls are no longer available with Autopilot for AWS Savings Plans. Instead, you can use Financial Commitment Reports to see a unified view of all your AWS financial commitments, with the ability to filter or create custom aggregations and groupings. Financial Commitment Reports track Savings Plans, Reserved Instances, Spot Instance usage, and EDP discounts for AWS costs.

Recommendations are displayed for individual compute categories, which are a representation of your normalized workloads that consist of the following elements:

  • An instance family, such as m5a
  • A Region
  • A platform (e.g., Redis, PostgreSQL Community Edition)

Each compute category has usage tracked hourly and grouped by the following compute types.

  • Existing customer usage covered by existing Reserved Instances
  • Existing customer usage covered by credits
  • On-Demand usage

You can also view associated active resources. Click the Active Resources link at the bottom of the graph.

RDS​

For RDS, the Y-axis unit is expressed in normalized instance units per hour for each compute category. The rationale for this is that RDS has the benefit of flexible instance families, where a Reserved Instance in the smallest possible unit can add up to have multiple units cover a single larger unit in that family.

RDS recommendations on the Autopilot dashboard

Redshift, OpenSearch, and ElastiCache​

For Redshift, OpenSearch, and ElastiCache, the Y-axis is expressed as the number of instances. Unlike the above example, there isn't flexibility for these classes, so this is a more straightforward scenario where the units represented are the exact number of instances you should purchase.

ElastiCache recommendations on the Autopilot dashboard

Purchase a Recommendation​

For each service, you are provided with the option to view and make purchases for provided savings recommendations. These purchases are manual and not automatically completed by Autopilot.

  1. Above any of the graphs, click View Savings Recommendations.
  2. The Savings Recommendations panel is displayed on the right. At the top of the panel, select the number of instances you want to purchase. A table of potential options is provided along with potential monthly savings to help you decide on the best option.
  3. Click Purchase via AWS Console to make these purchases on AWS.
ElastiCache recommendations on the Autopilot dashboard

Note that recommendations for these other services are generated weekly and indicate the date range for which recent Reserved Instance purchases are not included in the current recommendation. Ensure you have not already made a purchase that would cover this recommendation.

- + \ No newline at end of file diff --git a/aws_supported_services/index.html b/aws_supported_services/index.html index 38738103..54d6d097 100644 --- a/aws_supported_services/index.html +++ b/aws_supported_services/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

AWS Services & Regions

Supported Services​

Vantage will show 100% of your organization's accrued costs across all services. Vantage also offers per-resource pricing for the following services using custom logic to query APIs for each AWS service. While Vantage supports per-resource pricing for the most popular services, some services are not currently supported.

info

To request new service support on Vantage, email support@vantage.sh with the subject line of New AWS Service Support. Include as much information as you can about the data you want to see.

Below is a list of currently supported AWS services for active resources. Vantage maintains read-only access to the AWS APIs for these resources.

ServiceDescription
CloudWatchVantage supports CloudWatch Log Groups and its corresponding storage pricing.
CloudFrontVantage supports CloudFront and showing accrued costs per CloudFront distribution.
CloudTrailVantage supports CloudTrail.
CodePipelineVantage supports CodePipeline.
CodeBuildVantage supports CodeBuild.
ConfigVantage supports Config rules.
DynamoDBVantage supports DynamoDB tables.
EBSVantage supports all EBS volume types and corresponding pricing.
EC2Vantage supports all EC2 instance types, all on-demand and spot pricing as well as supporting CloudWatch metrics and logs. Vantage also imports all underlying EC2 images where possible.
ECSVantage supports ECS services and its corresponding pricing.
EFSVantage supports EFS and its corresponding pricing.
ECRVantage supports ECR and its corresponding pricing.
ELBVantage supports ELB and its corresponding pricing.
ElastiCacheVantage supports all ElastiCache clusters.
EKSVantage supports EKS and its corresponding pricing.
Elasticsearch ServiceVantage supports Elasticsearch and its corresponding pricing.
FargateVantage supports Fargate services and its corresponding pricing.
GlacierVantage supports Glacier vaults its corresponding pricing.
Global AcceleratorVantage supports Global Accelerator and its corresponding pricing.
GlueVantage supports view Glue job costs.
IAMVantage supports IAM groups, IAM users, and IAM roles.
LambdaVantage supports Lambda.
KMSVantage supports showing accrued costs for KMS keys.
Amazon Managed Streaming for Apache Kafka (Amazon MSK)Vantage supports MSK and its corresponding pricing.
MediaLiveVantage supports MediaLive channels, MediaConvert jobs, MediaConnect flow, MediaPackage channels, MediaStore containers, MediaTailor channels, and their corresponding pricing.
MQVantage supports MQ brokers and their corresponding pricing.
Networking primitivesVantage supports networking primitives, like elastic IPs, VPCs, subnets, Availability Zones, and security groups.
RedshiftVantage supports Redshift and its corresponding pricing.
Route53Vantage supports Route 53 Hosted Zones and its corresponding pricing. We also have write access for Route 53 Record Sets.
RDSVantage supports RDS and corresponding pricing.
S3Vantage supports S3 buckets and corresponding bucket pricing. We provide daily storage and object count figures. Vantage shows total costs per S3 bucket as well as summaries by storage classes. Vantage will also provide some calculations for you to determine savings impact of enabling S3 Intelligent-Tiering. We do not have permission to read from your S3 buckets.
Secrets ManagerVantage supports AWS Secrets Manager and its corresponding pricing. We do not have permissions to read your secrets.
SNSVantage supports showing accrued costs for SNS Topics.
SQSVantage supports showing accrued costs for SQS queues.
VPC Flow LogsVantage supports showing costs for VPC Flow Logs.
WorkspacesVantage supports Workspaces and its corresponding pricing.

Supported Regions​

Vantage can sync resources from all AWS regions with external connectivity.

- + \ No newline at end of file diff --git a/azure_supported_services/index.html b/azure_supported_services/index.html index 8c0dcdcd..fa35aecc 100644 --- a/azure_supported_services/index.html +++ b/azure_supported_services/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Azure Services & Regions

Supported Services​

Vantage will show 100% of your organization's accrued costs across all services. Vantage also offers per-resource pricing for the following services using custom logic to query APIs for each Azure service. While Vantage supports per-resource pricing for the most popular services, some services are not currently supported.

info

To request new service support on Vantage, email support@vantage.sh with the subject line of New Azure Service Support. Include as much information as you can about the data you want to see.

Below is a list of currently supported Azure services for active resources. Vantage maintains read-only access to the Azure APIs for these resources.

ServiceDescription/Supported Resources
App ServiceVantage supports App Service plans.
Application GatewayVantage supports Application Gateway and its corresponding pricing.
Azure BackupVantage supports Recovery Services vaults.
Azure Cache for RedisVantage supports Redis caches.
Azure ComputeVantage supports compute snapshots.
Azure Container RegistryVantage supports Container Registry and its corresponding pricing.
Azure Cosmos DBVantage supports Cosmos database account resources.
Azure DatabricksVantage supports Databricks workspaces.
Azure Database for PostgreSQLVantage supports PostgreSQL Single Server and Flexible Server.
Azure ExpressRouteVantage supports ExpressRoute circuits.
Azure FirewallVantage supports Azure Firewall and its corresponding pricing.
Azure Kubernetes Service (AKS)Vantage supports AKS managed clusters.
Azure Monitor Application InsightsVantage supports Application Insights components.
Azure Monitor Log AnalyticsVantage supports Log Analytics workspaces.
Azure SQLVantage supports SQL databases, SQL managed instances, and Azure SQL Database elastic pools.
Azure StorageVantage supports Storage accounts.
Azure Synapse AnalyticsVantage supports Synapse workspaces.
Azure Virtual MachinesVantage supports virtual machine resources.
Azure Virtual NetworkVantage supports NAT gateways and Virtual Machine Scale Sets.
Domain nameVantage supports domain name resources.
Load BalancerVantage supports Load Balancer and its corresponding pricing.
Logic AppsVantage supports Logic Apps workflows.
Microsoft Defender for CloudVantage supports security pricing configurations.
Power BI EmbeddedVantage supports Power BI Dedicated Capacity.
Private endpoint connectionsVantage supports private endpoint connection resources.
Public IP addressVantage supports public IP address resources.
Virtual network gatewayVantage supports virtual network gateway resources.

Supported Regions​

Vantage can sync resources from all Azure regions with external connectivity.

- + \ No newline at end of file diff --git a/budgets/index.html b/budgets/index.html index 84d0739e..294675fd 100644 --- a/budgets/index.html +++ b/budgets/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Budgets

You can create and assign a budget to a Cost Report. Once a budget is assigned, it's easy to see how costs are trending for a particular service, business unit, or team. You can also create budget alerts to alert you based on configurable thresholds.

tip

To get started with budgets, you can also view video demos on Vantage University 🎓.

Create a Budget​

note

The below instructions describe how to manually create a budget. You can also upload a CSV file to create a budget. See the section below for details.

  1. From the top navigation, click Financial Planning.
  2. On the left navigation, select Budgets. All existing budgets are displayed. You can edit or delete budgets from this screen.
    Click to view example image
    The Budgets landing page with three different budgets displayed. One budget has a month-to-date performance listed.
  3. From the top right of the screen, click New Budget.
  4. Enter a budget Name and click Create Budget.
  5. A budget details page is displayed. Under Assign to Cost Report or Segment, select the report you want the budget to be displayed on. You can create Budget Alerts to assign once your budget is created. Any associated alerts will also be listed here. See the section below for more details.
  6. For Budget Periods, click New Budget Period. Budgets can have multiple budget periods, one for each month, with a specific amount for each period:
    • Enter a start date in YYYY-MM format (e.g., 2024-03).
    • Enter an optional period end date.
    • Enter a total monthly budget amount in dollars.
    • Click New Budget Period to add additional budget periods.
      Click to view example image
      The Budget creation screen with three different periods added to the budget.
  7. At the top right, click Save Changes.
  8. Select the Performance tab to see each budget period with a month-to-date performance of how the budget performed or is forecasted to perform.
    Click to view example image
    Performance of a budget across six periods with actual and forecasted performance displayed for each month.
note

Budgets are scoped to a report within a specific workspace, and access can be controlled via teams.

Upload a Budget​

If you have existing budgets in spreadsheets or another tool, you can import them all at once by uploading a CSV file.

Expected Format​

Budget import files must adhere to the following requirements:

  • The file must be in CSV format.
  • The header row of the CSV must start with a unique string or identifier (e.g., Budget Name).
    • The remaining values in the header row must be the budget period start date in YYYY-MM format (e.g., 2023-02 for February 2023).
  • Each additional row in the CSV must start with the name of the budget. Corresponding values must be expressed as decimals (e.g., 25000.00) for every month where there is an associated budget. If there is no budget for a month, the value can be blank.

The below example shows a readable view, CSV file format, the budget import screen, and the final budget in Vantage. Team 3 does not have a budget for 3/2024, and therefore, no budget period is added for Team 3 during that timeframe. On the import, the period start and end date are set based on the column headers.

Budget Name2024-012024-022024-03
Team 150000.0051000.0052000.00
Team 230000.0030000.0040000.00
Team 345000.0050000.00

Import Budget​

  1. From the top navigation, click Financial Planning.
  2. On the left navigation, select Budgets.
  3. From the top right of the screen, click Import. The Import Budget Data modal is displayed.
  4. Click Choose File and select a CSV file.
  5. Click Upload. The Review Imported Errors screen is displayed. If no errors are present, click Confirm > OK.

Fix Import Errors​

If a formatting error is found in your imported CSV file, the import wizard indicates where the error occurred. To fix the error, correct the issue in your source CSV and re-upload the file. In the below example, an error occurred because the CSV file contained duplicate values in the header row.

Budget import errors

Use the following troubleshooting suggestions to check for errors in your CSV file:

  • Ensure there are no additional blank columns in the CSV file.
  • Ensure that each budget name is unique.
  • Ensure the dates in the header row are in the correct format (i.e., YYYY-MM).
  • Ensure values do not include other characters and are in decimal format (e.g., 56000.00, not $56,000.00).

View Budgets on Cost Reports​

Once a budget is assigned to a Cost Report, a budget report with month-to-date performance is displayed at the top of the Cost Report. The budget reflects amortized costs throughout the month, indicating whether the spending is above or below the budget month to date.

A budget is displayed as a trend line on the Cost Report in the console

Budgets are displayed as a yellow line on the graph in the cumulative, daily, weekly, and monthly views on a Cost Report. The dotted portion of the line corresponds to the future budget, which you can track against your forecasted costs.

note

If you select the Weekly view, you may see the budget line dip for the first and last week of the month. This is because budgets are metered per day.

Create Budget Alerts​

Budget alerts are automated alerts based on configurable budget thresholds. Create a budget alert for any of your existing budgets to notify you when a percentage of a budget is exceeded for a designated period. You can configure alerts to notify Vantage users via email, Slack, or Microsoft Teams channels. Periods can be set before or after a certain number of days into the month (e.g., “10 days from the start of the month”).

note

If you want to send alerts to Slack or Microsoft Teams, see the report notifications documentation for information on how to set up a Slack or Microsoft Teams integration with Vantage. Once you've set up an integration, follow the steps below to set up a budget alert.

  1. From the top navigation, click Financial Planning.
  2. On the left navigation, select Budget Alerts.
  3. At the top, click Configure Alert.
  4. The New Budget Alert modal is displayed. Configure the following parameters:
    • For Budget, select the budget for which the alert applies.
    • For If Costs Exceed, select a percentage threshold (e.g., 85% of the budget). You'll receive an alert only if the threshold is reached.
    • Optionally, enter a period of observation within the month (e.g., “10 days from the start of the month” or “5 days before the end of the month").
    • For Email recipients, select recipients, who are members of your team in Vantage, you want to receive the alert.
    • Optionally, select any Slack or Microsoft Teams channels you want to receive the alert.
      Click to view example image
      A budget alert configured to send to one user and a Slack team 10 days before the end of the month.
  5. Click Save. Budget alerts will look similar to the below image.
Email budget alert

Recipients will be notified immediately after a Cost Report is updated with the latest data. Reports are updated with the latest data at least once per day. If your budget exceeds the threshold for multiple alerts, you'll be notified only about the most severe alert (the alert with the highest threshold).

Budget Alert Limitations​

At this time, only dynamic, percentage-based thresholds are supported. Budget alerts can be configured only to send alerts based on actual, not forecasted costs.

note

A single cost increase will not typically trigger a budget alert. If you are interested in this feature, see the Cost Anomaly Alerts documentation.

Because a budget is defined for a month, you can only be alerted based on the budget amount for the entire month instead of the month to date. As a workaround, configure the Within option on the alert (e.g., "10 days from the start of the month") to mimic this behavior.

Budget Alerts and Cost Reports​

If you update a Cost Report that is associated with a budget alert, the following message is displayed: This report has budget alerts and may trigger a notification. Are you sure you want to save the report? You must confirm before saving the report.

- + \ No newline at end of file diff --git a/changelog/index.html b/changelog/index.html index 0c5bda07..455c65c1 100644 --- a/changelog/index.html +++ b/changelog/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Changelog

This page was last updated on October 16, 2024, with product updates for 0ctober 2024.

October 2024​

Product Updates​

  • New Azure recommendations: Additional recommendations, such as for rightsizing, were added for Azure.
  • Visual UI updates: Visual updates have been made to the look and feel of the Cost Reporting and Segments screens.
  • View as VQL: On Resource Report filters, a new button is available to see the VQL representation of a Resource Report filter.

Kubernetes Agent Updates​

See September's update for the most recent Kubernetes agent release.

API Updates​

  • User token endpoint: The last_seen_at field is added to the response of the /users/{user_token} endpoint.
  • Currency on workspaces: The enable_currency_conversion parameter is added to the /workspaces endpoint to enable currency conversion on workspaces.
  • Resource Reports API: The following endpoints were added to support the new Resource Reports API:
    • POST option for the /resource_reports endpoint
    • PUT option for the /resource_reports/{resource_report_token} endpoint
    • GET option for /resources endpoint
    • GET option for the /resources/{resource_token} endpoint
    • VQL is now available with its own namespace and schema to support creating and managing Resource Reports
  • vantage-go updates: Version 0.0.40 of the vantage-go library includes the following updates:
    • GET /resources added
    • GET/PUT/POST/DELETE of /resource_reports
    • PUT /workspaces can now configure currency for a workspace
    • /users API response now includes last_seen_at
  • You can now use terraform import to manage Terraform resources outside of the current state on the Terraform provider.

September 2024​

Product Updates​

  • Currency conversion: You can now set a presentational currency, on a per-workspace basis, to visualize cost reporting data in a currency of your choice.
  • Datadog integration update: Vantage provides a visual alert in the integration settings screen when the Datadog integration requires an update.
  • Datadog hosts costs: For cloud resources that have the Datadog agent installed, Vantage can associate Datadog per-host fees along with the primary cloud resources from AWS, Azure, and Google Cloud that drive those costs.
  • Auto-generated Datadog Resource Reports: Vantage automatically generates a Resource Report when it finds the Datadog Agent installed on relevant resources. Auto-generated reports will have a name similar to AWS EC2 Instances with the Datadog Agent Installed.
  • Visual UI updates: Visual updates have been made to the look and feel of the Cost Reporting sidebar.
  • View as VQL: On Cost Report filters, a new button is available to see the VQL representation of a Cost Report filter.
  • GitHub integration: Vantage now integrates with GitHub. See the Connecting GitHub documentation for details on how to get started.
  • New Autopilot banner: A banner is now displayed at the top of the Coverage Overview page on Autopilot when a Savings Plan is purchased.
  • Drill down on Cost Reports: You can now drill down in the Cost Report table when the report is grouped by more than three options.
  • Account search for Cost Recommendations: Organizations with many accounts can now search for an account to filter by on the Cost Recommendations screen.
  • Faster Budget loads: Performance improvements were made to the Budgets page for faster page loads.
  • Cost Report link in Slack alerts: A link to the corresponding Cost Report is now displayed on Slack budget alerts.
  • AWS Organization tags: You can now filter and group by AWS Organization tags on Cost Reports.

Kubernetes Agent Updates​

  • Updated cost calculation: Kubernetes Efficiency Reporting and Rightsizing Recommendations now accurately calculate pod costs down to the minute, meaning if a pod runs for only 5 minutes within an hour, Vantage recognizes only 5 minutes of spend, rather than the full hour.
  • Version 1.0.26, Helm Chart vantage-kubernetes-agent-1.0.36, includes the following update:
    • Added support for podSecurityContext to define the security options the pod should be run with

API Updates​

v0.1.27 of the Vantage Terraform Provider is now available:

  • The created_by_token is now available as an option on the vantage_budgets data source.

August 2024​

Product Updates​

  • Savings Planner visual updates: Visual updates were made to Savings Planner for navigability.
  • Custom Providers integration: Custom Providers are now available as an integration option, so you can connect any of your providers to Vantage using the FinOps FOCUS schema.
  • Cost Report and Dashboard header visual updates: Visual updates were made to Cost Report and Dashboard headers for better organization and navigation.
  • Provider icons visual improvements: On the main Virtual Tags and Cost Reporting screens, visual updates were made to include provider icons next to each report or virtual tag in the list.
  • Autopilot for AWS Savings Plans: Autopilot for AWS Savings Plans is now available, which allows Vantage to purchase Compute Savings Plans commitments on your behalf, with manual and automated options.
  • Account filter matching: For cost providers, like AWS, that have human-readable account names, you can now wildcard-match on account names in Cost Report filters (e.g., set a filter, like Account contains dev).
  • Total costs by date: On Cost Reports, the Total Costs row is displayed when you change the table display to By Date.
  • Set default dashboard: You can set the default dashboard that's displayed for a team or individual users when they log in to Vantage.
  • Additional GCP Active Resources: The following GCP services were added and synced as active resources:
    • Cloud AlloyDB clusters, instances, and backups
    • Cloud Container clusters
    • Cloud Functions functions
    • Memorystore for Redis instances
    • Secrets Manager secrets

Kubernetes Agent Updates​

See May's update for the most recent Kubernetes agent release.

API Updates​

  • The following API endpoints were released along with the Custom Providers feature:
    • /integrations/custom_provider endpoint to create a Custom Provider
    • /integrations/{integration_token}/costs.csv endpoint to upload a Custom Provider CSV file
    • /integrations/{integration_token}/costs/{user_costs_upload_token} endpoint to delete a Custom Provider CSV file
    • /integrations/{integration_token}/costs endpoint to list all uploaded CSV files for a Custom Provider

July 2024​

Product Updates​

  • Dynamic Cost Allocation: Dynamic cost allocation, which is the process of allocating costs based on another existing cost or metric, is now available. See the Virtual Tagging documentation for details.
  • Workspace access updates: If you are granted access via RBAC to a report in a workspace outside your regularly accessed workspace, when you access the link to the report, you will have temporary access to the new workspace and can view the items that you were granted access to.
  • Share reports across workspaces: You can now share report links across different workspaces. For example, if you're in Workspace A and open a report link from Workspace B, you'll be automatically switched to Workspace B to view the report. Previously, a 404 error was displayed.
  • GCP active resources: GCP active resources are now synced and available to filter within Resource Reports.
  • GCP cost recommendations: Recommendations are now available for GCP Compute rightsizing and commitments.
  • Grouped report forecasts: You can now view forecasts for bar charts when they are grouped.
  • Flow weight on Network Flow Reports: You can now change the Sankey diagram to be weighted by either costs or bytes on Network Flow Reports.
  • Save as new on reports: On existing reports, like a Cost Report, you can now click Save as New at the top to create a new report based on the current report's filters.
  • Vantage for MSPs: Vantage for MSPs is a new set of features for managed service providers. Learn more on the Partners website.

Kubernetes Agent Updates​

See May's update for the most recent Kubernetes agent release.

API Updates​

  • Costs endpoint updates: The /costs endpoint has been updated with the ability to specify settings parameters for returned costs, like credits, refunds, etc.
  • Cost Report endpoint updates: The /cost_reports endpoint has been updated to include the following parameters for POST and PUT:
    • previous_period_start_date
    • previous_period_end_date
    • start_date
    • end_date
    • date_interval
    • chart_type
    • date_bin
  • Two version updates were released of the Terraform provider:
    • v0.1.23 is based on the above API changes, including new parameters for the vantage_cost_report resource and the vantage_cost_reports data source.
    • v0.1.24 adds support for dynamic cost allocation on the virtual_tag_config resource.

June 2024​

Product Updates​

  • Visual UI updates: Visual updates have been made to the look and feel of the main navigation and related Active Resources screens.
  • New dashboard widgets: Resource Reports are a new widget option on dashboards.
  • Data transfer cost visibility: Network Flow Reports are available to provide visibility by source and destination to the flows within your network that are driving costs.
  • New active resources: VPC Flow Logs are now synced as active resources.
  • VPC Flow Logs active resources tab: The VPC Flow Logs tab is available on the Active Resources screen for resources that generate network traffic. This tab shows network flows for related resources.
  • Network costs: A new Network Costs button is displayed on Cost Reports for resources that generate network costs, like NAT Gateways.

Kubernetes Agent Updates​

See May's update for the most recent Kubernetes agent release.

API Updates​

New /integrations endpoints are available:

  • GET /integrations: retrieves all existing integrations
  • POST /integrations/azure: creates a new Azure integration
  • POST /integrations/gcp: creates a new GCP integration
  • DELETE /integrations/{integration_token}: deletes a specific integration
  • GET /integrations/{integration_token}: gets information about an existing integration
  • PUT /integrations/{integration_token}: updates workspace access for an existing integration

May 2024​

Product Updates​

  • Visual UI updates: Visual updates have been made to the look and feel of the Budgets, Business Metrics, Cost Recommendations, Active Resources, and Resource Reports screens.
  • Segments RBAC: Users with the editor role can now update segments.
  • MongoDB tags: Tags are now available as a filtering dimension for MongoDB Cost Reports.
  • Forecasted performance of a budget: Future budget periods are now displayed and compared to forecasts on Cost Reports.
  • Reserved Instance recommendations: Reserved Instance recommendations now include a link to Autopilot with split-out categories and usage.
  • Negative cost axis: The range of the cost axis on Cost Reports is updated to include negative values. This is visible in cases where costs may be negative due to things like credits.
  • Vantage University: Vantage University is available on the docs site and includes a set of videos for getting started with Vantage.
  • Labeled business metrics: Labeled business metrics are available to identify the source of a metric—like an associated application or cost center.
  • Kubernetes GPU idle costs: For each Kubernetes pod, you can now view the idle and total costs for NVIDIA GPU usage within a Kubernetes cluster.

Kubernetes Agent Updates​

  • Version 1.0.26, Helm Chart vantage-kubernetes-agent-1.0.34, includes the following updates:
    • Support is now available for NVIDIA GPU exporters.
    • Fargate nodes are now ignored.
  • Version 1.0.25, Helm Chart vantage-kubernetes-agent-1.0.33, includes the following update:
    • The report_http_proxy flag is available to supply during configuration. HTTP proxy is used for the HTTP client that calls Vantage and S3 during periodic reports. Overrides HTTP_PROXY in the event both are specified.

API Updates​

  • Cost recommendations endpoint: The /recommendations endpoint automates the retrieval of cost recommendations. The endpoint includes filtering options for parameters like category and provider.
  • Integrations endpoint: The /integrations endpoint automates the retrieval of information about existing integrations. You can also send a DELETE call to delete existing integrations.
  • Segment tokens in budgets: The cost_report_token parameter of the /budgets endpoint now accepts segment tokens (in addition to Cost Report tokens).
  • Business metrics endpoint updates: With the release of labeled business metrics, the /business_metrics endpoint is updated to include a label object as part of the values array of objects.

April 2024​

Product Updates​

  • Visual navigation improvements: A Create New menu for quick actions is available on the top navigation bar.
  • Datadog metrics: Business metrics have been updated with the option to directly ingest Datadog metrics.
  • New virtual tagging feature: Virtual tagging is available to consistently tag costs across providers in Vantage. This feature can help to increase tagging coverage across your cloud infrastructure.
  • New rightsizing recommendations: Kubernetes rightsizing recommendations are now available for rightsizing managed workloads in Kubernetes.
  • New to active resources: Kubernetes managed workloads are synced as active resources in Vantage.
  • Expanded forecasts: Forecasts have been expanded to include the upcoming month, the next three months, and six months ahead.
  • Kubernetes agent version: The Clusters section of the Kubernetes agent settings screen is updated to show cluster name, version, and indicate if the cluster is out of date.
  • Expanded chart options: Expanded chart options are available for Cost Reports, including expanded date bin selections for area and line charts and multi-line charts for grouped data.
  • API service tokens: Users with owner-level permissions can now create API service tokens for authenticating with the Vantage API at the account level, rather than being associated with a specific user.

Kubernetes Agent Updates​

See March's update for the most recent Kubernetes agent release.

API Updates​

March 2024​

Product Updates​

  • Saved filters on dashboards: You can now add a saved filter to a dashboard to view all Cost Reports on the dashboard with consistent filters applied.
  • Updated Overview page: Associated budget and per unit costs are now displayed on Cost Report widgets on the Overview page.
  • Updated UI look and feel: Visual improvements were made to the look and feel of the Overview and Budgets screens.
  • Segments sync status: Cost allocation segments are now updated to show segment sync status. The look and feel of this page have been visually updated as well.
  • Filterable cost recommendations: Recommendations are now filterable by provider on the Cost Recommendations screen.
  • Pie chart option: You can now change the graph view on Cost Reports to a pie chart.
  • Custom date filtering: The date picker on Cost Reports is updated to allow for custom period selections.
  • Custom Databricks pricing: Custom discounts are now supported for Databricks SKU groups.

Kubernetes Agent Updates​

The following versions were released this month.

  • Version 1.0.24 includes the following update:

    • Supports monitoring ArgoCD resources in the cluster.

  • Version 1.0.23 includes the following updates:

    • app.kubernetes.io labels are now allowed.
    • Agent scrape results are added to agent metadata.
    • Prometheus metrics are added for tracking reporting successes/failures.
    • Dependencies are updated to the latest stable versions.
    • Additional controller metadata is included in agent reports for use in Active Resources.

API Updates​

  • New tagged option: On the /cost_reports endpoint in the API, and the vantage_cost_report resource in the Terraform provider, tagged is a valid option for the groupings parameter.
  • New dashboard parameter: The saved_filter_tokens parameter is now available on the /dashboards endpoint. It is also available on the vantage_dashboard resource in the Terraform provider.
  • New Terraform resources: Additional Terraform resources are now available:
    • The vantage_segment resource automates the creation of cost allocation segments in Vantage. Large segment hierarchies can easily be automated with filters applied as needed.
    • The vantage_team resource automates the creation of Vantage teams. Create a team and assign Vantage users, by email, to the team.
    • The vantage_access_grant resource automates access grants via role-based access controls in Vantage. Create grants to allow or deny teams access to resources, like folders or Cost Reports.
    • The vantage_report_notification resource automates the creation of Cost Report notifications. Create a notification for a specific Cost Report. Specify the notification’s frequency (e.g., daily) and change (e.g., in dollars).
  • Terraform data sources: Data sources are now available to retrieve information outside your Terraform configuration.
  • Business metrics endpoint: The /business_metric endpoint is now available to create and update business metrics in the console.

February 2024​

Product Updates​

  • Ability to group by multiple tags: You can now group by multiple tags in the console.
  • EC2 rightsizing recommendations: New recommendations are added for rightsizing EC2 instances.
  • Segment settings: You can now edit the default report settings on a top-level segment report.
  • Updated UI look and feel: Visual updates were made to Financial Planning menus and screens.
  • Financial Commitment Reports: Financial commitment reports are now available to help you understand how your organization is utilizing financial commitments.
  • Bulk actions for folders and Cost Reports: You can now move and star folders and Cost Reports in bulk.
  • Additional operators on resource reports: The is greater than and is less than operators are both available for Metadata filters on resource reports. For example: where Metadata CloudWatch Log Groups Retention in Days is greater than 5.

API Updates​

  • New notifications endpoint: The /report_notifications endpoint is now available. This endpoint also now has support via the Terraform provider.
  • Multi-tag support: The groupings parameter of the /costs endpoint has support for multiple tags.
  • Data sources in Terraform: Data sources for multiple Vantage resources are now available in the Terraform provider.
  • Segment costs: You can now obtain costs for segment reports from the /costs endpoint.
  • Settings options on segments: The report_settings object is now available on the /segments endpoint.
  • Settings on Cost Reports: The settings object is now available on the /cost_reports endpoint.

January 2024​

Product Updates​

  • PlanetScale support: PlanetScale is now supported as a provider in Vantage.
  • Updated UI look and feel: The Settings UI and main navigation bar are visually updated for better navigability.
  • Charge Type filter and group: Charge Type is available as a new filter and grouping category on Cost Reports.
  • Created by column: The Created by column is added to Business Metrics, Savings Models, as well as Cost Reporting screens, like Dashboards.
  • Created On column sort: The Created On column, available on Cost Reporting screens, correctly sorts by date.
  • Created by me filter: The Created by me filter screen is available in Cost Reporting. New reports you create will now be visible within this view.
  • Tag grouping for advanced exports: The advanced export on Cost Reports now has a Tag grouping option.
  • "Other" grouping expanded: The Other grouping is expanded on Cost Reports so you can display additional costs, beyond what's already displayed, in the table and graph.
  • Cost Reports line and area charts: When grouping by specific criteria, you can now adjust the Cost Report graph to be displayed as an area chart or line chart, with a line for each group.
  • Searchable Business Metrics Report dropdown: The Report dropdown menu on the Business Metrics screen is now searchable.

API Updates​

  • Priority added to PUT request for segments: The priority parameter is available on the /segments/{segment_token} endpoint.
  • New groupings parameter: The groupings parameter is available on the /costs endpoint.
  • Access grant endpoint update: Update/destroy endpoints for /access_grant now use the access grant token to identify an access grant.

December 2023​

Product Updates​

  • Expanded recommendations: Cost recommendations have been expanded for Azure.
  • Kubernetes efficiency reports: Kubernetes efficiency reports allow teams to quickly identify which Kubernetes pods are running inefficiently. These reports are a customized view of Kubernetes idle and total costs based on Cluster, Namespace, and Label.
  • Official Kubernetes integration: The Vantage Kubernetes agent provides a single in-cluster deployment that handles both metrics collection and upload to Vantage—without any intermediary requirements.

API Updates​

  • Cost allocations segment API: Script both the creation and modification of cost allocation segments via new API endpoints.

November 2023​

Product Updates​

  • Automatic team assignment for SSO: Automatically assign users to teams in Vantage based on your organization's existing SSO groups.
  • Confluent support: Confluent is now supported as a provider in Vantage.
  • Team-based access controls: Enterprise customers can now use role-based access control to create fine-grained permissions for teams across their organizations.

October 2023​

Product Updates​

  • Resource report exports: You can now download lists of resources for further exploration via resource reports.

September 2023​

Product Updates​

  • Annotations for reports: You can now add annotations to Cost Reports for infrastructure changes or events.
  • Oracle support: Oracle is now supported as a provider in Vantage.
  • Dashboards: You can now create dashboards with custom collections of Cost Reports and apply date range and period filters to all reports present on them.

API Updates​

  • Write API: The new write API automates the management of Cost Reports, saved filters, and dashboards.
  • New Terraform resources: New Terraform resources are available for Cost Reports, folders, saved filters, and dashboards.

August 2023​

Product Updates​

  • Alert thresholds for anomaly detection: Set custom alert thresholds on cost anomaly alerts, so alerts are tailored to your tolerance for cost spikes.
  • Comparative cost reporting: Cost Reports now have a By Date toggle to display costs by day, week, or month in the costs table.
  • Budget alerts: You can now create budget alerts to receive automated notifications when costs exceed user-defined alert thresholds.

July 2023​

Product Updates​

  • Datadog support: Datadog is now supported as a provider in Vantage.
  • Multi-dimensional cost reporting: You can now group Cost Reports by multiple dimensions.

June 2023​

Product Updates​

  • GCP resource-level costs: Resource-level costs are available for GCP Cost Reports.
  • Resource reports: You can create resource reports to view and access resources generated per provider.

May 2023​

Product Updates​

April 2023​

Product Updates​

  • Self-service SAML: Users can now configure SAML-based SSO for their account without contacting Vantage support.
  • Saved filters: Saved filters are available to save and reuse filter logic across multiple Cost Reports.
  • Azure cost recommendations: Azure cost recommendations are now supported.

March 2023​

Product Updates​

  • Cost Report exports: You can now export Cost Reports via custom exports.
  • Per-unit cost support: With per-unit costs, you can track costs per customer, endpoint, transaction, etc.

API Updates​

  • Terraform provider: Terraform provider is now available to integrate AWS accounts with Vantage.

February 2023​

Product Updates​

  • New Relic support: New Relic is now supported as a provider in Vantage.
  • Expanded resource filtering: You can now filter by resource in Cost Reports.
  • MongoDB Atlas support: MongoDB Atlas is now supported as a provider in Vantage.

January 2023​

Product Updates​

  • Updates to Cost Reports: You can now save custom date ranges, date bins, and groupings to share with teammates in Cost Reports.
  • Autopilot recommendations expanded: Autopilot is expanded to recommend Reserved Instance purchases on RDS, ElastiCache, Redshift, and OpenSearch.
  • Cost allocation segments: Segments are now enabled for teams to allocate costs to business units.
- + \ No newline at end of file diff --git a/connecting_aws/index.html b/connecting_aws/index.html index af8519e4..a6190636 100644 --- a/connecting_aws/index.html +++ b/connecting_aws/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

AWS

Vantage has a few options to connect to AWS, including CloudFormation, the AWS CLI, a Terraform module, and the AWS IAM Console. All options are described below.

How Vantage Connects with AWS​

Vantage understands security concerns and aims to provide as secure a connection as possible with your AWS accounts. Vantage uses a mechanism called a Cross-Account IAM Role to interact with services in your AWS account. AWS has publicly documented this method and officially recommends it as the preferred method of doing any cross-account interactions on AWS. Numerous internal AWS services and systems also leverage this method.

This means that Vantage never needs access credentials, account logins, or passwords for AWS.

AWS Permissions​

When you create a Cross-Account IAM Role using the provided CloudFormation template, or via Terraform, you provide Vantage with various permissions. Vantage only collects metadata about your infrastructure and never attempts to read sensitive information from the underlying services. Our CloudFormation template is public, and you can audit the template's list of permissions.

AWS GovCloud Environments​

Vantage supports ingesting costs for infrastructure in GovCloud environments. Note that at this time, we are unable to sync active resources from GovCloud regions into the Active Resources screen in Vantage; however, you can still view costs by resource in Cost Reports. You also have access to all other Vantage functionality.

Create a Connection​

Navigate to the Vantage Integrations page, and create a new AWS connection. On the AWS connection page, you will see a few options to connect.

  • AWS Console: Click the purple Connect Vantage via AWS Console button to directly log in to AWS. You will be directed to CloudFormation to create the necessary stack that will contain prefilled parameters.
  • AWS CLI: Click the More Connection Options dropdown and select Connect via AWS CLI. The CLI commands needed to create a connection are provided on this screen.
  • Terraform: Click the More Connection Options dropdown and select Connect via AWS Terraform. Instructions for how to connect using the Terraform module are provided on this screen. See the section below for more details.
  • AWS IAM Console: Click the More Connection Options dropdown and select Connect via AWS IAM Console. Instructions are provided on this screen. See the section below for more details.
  • CloudFormation StackSet for Multiple Member Accounts: Click the Connect via CloudFormation StackSet button. The necessary commands to create this connection are displayed. See the next section for more information.

After you create your integration between AWS and Vantage, you can view the status of your connection on the AWS Settings page.

note

Vantage will experience a delay in receiving all your cost data until the first Cost and Usage Report (CUR) is received from AWS. In addition, the first CUR that's sent to Vantage contains only the current month's data. See the instructions below for backfilling a CUR.

Connect Multiple AWS Accounts​

You can connect multiple AWS accounts to Vantage; however, we strongly advise that you connect your root or management AWS account first. When you connect the root account, you can see all costs for the organization, including linked accounts.

Important

If you connect only a linked or member account, you will experience the following issues:

  • You will see only costs and costs by resource for that linked account, rather than for your whole organization.
  • You will be unable to see costs for the other member accounts in your AWS organization.
  • You may not see the full coverage of cost allocation tags from the organization.
  • If Reserved Instances (RIs) are purchased in the linked account, those instances will be realized in the linked account first instead of being realized across the organization.

Once you connect your root/management AWS account, Vantage will profile all member accounts present in the organization. Vantage will be able to show you accrued costs from all member accounts in the organization, as well as Active Resources that are present in that root AWS account.

If you have multiple member accounts and want to view Active Resources present in those accounts, you use the CloudFormation StackSet that will create one role per AWS member account. You're also welcome to skip this step and add/remove individual AWS accounts from your account settings whenever you want.

We recommend using StackSets if you have several accounts you want to connect. Using the StackSet will automate the process for all the accounts in your organizational unit. When connecting your account, if you have at least one member account, you will see instructions, specific to your account, on how to connect your member accounts using StackSets.

StackSet Prerequisites​

To leverage StackSets, you must enable your organization's access to operate a service-managed StackSet. You'll need to enable this setting in the AWS Management Console. If you don't have this setting enabled and attempt to run a StackSet command, you'll see the following error:

An error occurred (ValidationError) when calling the CreateStackSet operation: You must enable organizations access to operate a service managed stack set

For more information, see AWS's instructions for enabling this setting.

Connect with Terraform​

During onboarding, instead of following the CloudFormation process, you can use the Vantage Terraform module. Refer to the Terraform documentation for more information.

Connect by Manually Creating an IAM Role​

If you want to create IAM roles manually or use another tool to manage your infrastructure, you can create the necessary cross-account role.

  1. On the AWS connection page in the Vantage console, click More Connection Options > Connect via AWS IAM Console.
  2. You will be presented with a Trust Relationship and an Inline Policy that is required for the role. Follow the steps provided in the Vantage console to set up the role. Keep this tab open as you will need some submit the ARN of the role to complete the connection.
  3. After creating the role in IAM, return to the onboarding page in Vantage and add the ARN of the created role to the Cross account arn field at the bottom of the connection workflow pop-up window. Then, click Connect to complete the connection.

Next Steps: Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

AWS Data Ingestion Delay​

Vantage creates both an IAM role and a Cost and Usage Report (CUR) integration when onboarding to AWS. While an IAM role is created within a minute, and historical data can be populated almost immediately, it can take AWS up to 24 hours to deliver the first CUR to Vantage. As a result, only partial data will be present until this first CUR is received.

This delay will impact a few features in the Vantage console:

  • Active Resources will initially show only hourly and monthly rates. Once the first CUR is received, you can see actual accrued costs per resource, broken down by cost category and subcategory.
  • Cost Reports will show line-item data per service initially but will not be able to show costs by resource until the first CUR is received.
  • Both Autopilot and Savings Planner are unavailable until the first CUR is received.

Once Vantage receives its first CUR, this functionality will automatically be made available, and Vantage will alert you via email. Ultimately, this is a limitation imposed by AWS, and all Vantage features will become active once the data is received.

Backfill AWS CUR for Previous Reporting Periods​

The first CUR that's sent to Vantage contains only the current month's data. If you want to see historical data in Vantage, you can backfill your CUR for re-ingestion into Vantage.

If you have existing historical CUR files, add a copy of these files to the shared Vantage S3 bucket. Then, email our Support team to ingest the backfilled CUR. By default, Vantage will automatically process CUR files for the current calendar month, but our Support team can also manually process historical CURs if notified.

note

Ideally, these files should be a daily CSV; however, Vantage can also support hourly and/or Parquet formats.

If you do not have this data available, you can contact AWS Support and open a ticket for AWS to backfill your CUR. Follow the steps below.

  1. From your AWS root/management account, use the top search bar to search for and navigate to Data Exports.

  2. A table of data exports is displayed. Observe the Export Name column. You should see the legacy CUR export that was created by Vantage when the integration was set up. Take note of the values in the Export Name and S3 Bucket columns.

  3. Open a ticket with AWS Support to backfill the Vantage export. You can use the sample email template below when creating your request.

    AWS Support Request Template

    Subject: Request for Backfilling AWS Legacy CUR Data Export

    [Insert your organization name] needs help backfilling a legacy CUR Data Export per the below requirements:

    • Please backfill the existing [Insert Vantage legacy CUR Data Export name] report from the [Insert export's S3 bucket name] S3 bucket.
    • We need historical data for the following period: [Insert start date] to [Insert end date].
    • This should be a daily CSV file.

    Once the historical data is successfully backfilled into the above legacy CUR Data Export, please send us a notification or confirmation.

    Thank you,

    [Insert your name]

  4. Once AWS Support completes your request, please email support@vantage.sh to re-ingest the backfilled legacy CUR Data Export.

Update the Vantage AWS Integration​

Occasionally, Vantage will modify the permission sets it uses to access billing and resource data on AWS. When this happens, you can update your integration.

  1. Navigate to the Integrations page of the Vantage console.
  2. From the AWS tile, click Manage.
  3. The Account list is displayed. Click Manage for the cloud account that you want to update. (For AWS organizations with multiple accounts, this will usually be the Management account.)
  4. Click Update Vantage via AWS Console to perform the update, or click More Update Options for command-line and other deployment methods.

Reporting Dimensions​

On AWS Cost Reports, you can filter across several dimensions:

  • Account (AWS account name)
  • Category (e.g., EC2 Data Transfer)
  • Tag/Not Tagged (includes AWS tags and virtual tags created in Vantage for this provider)
  • Subcategory (e.g., EC2 DataTransfer-In-Bytes)
  • Resource (specific resource IDs)
  • Region (e.g., US East (Ohio))
  • Charge Type (e.g., Usage)
  • Billing Account (AWS billing account name)
  • Marketplace (Toggle to show only Marketplace purchases or excluded)
  • Service (e.g., AWS CloudTrail)

View Amazon CloudWatch Metrics on Cost Reports​

You can import Amazon CloudWatch metrics as business metrics to view alongside Cost Reports. See the Per Unit Costs documentation for more information.

VPC Flow Logs: Network Flow Reports​

For network-enabled resources, Network Flow Reports provide visibility by source and destination to the flows within your network that are driving costs. See the Network Flow Reports documentation for information on how to enable these reports and view data transfer costs for AWS services.

- + \ No newline at end of file diff --git a/connecting_azure/index.html b/connecting_azure/index.html index 08039e6e..04de8013 100644 --- a/connecting_azure/index.html +++ b/connecting_azure/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Azure

Vantage integrates with your Azure account using an Active Directory Service Principal. This principal is then assigned access to either management groups or individual subscriptions.

You can connect hundreds of Azure subscriptions to Vantage through the management group method. Any subscriptions that are part of a resource group will be automatically imported.

note

The service principal is granted Reader permissions. It does not have permissions—nor will it ever attempt—to make any changes to your infrastructure.

Connect Your Azure Account​

tip

Instructions are provided below for you to connect via the Azure CLI or the Azure portal.

Connect via the Azure CLI​

Prerequisites​

  • The below commands are run via the Azure CLI. Ensure you have access to Azure CLI and can create service principals and manage their permissions.
  • Create a free Vantage account, then follow the steps below to integrate Azure costs.

Step 1: Create an Azure Service Principal​

Create a service principal using the following command: 

az ad sp create-for-rbac -n "vantage"

You should see output similar to the below output:

{
  "appId": "2d218f0f5-7ad5-4a12-abc7-bad2889d6407",
  "displayName": "vantage",
  "password": "8zkj3~yswKd433U12SHrvp22UoA6tOOOkZ_BYar2",
  "tenant": "1050a480-ef60-43d7-b8db-224aad100b60"
}

Record the appId, password, and tenant as you will enter these credentials into the Vantage console.

Step 2: Grant the Service Principal Permissions​

note

Vantage recommends assigning permissions to a management group that aggregates your subscriptions. By following this recommendation, you do not have to manually assign each subscription.

Grant permissions to the appId from the service principal created above. The scope can be a subscription or management group. Ensure you replace <SERVICE_PRINCIPAL_APP_ID> with the appId. Replace <MANAGEMENT_GROUP_ID> (or <SUBSCRIPTION_ID>) with your management group ID (or subscription ID). 

az role assignment create --assignee <SERVICE_PRINCIPAL_APP_ID> \
  --role Reader \
  --scope "/providers/Microsoft.Management/managementGroups/<MANAGEMENT_GROUP_ID>"

Skip to the Save the Credentials in Vantage section for the steps to complete the connection with Vantage.

Connect via the Azure Portal​

Prerequisites​

  • The below instructions are for connecting using the Azure portal. If you already completed the steps via the Azure CLI, skip to the Save the Credentials in Vantage section. You should have access to set up service principals and grant those service principals permissions.
  • Create a free Vantage account, then follow the steps below to integrate Azure costs.

Step 1: Create a New Application Registration​

  1. From the main page of the Azure portal, search for and navigate to Microsoft Entra ID.
  2. In the left navigation, under Manage, select App registrations.
  3. Click + New registration.
    Expand to view example image
    Azure portal with App Registration menu option selected
  4. The Register an application screen is displayed. For Name, enter vantage.
  5. Leave all other settings as their defaults and click Register.
    Expand to view example image
    Azure portal the Register an application screen and vantage entered as app name
  6. The app details are displayed. Record the Application (client) ID and Directory (tenant) ID to use later.
    Expand to view example image
    Azure portal with the client ID and tenant ID displayed and highlighted

Step 2: Generate a Client Secret​

  1. On the same page, next to the Client credentials field, click Add a certificate or secret. (You can also access the Certificates and secrets screen from the left navigation menu.)
  2. Click + New client secret.
  3. The Add a client secret pane is displayed. For Description, enter a description, such as vantage-secret.
    Expand to view example image
    Azure portal with the Azure client secret window open and a new secreted created called vantage-secret
  4. For Expires, select an expiration option for the secret.
    caution

    If this secret expires, you will need to supply Vantage with a new secret before the expiration date.

  5. Click Add.
  6. The newly created secret is displayed. Copy the secret's Value to add to the Vantage console later. This value will be displayed only one time.

Step 3: Grant the Service Principal Permissions​

note

Vantage recommends assigning permissions to a management group that aggregates your subscriptions. By following this recommendation, you do not have to manually assign each subscription.

  1. From the top navigation, search for and navigate to Management groups. (If you want to assign permissions to a subscription, navigate to Subscriptions.)
  2. Open the management group for which you will be assigning permissions.
  3. On the left navigation, click Access control (IAM).
  4. Click Add role assignment.
    Expand to view example image
    Azure portal with management group window open. The Access control tab is highlighted.
  5. On the Add role assignment screen, select Reader. Then, click Next.
    Expand to view example image
    Azure portal with Reader role highlighted
  6. For Assign access to, select User, group, or service principal.
  7. Click + Select members. The Select members tab is displayed on the right. Search for the vantage app you created before. Select the listed app, then click Select.
    Expand to view example image
    Azure portal with Add role assignment window displayed
  8. Click Next > Review + assign.

Save the Credentials in Vantage​

After you complete the steps for connecting via the Azure CLI or Azure portal, follow the steps below to add the Azure tenant ID, service principal App ID, and service principal password/secret in Vantage.

  1. Navigate to the Integrations page in the Vantage console, and add an Azure integration.
  2. On the Azure integration page, click Add Credentials.
  3. Add the Azure AD Tenant ID, Service Principal App ID, and Service Principal Password you previously obtained, then click Connect Account. Vantage will begin importing your Azure costs.

Next Steps: Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

Azure Cost and Rightsizing Recommendations​

Vantage currently supports cost recommendations for Compute Reserved Instances and Compute Unattached Virtual Hard Disks (disks that have not been attached to a VM in the last 30 days). Each recommendation shows potential savings value, which is something that is not shown in Azure Advisor. Savings estimates are displayed in USD.

Kubernetes and AKS​

Vantage supports Kubernetes cost allocation on Azure, including Kubernetes clusters running on VMs or through AKS. Vantage recommends using the Vantage Kubernetes agent to monitor and ingest Kubernetes costs from Azure.

Azure Reporting Dimensions​

On Azure Cost Reports, you can filter across several dimensions:

  • Resource Group (resource group name)
  • Category (e.g., Virtual Network IP Addresses)
  • Tag/Not Tagged (includes Azure tags and virtual tags created in Vantage for this provider)
  • Subcategory (e.g., Virtual Network Standard IPv4 Static Public IP)
  • Resource (resource ID)
  • Region (e.g., Us East)
  • Charge Type (e.g., Usage)
  • Subscription (subscription name)
  • Marketplace (Toggle to show only Marketplace purchases or excluded)
  • Service (e.g., Virtual Machines)
- + \ No newline at end of file diff --git a/connecting_confluent/index.html b/connecting_confluent/index.html index c45c0ad2..5f841b85 100644 --- a/connecting_confluent/index.html +++ b/connecting_confluent/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Confluent

Vantage integrates with your Confluent account using a Confluent API key and secret to access the Billing API. This endpoint provides structured cost data, broken down by by category (e.g., Kafka or Connect), resource (e.g., Kafka Cluster), and subcategory (e.g., Kafka Storage or Connect Capacity).

Vantage currently supports the following Confluent products:

  • Kafka
  • Connect
  • KSQL
  • Audit Logs
  • Cluster Links
  • Custom Connect
  • Support Cloud

Connect Your Confluent Account​

Prerequisites​

Create a free Vantage account, then follow the steps below to generate a Confluent API key.

info

Confluent requires an OrganizationAdmin role on the service account used in order to access the Billing API. See the Confluent documentation for information on how to add the role to your service account.

The OrganizationAdmin role provides read/write access; however, Vantage will never perform write operations and will only read from the Billing API and Organizations API.

  1. Log in to the Confluent Cloud console.
  2. From the top right of the console, click the hamburger menu.
  3. Under ADMINISTRATION, click Cloud API keys.
  4. Click Create key.
  5. For the scope, select the Granular access tile.
  6. Select an existing service account or create a new one.
  7. Copy the key and the secret to add to Vantage.

Create the Connection​

  1. From the Vantage console, navigate to the Confluent Settings page.
  2. Click Add API Key.
  3. Enter your newly created API key and API secret.
  4. Click Connect Account.
  5. On the Confluent Settings page, you will see your account listed with a Status of Imported.

Costs will be ingested and processed as soon as you add the integration. It usually takes less than 15 minutes to ingest Confluent costs. As soon as the costs are processed, they will be available on your All Resources Cost Report.

note

Confluent data refreshes daily in the Vantage console.

Next Steps: Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

Confluent Reporting Dimensions​

On Confluent Cost Reports, you can filter costs across several dimensions:

  • Category (e.g., Kafka Storage)
  • Tag (virtual tags created in Vantage for this provider)
  • Resource (resource service ID)
  • Charge Type (e.g., Usage)
  • Organization (organization ID)
  • Service (e.g., Kafka)

You can also view credits or discounts for Confluent costs in Cost Reports.

  1. At the top of any Confluent Cost Report, click Settings.
  2. Then, toggle on/off Credits and/or Discounts.

Active Resources​

Confluent Kafka Clusters are synced as active resources and available in resource reports.

- + \ No newline at end of file diff --git a/connecting_coralogix/index.html b/connecting_coralogix/index.html index bb51af60..89e2e48c 100644 --- a/connecting_coralogix/index.html +++ b/connecting_coralogix/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Coralogix

Vantage connects to Coralogix organizations through gRPC API calls. After Vantage is authorized to access your Coralogix organization, Vantage will ingest data using the Coralogix Data Usage Service API endpoints. No access is granted to the Coralogix-connected applications. Vantage can see only usage data related to the connected services.

Vantage supports the Logs, Metrics, and Spans services, as well as the application and subsystem names for your account. The subsystem name typically refers to the environment (e.g., production, development, or staging). The application name typically refers to the name of the service or applications that send your logs, metrics, and traces. Both the subsystem and application names can be customized, so your values may be different.

Connect Your Coralogix Account​

Prerequisites​

Create the Connection​

  1. Log in to the Coralogix dashboard.
    tip

    If you experience issues logging in to your dashboard, your account may be using a different domain. Ensure you use the correct domain to log in to your dashboard.

  2. From the top navigation, expand the Data Flow menu.
  3. Select API Keys.
    Expand to view example image
    The Coralogix Data Flow menu with the API Key option highlighted
  4. Under Alerts, Rules and Tags API Key, click GENERATE NEW API KEY. Click the copy icon next to the key and copy the generated key.
    Expand to view example image
    The Coralogix API Access screen. A box is displayed around the Generate New API Key option.
  5. In the top-right corner of the navigation bar, click your user profile icon. Then, select Organization Admin Console.
    Expand to view example image
    The Coralogix profile menu. A box is displayed around the Organization Admin Console option.
  6. The Organization Admin Console screen is displayed. From the left navigation menu, under Account, select Preferences.
  7. The Account Preferences screen is displayed. In the Change Team name and URL section, copy the part of the domain after your team's name. For example, if your domain is https://test-team.cx498.coralogix.com/, then copy only cx498.coralogix.com.
    Expand to view example image
    The Coralogix Account Preferences screen. A number 1 tooltip is displayed next to the Preferences option. A number 2 tooltip is displayed next to the team name and URL option.
  8. Navigate to the Integrations page in Vantage.
  9. Select Coralogix and select the Connect tab.
  10. At the bottom of the page, click Add API Key.
  11. Enter your previously generated API Key and the Domain you copied.
  12. Enter a Description for this connection. The Description is your team name and is also available in your Coralogix domain URL (e.g., in https://test-team.cx498.coralogix.com/, use test-team).
  13. Click Connect Account.
  14. After you authorize a connection, on the Coralogix Settings page, you will see the status of your connection change to Importing.

Costs will be ingested and processed as soon as you add the integration. It usually takes less than 15 minutes to ingest Coralogix costs. Once costs are processed, they will be available on your All Resources Cost Report.

note

Based on limits imposed by Coralogix, the integration includes 90 days of historical Coralogix usage and cost data. Coralogix data refreshes daily in Vantage.

Next Steps: Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

Coralogix Reporting Dimensions​

On Coralogix Cost Reports, you can filter costs across several dimensions:

  • Service (e.g., Logs, Metrics, Spans)
  • Category (subsystem name)
  • Subcategory (application name)
  • Tag (virtual tags created in Vantage for this provider)
note

Because the Metrics service doesn’t have a subsystem or application name, costs for this service can't be filtered by category or subcategory.

- + \ No newline at end of file diff --git a/connecting_custom_providers/index.html b/connecting_custom_providers/index.html index b8d7fb91..55b927ca 100644 --- a/connecting_custom_providers/index.html +++ b/connecting_custom_providers/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Custom Providers

With the Custom Provider integration option in Vantage, you can upload costs from providers that don’t expose billing APIs, aren’t yet supported by Vantage, or originate from custom systems. You can import costs by providing any CSV that adheres to the schema described below or through the Vantage API. If Vantage eventually provides support for one of your Custom Providers, you will be able to set up the official provider integration alongside your Custom Provider.

FinOps FOCUS Schema​

FOCUS is an open-source schema that standardizes cost and usage billing data across different cloud providers. When you add a Custom Provider in Vantage, you use a CSV template format that is a subset of the FOCUS schema. The fields in this template provide enough detail for Vantage to correctly render costs and perform cost allocation. With just the minimum required fields, Custom Provider costs are available with other Vantage features, such as anomaly alerts, report notifications, and forecasting. See the explainer video below for an introduction to this feature and how FinOps FOCUS is used.

Review CSV Format​

To create a Custom Provider in Vantage, create a CSV file for your data that uses the following format. Add your provider’s cost and usage data to the file. Note that there is a maximum of 10,000 rows and a file size of 2MB allowed. Each time that you upload additional cost data, you will need to create a separate CSV file for that new dataset.

ChargePeriodStart,ChargeCategory,BilledCost,ResourceId,ResourceType,RegionId,ServiceCategory,ServiceName,Tags
2021-01-01,Usage,1.23,resource-id-1,cost_sub_category-1,us-east-1,service-category-1,service-name-1,"{""tag1"":""value1"",""tag2"":""value2""}"

Only the following fields are required:

  • ChargeCategory
  • ChargePeriodStart
  • BilledCost
  • ServiceName
note

If you want to upload amortized costs, then ChargePeriodEnd is also required.

Data Format​

The following table provides details for each field within the template, as well as their Vantage representation on reports.

Column NameRequiredVantage RepresentationData TypeFOCUS Column ID & LinkExamples
BillingCurrencyNoBilling currency costs are displayed inA currency code, like GBP.

If you enter a currency code not available in Vantage, an error is displayed on validation. Check that currency conversion is also enabled. See the Currency Conversion documentation for details. 		BillingCurrencyJPY, AUD, USD
ChargeCategoryNoCharge Type filter and grouping optionValid values are case-sensitive and include:
  • Credit
  • Refund
  • Discount
  • Tax
  • Usage
ChargeCategoryUsage
ChargePeriodStartYesStart date of cost periodDate in YYYY-MM-DD or ISO 8601 formatChargePeriodStart2024-08-25
ChargePeriodEndOnly for amortized costsEnd date of cost periodDate in YYYY-MM-DD or ISO 8601 formatChargePeriodEnd2024-08-25
ConsumedQuantityNoQuantity associated with ConsumedUnitNumericConsumedQuantity598
ConsumedUnitNoUnit of usage associated with ConsumedQuantityAlphanumericConsumedUnitGB
BilledCostYesCost that’s displayedPositive or negative number values accepted; dollar signs and decimal values are also acceptable

All costs are considered to be in USD		BilledCost1245 or -456 or $1.23 or -$1.23
RegionIdNoRegion filter and grouping optionAlphanumericRegionIdus-east-1
ResourceIdNoResource filter and grouping optionAlphanumericResourceIdtask/3 or 123456
ResourceTypeNoSubcategory filter and grouping optionAlphanumericResourceTypeLarge
ServiceCategoryNoCategory filter and grouping optionAlphanumericServiceCategoryTask
ServiceNameYesService filter and grouping optionAlphanumericServiceNameCompute
TagsNoTags filter and grouping optionValid JSON object; array of key/value pairsTags"{""env"":""production""}" for one tag

"{""env"":""prod"",""env"":""dev""}" for multiple tags

Upload Custom Provider File​

Custom Provider files can be uploaded at any time in the console. The above schema adds a timestamp based on the ChargePeriodStart column, so Vantage can place the data in the correct relationship to other costs under a Custom Provider.

note

Users must have Owner permissions to upload Custom Provider files. If you prefer to use the API rather than the Vantage console, see the API section below.

  1. Navigate to the Integrations page in Vantage.

  2. Select Custom Provider. (If you have already added a Custom Provider and are adding another one, ensure you are on the Connect tab.)

  3. Click Select a File and upload your formatted CSV file.

  4. Click Upload Costs.

    1. If your CSV file contains any errors, the Review pop-up window is displayed and indicates where the error occurred. See the Troubleshooting section for details on specific errors.
      Click to view example image
      Error screen for Custom Provider
    2. For error-free files, a message is displayed that indicates your file is okay. Click Review to see the first 25 rows of uploaded data.
      Click to view example image
      Error-free Custom Provider upload
    tip

    You can click Select a File again if you accidentally uploaded the wrong file.

  5. Enter a Name for your Custom Provider. This is the name that will be displayed in report filters. Optionally, enter a Description.

  6. Click Create Custom Provider Integration.

  7. The Manage integration screen is displayed. Initially, the message Importing and Processing will be displayed on this screen. You can click the Import Costs tab if you want to upload additional cost files.

    Click to view example image
    File is processing to be uploaded

  8. Once your Custom Provider is processed, in the Workspace Access section of this screen, select which workspaces this integration is associated with. See the Workspaces documentation for more information.

Costs will be ingested and processed as soon as you add the integration. It usually takes less than 15 minutes to ingest Custom Provider costs. Once costs are processed, they will be available on your All Resources Cost Report. Vantage aggregates uploaded Custom Provider costs to a daily level.

Troubleshoot Custom Provider Uploads​

When you upload a file that contains errors, the Review window displayed and shows the rows where errors were identified. The first 25 rows are displayed. If you have an error in a row that’s not one of the first 25 rows, that row will be displayed at the top, along with all other errors. Some common errors are noted below.

IssueDescriptionSolution
Improper CSV formatThe file format is not a valid CSV or exceeds the 10,000-row limit or 2MB file size max.Ensure the file is a properly formatted CSV, with no more than 10,000 rows or 2MB in size.
Missing required fieldsOne or more required fields (ChargeCategory, ChargePeriodStart, BilledCost, ServiceName) are missing or improperly formatted.

An error message noting which rows are missing required field values will be displayed in the Review window.		Verify that all required fields are present and correctly formatted. See the CSV Format section for details.
Invalid valuesThe file contains invalid values, such as incorrect date formats, invalid numbers, tags that are not formatted as JSON or have missing quotes, or incorrect case-sensitive values for ChargeCategory.

An error message noting which rows contain invalid values will be displayed in the Review window.		Double-check the data in your CSV to ensure dates are in YYYY-MM-DD format, numbers are valid, and ChargeCategory values match the allowed case-sensitive options (e.g., Usage, Credit). See the Data Format table for details.
Improper Vantage permissionsThe user attempting the upload does not have the proper permissions.Ensure you have Owner permissions to upload Custom Provider files. See the Role-Based Access Control documentation for details.
Duplicate file namesYou attempt to upload a new costs import file that has the same name as a previous costs upload file. An error message is displayed indicating you already have a file uploaded with the same name. The new file will overwrite the old file.Ensure each CSV file that you upload is named something different (e.g., cloudflare_costs_8_2024, cloudflare_costs_9_2024).

Steps to Resolve File Issues​

  1. After you’ve identified the issues, reopen your CSV file, correct the errors, and save.
  2. On the Custom Provider upload screen, close the Review window, click Select a File, and upload the corrected version of your CSV file.
  3. After a successful upload, a confirmation message is displayed. You can click Review to verify the first 25 rows of your uploaded data to ensure accuracy.
  4. Follow steps 5–8 in the Upload Custom Provider File section to complete the upload process.

View Custom Provider Costs in Vantage​

Once you have uploaded Custom Provider costs, you can query these costs in other Vantage tools. Your Custom Provider will be included in the Providers list of filters on Cost Reports, Segment Reports, and Saved Filters.

Cost Report for custom provider

If you did not provide any information for a particular filter (e.g., RegionId), then those filters will be displayed as empty.

Cost Report for custom provider with no region filter

Add Additional Imports​

After the initial costs import, you can add additional cost imports.

Important

If you upload a file with the same name as an existing import, your new file will overwrite the original file. Ensure you have different names for each file upload (e.g., cloudflare_costs_8_2024, cloudflare_costs_9_2024).

  1. Navigate to the Integrations page.
  2. Select your Custom Provider.
    Click to view example image
    Manage screen for custom provider
  3. Click the Import Costs tab. Import your new cost file. Review any errors and correct as needed. Once uploaded, your file will be displayed within the Imports section of the Manage tab.

Delete Imported Files​

If you want to delete an imported file, the costs will be removed from your Custom Provider.

  1. Navigate to the Integrations page.
  2. Select your Custom Provider.
  3. In the Imports section of the Manage tab, you can view existing imports along with the date the file was imported and who imported the file. Click the trashcan icon next to an import to remove it. If you delete a CSV, the corresponding data will be deleted from the provider.
    Click to view example image
    Import section for custom provider

Use the API to Add a Custom Provider​

tip

To reference a Custom Provider in VQL queries, navigate to the Integrations page. Use the displayed Provider ID (e.g., custom_provider:accss_crdntl_123a45bfdaf38765).

You can also use the API to create and upload costs for a Custom Provider.

  1. Send a POST request to the /integrations/custom_provider endpoint to create the Custom Provider.

    curl --request POST \
     --url https://api.vantage.sh/v2/integrations/custom_provider \
     --header 'accept: application/json' \
     --header 'authorization: Bearer AUTH_TOKEN' \
     --header 'content-type: application/json' \
     --data '
    {
      "name": "My Custom Provider",
      "description": "Costs for this provider"
    }
    '

  2. On a successful 200 response, a Custom Provider token is returned.

    {
    "token": "<CUSTOM_PROVIDER_TOKEN>",
    "provider": "custom_costs",
    "account_identifier": "My Custom Provider from the API",
    "status": "connected",
    "workspace_tokens": [],
    "created_at": "2024-08-26T14:04:17Z"
    }

  3. Use the token to upload a CSV file via the /integrations/{integration_token}/costs.csv endpoint.

    curl --request POST \
      --url https://api.vantage.sh/v2/integrations/<CUSTOM_PROVIDER_TOKEN>/costs.csv \
      --header 'accept: application/json' \
      --header 'authorization: Bearer TOKEN' \
      --header 'content-type: multipart/form-data' \
      --form csv='@vendor_costs.csv'

  4. If there are any errors, the following 422 response is returned. Fix the errors in your CSV, and upload a new file. 

    {
      "errors": [
        "Row 1: ChargeCategory must be one of the following: Credit, Discount, Fee, Refund, Tax, or Usage",
        "Row 22: Tags must be a valid JSON object",
        "Row 27: BilledCost must be a valid number",
        "Row 31: ChargePeriodStart must be a valid date"
      ]
    }
- + \ No newline at end of file diff --git a/connecting_databricks/index.html b/connecting_databricks/index.html index 7e3e3684..52702c96 100644 --- a/connecting_databricks/index.html +++ b/connecting_databricks/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Databricks

Vantage integrates with your Databricks account through the use of Billable Usage Logs. Vantage provides an S3 bucket for Databricks to periodically deliver usage logs. Databricks delivers cost-only data to the bucket, outlining the Databricks service used, usage in Databricks Units (DBU), and metadata related to workspace, cluster, and any related tags.

Connect Your Databricks Account​

Prerequisites​

Create the Connection​

  1. From the Vantage console, navigate to the Databricks Settings page.
  2. Click Setup Account.
  3. Enter your Databricks Account ID.
    tip

    You can find your Databricks Account ID in the user profile dropdown of the Databricks account console.

  4. Click Connect Account.
  5. On the Databricks Settings page, you will see your account listed with a Status of Pending. Click Pending to complete the connection. Additional steps will be displayed on the Finalize Your Databricks Account Setup page. Keep this page open.

Finalize Your Databricks Account Setup​

Vantage will prepare an S3 bucket to store your Databricks billable usage logs. You will need to configure Databricks to deliver your usage logs to that bucket.

  1. Install or update the Databricks CLI.

  2. Configure authentication for the Databricks CLI:

    info

    The below steps are based on the OAuth user-to-machine (U2M) authentication Databricks documentation.

    Create ~/.databrickscfg. Replace <ACCOUNT_ID> with the value of your Databricks account. (See the Databricks documentation for how to locate your account ID.) Replace the <ADMIN_USERNAME> and <ADMIN_PASSWORD> with your account administrator user's credentials.

    [production]
    host       = accounts.cloud.databricks.com
    account_id = <ACCOUNT_ID>
    username   = <ADMIN_USERNAME>
    password   = <ADMIN_PASSWORD>

  3. Initiate OAuth token management with the following command, replacing ACCOUNT_ID with the account ID you used in the last step:

    databricks auth login --host https://accounts.cloud.databricks.com/ --account-id <ACCOUNT_ID>

  4. Follow the remaining instructions provided on the Finalize Your Databricks Account Setup page in Vantage. These instructions will walk you step by step through creating a storage configuration, creating a credential configuration, and creating a log delivery configuration to finalize the integration.

After completing all the steps above, your Databricks integration status should automatically update from Pending to Importing. Once fully imported, the status will update to Imported. You can view your connection status on the Databricks Settings page.

Databricks generally delivers usage logs once per day.

Next Steps: Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

Custom Pricing in Databricks​

From the Databricks integration page, you can set custom discounts on Databricks SKU groups. Once the discounts are saved, the discounted rate is applied, and Cost Reports are automatically updated to reflect the newly discounted prices. Currently, only AWS is supported. If you are using Databricks on Azure, these discounts are reflected in your Azure billing data, and a Databricks integration is not required.

The following Databricks SKU groups are supported:

  • AWS Jobs Compute
  • AWS Jobs Compute Photon
  • AWS All-Purpose Compute
  • AWS All-Purpose Compute Photon
  • AWS SQL Compute
  • AWS DLT Compute
  • AWS DLT Compute Photon
  • AWS Serverless SQL Compute
  • AWS Serverless Inference
note

At this time, the AWS Security and Compliance SKU group is not supported.

To add custom pricing for SKU groups:

  1. From the top navigation, click Settings.
  2. From the side navigation, click Integrations.
  3. The Connected Providers page is displayed. Select the Databricks integration.
  4. On the Manage tab, select a connected account.
  5. In the Custom Discounts section, click + Add a Discount.
  6. For Service Name, select a SKU group from the list.
  7. For Your Discount, enter a discount as a percentage.
    Click to view example image
    A list of three different Databricks SKU discounts in the console.
  8. To add another SKU group discount, click + Add a Discount. When you are finished, click Save.

Once the discounts are saved, all existing cost data for the integration is re-processed. The status of each billing period is displayed on the integration page. Once the data is processed, any corresponding reports are automatically refreshed. The refresh process may take up to an hour until they are displayed on all reports.

Databricks Reporting Dimensions​

On Databricks Cost Reports, you can filter across several dimensions:

  • Account (account name)
  • Category (e.g., Jobs Compute - Photon)
  • Tag/Not Tagged (includes Databricks tags and virtual tags created in Vantage for this provider)
  • Cluster (e.g., Jobs Computer - <CLUSTER_ID>)
  • Charge Type (e.g., Usage)
  • Service (e.g., All Purpose Compute)
note

The Tag filter contains values like JobID, which can be used to view costs for specific Databricks jobs.

- + \ No newline at end of file diff --git a/connecting_datadog/index.html b/connecting_datadog/index.html index 08bbc82b..a40a63da 100644 --- a/connecting_datadog/index.html +++ b/connecting_datadog/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Datadog

Vantage uses a read-only (scoped to usage_read) Datadog OAuth token. This token is used to pull data from the usage metering endpoint. The usage metering API provides hourly, daily, and monthly usage across multiple facets of Datadog. This API is available to all Pro and Enterprise customers. For Datadog business metrics, Vantage also requires the metrics_read and timeseries_query scopes.

note

Usage is only accessible for parent-level organizations.

For documentation about connecting to Vantage from Datadog, see the Vantage Integration page in Datadog's documentation.

Connect Your Datadog Account​

Prerequisites​

  • When connecting your Datadog account, your user will need access to the usage_read scope to complete the connection. Vantage also requests the metrics_read and timeseries_query scopes for importing Datadog business metrics. See the Datadog documentation for more information on roles.
  • Create a free Vantage account, then follow the steps below to integrate Datadog costs.

Create the Connection​

  1. From the Vantage console, navigate to the Integrations page.
  2. Select Datadog and add a connection.
  3. You will be brought to the Datadog login screen and guided through the Datadog OAuth flow for adding your Datadog account.

After authorizing the connection with Vantage, you will see the status of your connection change to Importing within the Vantage console.

note

Once connected, Vantage will ingest six months of historical Datadog costs. The data is refreshed everyday at 2 AM UTC, but delays, up to 72 hours, may occur.

Next Steps: Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

Update the Datadog Integration​

Sometimes an update is required to use new Vantage features related to Datadog. Navigate to the Manage Integration page for your Datadog integration. If you need to update the integration, the Update Required button is displayed in the Status column. Click the button to access the OAuth integration workflow and reconnect your integration.

Update button for an out-of-date Datadog integration

Datadog Reporting Dimensions​

Within Cost Reports, Vantage will show cost data for at least the following services.

  • APM
  • Application Security Monitoring
  • Audit Trail
  • CI Visibility
  • CSPM
  • Database Monitoring
  • Incident Management
  • Infrastructure
  • Log Management
  • Network Monitoring
  • Observability pipelines
  • RUM
  • Sensitive Data Scanner
  • Serverless Monitoring
  • Synthetic Monitoring
  • Workload Security

The following Cost Report filters are available for Datadog:

  • Organization
  • Category
  • Tag/Not Tagged (see the section below)
  • Subcategory
  • Service

At the Category and Subcategory levels, you can access information such as how much Datadog spend is covered by committed-use discounts or which individual Datadog container is contributing to overall Logging costs.

Datadog Cost Tags (Usage Attribution Tags)​

info

This feature is only available if you have a Datadog Enterprise plan with usage tags enabled.

You can have up to three tag keys per organization enabled for usage attribution in Datadog. Once enabled, Datadog begins breaking down the usage by any number of tag values for these keys. This allows you to see usage for specific services allocated to a specific key/value pair.

The following Datadog services support Datadog cost tags:

  • APM
  • CI Pipeline
  • Fargate
  • Infrastructure Hosts
  • Lambda
  • Logs
  • NPM
  • Synthetic Tests
  • Time Series

To use these tags within Vantage:

  1. Open any Cost Report.
  2. Click Filters, and select Datadog for the provider.
  3. Click New Rule > Tag.

You can also Group By a specific tag key on a Datadog Cost Report. The following filter operators are supported:

  • Tagged with key
  • Tagged with Key where the value: is, is not, contains, does not contain
  • Not Tagged
  • Not Tagged with Key

If you just applied your first Datadog tag key and value, it can take up to 48 hours for the tag to appear in Vantage. Tags are not applied retroactively.

Datadog Pricing in Vantage​

For certain services, Datadog prices based on the 95th to 99th percentile (p95/p99) of usage rather than daily usage. For example, APM is billed on the 99th percentile of the number of hosts you have running at any given time. In Vantage, Datadog costs are realized on the first day of the month. As the month progresses, you might notice that costs retroactively increase or decrease based on your usage.

Because these costs are always realized on the first of the month, when you compare previous periods for services that price on the p95/p99 of usage, you’ll always have the same comparison dates. For services that do not price on p95/p99, Vantage shows costs realized per day, when the accompanying usage data is available.

In the below visual example, a Cost Report is filtered to all Datadog costs. The date grouping is set to Daily. If you select a service row in the table, that service is isolated on the graph, and you can see how the service is priced. In this example, Log Management has accrual data and prices daily; whereas, Containers is priced based on the p95/p99 of usage, and costs are realized on the first of the month.

GIF selecting different Datadog services. When Log Management is selected, costs are displayed for the whole month. When Containers is selected, costs are displayed on the first of the month.

Reporting Dimensions​

On Datadog Cost Reports, you can filter across several dimensions:

  • Organization (organization name)
  • Category (e.g., APM integrated spans)
  • Tag/Not Tagged (includes Datadog tags and virtual tags created in Vantage for this provider)
  • Subcategory (e.g., Virtual Network Standard IPv4 Static Public IP)
  • Charge Type (e.g., Usage)
  • Service (e.g., Database Monitoring)

View Datadog Metrics on Cost Reports​

You can import Datadog metrics as business metrics to view alongside Cost Reports. See the Per Unit Costs documentation for more information.

Datadog Host Costs​

For cloud resources that have the Datadog agent installed, Vantage can associate Datadog per-host fees along with the primary cloud resources from AWS, Azure, and Google Cloud that drive those costs. See the Active Resources documentation for details on how to view these costs.

- + \ No newline at end of file diff --git a/connecting_fastly/index.html b/connecting_fastly/index.html index 126eb1bd..aaeb56fd 100644 --- a/connecting_fastly/index.html +++ b/connecting_fastly/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Fastly

Vantage integrates with your Fastly account through a read-only API token. Fastly API tokens are free for you to create, and adding them to the Vantage console takes only a few minutes.

Connect Your Fastly Account​

Prerequisites​

Create a free Vantage account, then follow the steps below to create a Fastly API token.

  1. Navigate and log in to the Fastly console.
  2. On the API tokens page, re-enter your password if prompted. Then, click + Create Token.
  3. Enter the following token details:
    • For Name, enter something relevant, like VantageReadOnlyToken.
    • For Type, select Automation token.
    • If the Role option is displayed, select Billing.
    • For Scope, select Read-only access (global:read) — Read account information configuration and stats. Ensure all other options remain unchecked. Vantage will never attempt to make changes to your Fastly infrastructure.
    • For Access, select All Services on YOUR_ORGANIZATION_NAME.
    • For Expiration, select Never expire.
      Click to view example token creation form
      Fastly API token form
  4. Click Create Token, and re-enter your password if prompted. Fastly will generate your API token. Copy this token for the next steps.

Create the Connection​

  1. From the Vantage console, navigate to the Fastly Settings page.
  2. Click Add API Token, then paste the API token you just generated.
  3. Click Connect account. Vantage will automatically begin ingesting and visualizing your costs within the Vantage console. It should take about an hour for cost data to populate.
note

Fastly data refreshes daily in the Vantage console.

Next Steps: Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

Fastly Reporting Dimensions​

On Fastly Cost Reports, you can filter across several dimensions:

  • Account (account name)
  • Category (e.g., CDN Data Transfer)
  • Subcategory (e.g., CDN Requests)
  • Resource (service resource ID)
  • Region (e.g., Usa)
  • Charge Type (e.g., Usage)
  • Service (e.g., CDN)
  • Tag (virtual tags created in Vantage for this provider)
- + \ No newline at end of file diff --git a/connecting_gcp/index.html b/connecting_gcp/index.html index cbd35b27..9e4e1045 100644 --- a/connecting_gcp/index.html +++ b/connecting_gcp/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Google Cloud

Vantage uses a service account to integrate with your GCP account. The service account is generated on a per-customer basis. Vantage requests extremely basic and limited permissions for GCP. During the integration process, you will grant the service account access only to the specific BigQuery dataset that contains your billing data.

Prerequisites​

Before you start the integration process, you will need to complete the following prerequisites:

  • Create a project to store your Cloud Billing export data.
  • Create a BigQuery dataset to store your Cloud Billing export data.
  • Enable Cloud Billing export.

See the GCP Cloud Billing export instructions for details on how to complete the above steps. Then, return to this page to complete the rest of the integration process.

note

If your organization enforces domain restrictions, you can add the following Google Cloud organization ID to allow Vantage access: 421856710303. If you instead need the customer ID, use C03l99qsz.

If you have a pre-existing Cloud Billing export set up, ensure your configuration adheres to the requirements below before moving further.

  • Your project is linked to the same Cloud Billing account that the Cloud Billing export is enabled on.
    tip

    We recommend you create a dedicated project to store all Cloud Billing data, rather than using an existing project.

  • Detailed Billing Export is enabled, not Standard Billing Export.
  • The BigQuery dataset and table are deployed to either US (multiple regions in United States) or EU (multiple regions in European Union).
  • If you have multiple Cloud Billing accounts, you will need to enable Cloud Billing exports on each account.
note

If your GCP billing data is typically displayed in a currency other than USD, Vantage will convert it to USD using the currency_conversion_rate field in the Cloud Billing export data.

Create a Connection​

Open a new browser tab, and navigate to the Vantage GCP Settings page. You should see your customer-specific service account displayed at the top of the integration page. Keep this page open.

Step 1: Grant the Vantage Service Account Permission to Access BigQuery and Active Resources​

Back in GCP, navigate to the IAM console, and complete the steps below to grant the Vantage service account permission to access BigQuery. To enable active resources, you must also grant the Viewer role to the Vantage GCP service account. This role allows read-only access to all resources in the project, enabling Vantage to gather data on active resources.

info

For a list of all supported GCP active resources, see the GCP Supported Services documentation.

  1. At the top of the IAM console, select the project that hosts the BigQuery dataset with your Cloud Billing export data.

  2. Configure the following permissions:

    • In the center of the page, under Permissions for project "My Project ABCD", click + GRANT ACCESS.
      Expand to view example image
      GCP project permissions menu
    • In the New principals field, under Add principals, paste the value for your Vantage service account. This value is the one displayed on the Vantage GCP Integration page you opened earlier.
    • In the Role field, under Assign roles, search for and select BigQuery Job User.
    • Click + ADD ANOTHER ROLE.
    • Under Assign roles, click Basic and select the Viewer role from the Role list. This adds the role needed for active resources.
      Expand to view example image
      Grant GCP project access

  3. Click SAVE.

Step 2: Grant the Vantage Service Account Permission to Access the BigQuery Dataset​

Go back to BigQuery, and complete the steps below to grant the Vantage service account permission to access the BigQuery dataset.

  1. At the top of the BigQuery console, ensure the project that you set up to contain your billing data is selected.
  2. In the Explorer panel, select your project to expand it.
  3. Select the three vertical dots next to the dataset name, then click Open. The Dataset info will be displayed on the right. Keep this screen open to later obtain your project ID and dataset name.
  4. Select the three vertical dots next to the dataset name again, then click Share.
    Expand to view example image
    BigQuery share dataset menu

    In this example, project-id-123456 is the project and all_billing_data is the dataset.

  5. On the Share permissions panel that appears on the right, click + ADD PRINCIPAL.
  6. In the New principals field, under Add principals, search for and select the Vantage service account.
    tip

    Copy the full name of your service account from the Vantage console into the search field to search for it.

  7. In the Role field, under Assign roles, search for and select BigQuery Data Viewer.
    Expand to view example image
    Grant BigQuery dataset access
  8. Click SAVE.

Step 3: Add Your GCP Configuration Information to the Vantage Console​

Keep BigQuery open in one of your browser tabs. Go back to the Vantage GCP Integration page to complete the integration process.

  1. At the bottom of the Vantage GCP Integration page, click Add Project Info. A pop-up is displayed, which requires your Billing account ID, the project ID for the project that hosts the BigQuery dataset, and the BigQuery dataset name.
  2. To obtain your Billing Account ID:
    • Go to GCP Billing.
    • Copy the value for your billing account, displayed in the Billing account ID column. It will look something like 1234AB-123456-7ABC12.
      Expand to view example image
      GCP Billing account ID screen
  3. To obtain your Project ID hosting BigQuery dataset and BigQuery Dataset Name:
    • In the Dataset info screen of BigQuery (previously opened in step 3 of the last section), observe the value on the Dataset ID line.
      Expand to view example image
      BigQuery dataset details
    • Copy everything before the period. For example, in project-id-123456.all_billing_data, copy only project-id-123456. Paste this in the Project ID hosting BigQuery dataset field in Vantage.
    • Copy everything after the period and paste it in the BigQuery Dataset Name field in Vantage. (For example, in project-id-123456.all_billing_data, copy all_billing_data.)
      Expand to view example image
      Vantage console configuration
  4. Click Connect Account.
Important

It typically takes a few hours for data to start appearing. Cloud Billing data is added retroactively for the current and previous month when detailed usage cost data is configured. Full data for the current and previous month can take 24–48 hours to fully propagate.

Next Steps: Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

Reporting Dimensions​

On GCP Cost Reports, you can filter across several dimensions:

  • Project (project name)
  • Category (e.g., Cloud Functions Invocations (2nd Gen))
  • Label/Not Labeled (includes GCP labels and virtual tags created in Vantage for this provider)
  • Resource (resource ID)
  • Region (e.g., Us East1)
  • Charge Type (e.g., Usage)
  • Billing Account (billing account ID)
  • Marketplace (Toggle to show only Marketplace purchases or excluded)
  • Service (e.g., Cloud Build)
- + \ No newline at end of file diff --git a/connecting_github/index.html b/connecting_github/index.html index 724a5ef4..590f8040 100644 --- a/connecting_github/index.html +++ b/connecting_github/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

GitHub

Vantage ingests GitHub costs via a Vantage-owned billing manager account that users add to their GitHub Organization or Enterprise. The billing manager account has no access to any source code.

With the Vantage–GitHub integration, you can track costs from the following GitHub services: GitHub Actions, Shared Storage, and Copilot. In addition to these services, Vantage can also pull the underlying compute costs for self-hosted runners that run on a virtual machine, such as an EC2 instance, or in Kubernetes.

How Vantage Integrates with GitHub​

The GitHub integration is completed in the following steps. Detailed integration steps are provided in the next section.

  1. Grant Vantage manage billing:enterprise or read:org access to the GitHub API, allowing Vantage to query the API for billing data returned from the Get usage billing report for an enterprise API endpoint.
  2. Invite an account-specific Vantage email address as a billing manager to either you GitHub Enterprise or Organization.
  3. After the Vantage user is invited, Vantage will confirm the addition of the user to your account within 24 hours.
  4. Add the integration in the Vantage console.

With this approach, Vantage can automatically pull a detailed usage report (CSV) from GitHub. With the information in the detailed usage report CSV, you can see granular usage breakdowns for GitHub Actions, such as build minutes by user, repository, and workflow, as well as the associated infrastructure used to perform the build. This is the most detailed method to provide the information that’s needed for this integration.

The Usage Report CSV contains metadata about every GitHub Actions build for the billing period, such as the user that initiated the build, the organization the user belongs to, the associated source code repository, the workflow name, the runner type, size, and operating system. With this additional metadata, Vantage can help you understand the users or repositories that are using the most minutes. This can help identify anomalies, build/test issues, and over-provisioned runners. Vantage customers can create filters for any of the metadata provided in the CSV.

Connect Your GitHub Account​

Follow the steps in this section to add a Vantage-owned GitHub billing manager account to your Organization or Enterprise. This user can pull cost and usage information from your GitHub account and send it to Vantage.

note

The GitHub billing manager is customer-specific and not shared across other accounts. Per GitHub's documentation: "Billing managers do not use paid licenses in your organization's subscription."

Prerequisites​

The following steps provide information for both Enterprise and Organization accounts.

  • Ensure you have the correct role for adding a member to your account:
    • For Organization accounts, members of the organization's Owners team can add billing manager permissions.
    • For Enterprise accounts, Enterprise owners can invite other people to their enterprise account as billing managers.
  • Create a free Vantage account, then follow the steps below to connect to GitHub.

Create the Connection​

Follow the steps below to add your Enterprise or Organization information, set up the Vantage integration, and invite the Vantage billing manager to your account.

Step 1: Obtain Your Organization or Enterprise Name​

Navigate to GitHub and obtain your Enterprise or Organization name.

For Enterprises, navigate to the Enterprises page on GitHub. Select your Enterprise. Copy the name that's displayed in the URL to use in step 3 (e.g., in https://github.com/enterprises/mycompany, copy only mycompany—all lowercase, no spaces—do not copy the full URL, just the mycompany part).

Step 2: Create a Fine-Grained Access Token​

Create a personal access token for your Enterprise or Organization. These steps are also provided in the GitHub documentation.

  1. Navigate to the Personal Access Tokens screen on GitHub.
  2. Click Generate new token, then click Generate new token (classic).
  3. For Note, enter a description for the token.
  4. Select a token expiration.
  5. For Scopes, select the following scopes based on whether you are an Organization or Enterprise:
    • For Organizations, select the read:org scope.
    • For Enterprises, select the manage_billing:enterprise scope.
  6. Click Generate token and copy the provided token to use in step 3.

Step 3: Add Your Account Information to Vantage​

Navigate to Vantage and follow the steps below to add the information you obtained in the previous steps.

  1. From the top navigation in Vantage click Settings.
  2. On the left navigation, select Integrations. The GitHub integrations page is displayed. Ensure you are on the Connect tab.
  3. Click Add GitHub Account.
  4. Add your Enterprise or Organization name and select your account type. For API key, add your previously generated personal access token.
  5. Click Connect Account.

Step 4: Invite the Vantage Billing Manager to Your GitHub Account​

After you add your initial account information, add the billing manager to your account.

  1. On the integration page, copy provided Vantage billing manager email address. This email address will be associated with the user who's the billing manager on your GitHub Organization or Enterprise.

  2. Navigate to GitHub and follow the steps below for either your Organization or Enterprise.

    note

    These steps are also documented in GitHub's documentation.

    1. Navigate to the Enterprise Admin screen, which will be the following URL, but with your Enterprise's name https://github.com/enterprises/YOUR_ENTERPRISE_NAME/admins.
    2. At the top, click Invite admin.
    3. Paste the Vantage billing manager email you copied earlier.
    4. Select Billing Manager for the role.
    5. Click Send Invitation.

An email will be sent to the Vantage-owned billing manager email address for Vantage to accept your Organization's or Enterprise's invitation. Note that it will take about 24 hours for your invitation to be accepted by Vantage. Once costs are imported, you'll receive an email, and they'll be available on your All Resources Cost Report.

note

GitHub data refreshes daily in Vantage.

Next Steps: Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

GitHub Reporting Dimensions​

On GitHub Cost Reports, you can filter costs across several dimensions:

  • Category (e.g., Actions - Hosted Runner)
  • Tag (Includes the below items and virtual tags created in Vantage for this provider)
    • owner
    • repo
    • username
    • workflow
  • Subcategory (e.g., Actions - Compute - UBUNTU_16_Core)
  • Resource (e.g., Actions - specific Actions workflow)
  • Charge Type (e.g., Usage)
  • Organization (organization name)
  • Service (Actions, Storage, and Copilot)

You can also view GitHub credits in Cost Reports.

  1. At the top of any GitHub Cost Report, click Settings.
  2. Then, toggle on/off Credits.

GitHub Costs Demonstration​

The below video talks about how to get started with GitHub costs and how to use Virtual Tags along with this integration.


- + \ No newline at end of file diff --git a/connecting_kubernetes/index.html b/connecting_kubernetes/index.html index 9c102d71..1aab01ce 100644 --- a/connecting_kubernetes/index.html +++ b/connecting_kubernetes/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Kubernetes

Vantage allows you to see in-cluster costs for Kubernetes clusters, including seeing costs by Container, Service, Namespace and Label. Vantage supports any type of Kubernetes deployment (e.g., EKS, GKE, self-managed). This allows teams to easily understand how their shared clusters are being utilized and how to account for cluster costs across teams and applications.

The Vantage Kubernetes agent is the recommended integration point for ingesting Kubernetes costs into Vantage. Note that a primary provider (e.g., AWS, Azure, or GCP) is required to connect Kubernetes costs.

How the Integration Works​

Vantage looks at pod lifecycle data and the underlying nodes that pods run on. By joining the lifecycle data of each pod (along with the greater of either the reserved or actual CPU/memory prescribed) with the specific rate information of the underlying node, Vantage allocates subcategories of the node (vCPU, memory, GPU, storage, etc.) to the pod. The lifecycle of the EC2 instance is also automatically determined (On-Demand, Spot, Reserved, Savings Plans, EDP, etc.). This allows you to see costs by the following dimensions:

  • By container name
  • By Kubernetes service
  • By Kubernetes namespace
  • By Kubernetes label

Vantage automatically profiles your clusters for all existing Services, Namespaces, and Labels to be available for you in the Vantage console as dimensions for filtering and reporting.

Enable Kubernetes Costs​

To get started, follow the instructions for setting up the Vantage Kubernetes agent.

Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

Reporting Dimensions​

On Kubernetes Cost Reports, you can filter across several dimensions:

  • Account (associated account name)
  • Grouping (includes Kubernetes grouping names and values and virtual tags created in Vantage for this provider)
  • Region (e.g., Westus2)
  • Charge Type (e.g., Usage)
  • Cluster (cluster name)
- + \ No newline at end of file diff --git a/connecting_mongodb-atlas/index.html b/connecting_mongodb-atlas/index.html index 91dd1d24..da93ee38 100644 --- a/connecting_mongodb-atlas/index.html +++ b/connecting_mongodb-atlas/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

MongoDB Atlas

Vantage integrates with your MongoDB account using the Invoices API. To see Active Resources for your MongoDB Atlas account, Vantage uses the Clusters API and the Projects API.

Connect Your MongoDB Atlas Account​

Prerequisites​

  • To create an API key for Vantage to ingest costs, you must be an Organization Owner inside the MongoDB Atlas console.

  • To add the API key to relevant projects to use Active Resource inventories inside Vantage, you must be a Project Owner in the MongoDB Atlas console.

    info

    For more information on user roles in MongoDB Atlas, see the MongoDB Atlas documentation.

Create a free Vantage account, then follow the steps below to integrate MongoDB Atlas costs.

Step 1: Review the Vantage Integration Page​

Navigate to the MongoDB Atlas Settings page in the Vantage console. Then, click Add API Key.

You will need to add your Organization ID, Public API key, and Private API key. Detailed steps for obtaining each of these items are provided below. Leave this tab open so you can go back and populate these fields as you obtain each value.

Add MongoDB information in the Vantage console

Step 2: Obtain Organization ID​

  1. In a new browser tab, navigate to the MongoDB Atlas console.
  2. At the top of the page, next to the Organization dropdown menu, click the gear icon to go to Organization Settings.
    Expand to view example image
    Open Organization Settings in MongoDB Atlas
  3. Your Organization ID will be displayed at the top. Copy the Organization ID. Then, go back to your Vantage browser tab and paste your ID into the Organization ID field.
    Expand to view example image
    Obtain Organization ID in MongoDB Atlas

Step 3: Create an Organization API Key​

Next, you'll create an API key and grant it read-only permissions to your invoices and, optionally, to cluster-level cost data.

  1. From the left navigation menu, click Access Manager.

  2. At the top, click Create API Key.

    Expand to view example image
    View Access Manager in MongoDB Atlas

  3. On the Create API Key screen, configure the following details:

    • For Description, enter a name, like Vantage Integration.
    • For Organization Permissions, select Organization Billing Viewer and Organization Read Only.
    Expand to view example image
    Edit API key permissions in MongoDB Atlas

  4. Click Next. Your public and private keys are displayed. Copy the keys and paste them into the Public API key and Private API key fields in Vantage.

    Expand to view example image
    Copy API keys in MongoDB Atlas
    note

    If your organization requires an IP Access List for access control, you will need to add each of the following IPs to the API Access List section. Add each IP address individually:

    54.87.66.45
    3.95.43.133
    54.162.3.72
    44.199.143.63
    3.218.103.23
    Copy API keys in MongoDB Atlas

  5. At the bottom, click Done.

If you want to have Vantage ingest per-cluster resource data from MongoDB Atlas, then proceed to the next section. Otherwise, back in the Vantage console, click Add Key.

Step 4: Grant Project Access for Active Resources​

  1. On the left navigation menu, select Projects to see your list of Atlas projects. Select your project from the list.

    Expand to view example image
    Open MongoDB Atlas projects

  2. At the top, click Access Manager, then select the project.

  3. Click Invite to Project.

    Expand to view example image
    Invite to project in MongoDB Atlas

  4. Search for and select the Vantage Integration API key to add it to the project.

    Expand to view example image
    Add Vantage key to MongoDB Atlas project

  5. Grant the Vantage Integration API key Project Read Only access. Then, click Invite to Project. Repeat this process for any other projects where you want to see resource-level costs.

    Expand to view example image
    Grant API key read-only access to project

  6. Back in the Vantage console, click Add Key.

Your MongoDB Atlas integration status should automatically update from Pending to Importing. MongoDB Atlas data is refreshed once a day. If you've successfully granted project access for active resources, your Active Resources view will begin populating with cost data.

Next Steps: Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

MongoDB Atlas Reporting Dimensions​

On MongoDB Atlas Cost Reports, you can filter across several dimensions:

  • Project (project ID)
  • Category (Atlas Cluster - Atlas Instance M2)
  • Tag (includes MongoDB tags and virtual tags created in Vantage for this provider)
  • Resource (service resource ID)
  • Charge Type (e.g., Usage)
  • Organization (organization name)
  • Service (e.g., REALM)

Active Resources​

MongoDB Atlas clusters are synced as active resources and available in resource reports.

- + \ No newline at end of file diff --git a/connecting_new_relic/index.html b/connecting_new_relic/index.html index f6b1ee83..9e5f0e8e 100644 --- a/connecting_new_relic/index.html +++ b/connecting_new_relic/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

New Relic

Vantage integrates with your New Relic account using NerdGraph, New Relic's GraphQL API. It accesses the API using an API token.

Connect Your New Relic Account​

Prerequisites​

Create a free Vantage account, then follow the steps below to generate a New Relic API token and obtain your Account ID.

  1. Log in to your New Relic account. Then, follow the instructions in the New Relic documentation to create a User key.
  2. Once you've created a new User key, you will see the key in your API keys list. Click the ellipses next to the key in the list and select Copy key. You will need this value for completing the integration with Vantage.
  3. To obtain your Account ID, follow the instructions provided in the New Relic documentation. Copy the value for your Account ID.

Create the Connection​

  1. Navigate to the New Relic Settings page in the Vantage console.
  2. Click Add Connection.
  3. Paste your New Relic Account ID and New Relic API Key you previously obtained into the provided fields.
  4. Complete the additional fields based on the specific pricing for your account. This can include the per-gigabyte ingestion rate, amount of free ingestion per month, core and full platform user pricing, and any free user seats. For more information on New Relic pricing, see the New Relic documentation.
  5. Click Connect Account. Vantage will automatically begin ingesting and visualizing your costs within the Vantage console, which may take a few minutes.
note

New Relic data refreshes daily in the Vantage console.

Next Steps: Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

New Relic Reporting Dimensions​

On New Relic Cost Reports, you can filter across several dimensions:

  • Account (account name)
  • Category (e.g., New Relic Users - CoreUsers)
  • Tag (virtual tags created in Vantage for this provider)
  • Charge Type (e.g., Usage)
  • Service (e.g., New Relic Ingestion)
- + \ No newline at end of file diff --git a/connecting_open_ai/index.html b/connecting_open_ai/index.html index daef2074..bf4a539b 100644 --- a/connecting_open_ai/index.html +++ b/connecting_open_ai/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

OpenAI

Vantage integrates with your OpenAI account using the OpenAI Usage API endpoint and an API key.

note

The Usage endpoint is currently undocumented, but it provides structured cost data broken down by operation (e.g., Chat Completion or Embedding) and model (e.g., GPT-3.5-turbo).

The following models are supported:

  • Language models: GPT-4, GPT-3.5
  • GPT-3 fine-tuning models: Ada, Babbage, Curie, and Davinci
  • Embedding models: Ada
  • Image models: DALL-E
  • Audio models: Whisper

All models of the following operations are supported:

  • Completions
  • Chat Completions
  • Edits
  • Images
  • Embeddings
  • Audio (Translations and Transcriptions)
  • Fine-tunes
  • Moderations

Prerequisites​

Create a free Vantage account, then follow the steps below to generate an OpenAI API key.

Create a Connection​

  1. Navigate to the API Keys page of the OpenAI console.
  2. In the Default organization section, select the OpenAI organization you want Vantage to connect.
    Click to view example image
    Default Organization section in OpenAI console
  3. Click + Create new secret key.
  4. For Name, add an identifiable name, like Vantage Integration. For Permissions, select All.
    note

    Vantage will never attempt to write to any endpoints using your API key. Vantage only reads from the Usage endpoint.

    Click to view example image
    Create API key modal with a number 1 next to the Create new secret key button and number 2 next to the input field for the key name
  5. Click Create secret key and copy the generated API key.
    Click to view example image
    A sample API key is displayed on the OpenAI API key console
  6. Navigate to the Connect tab of the OpenAI Settings page in the Vantage console. Then, click Add API Token.
  7. The New OpenAI Account modal is displayed. For API key, paste your previously generated API key. For Description, enter any descriptor to identify that you've added this integration, such as your name.
    Click to view example image
    The API key account modal in the Vantage console with sample data added
  8. Click Connect Account. Costs will be ingested and processed once you add the integration. It usually takes less than 15 minutes to ingest OpenAI costs. As soon as costs are processed, they will be available on your All Resources Cost Report.
note

OpenAI data refreshes daily in the Vantage console.

Next Steps: Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

OpenAI Reporting Dimensions​

On OpenAI Cost Reports, you can filter across several dimensions:

  • Organization
  • Operation (e.g., Chat and Completions)
  • Model (e.g., GPT-3.5)
- + \ No newline at end of file diff --git a/connecting_oracle/index.html b/connecting_oracle/index.html index a6dd1139..fb184b26 100644 --- a/connecting_oracle/index.html +++ b/connecting_oracle/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Oracle Cloud

Vantage uses a read-only IAM user and API key to read from a Cost and Usage Reports object storage bucket. When connecting to Oracle, you will be required to create a Vantage-specific IAM user and upload a generated RSA public key to that user. That user must then be granted access to read objects from the Cost and Usage Report tenancy.

Connect Your Oracle Cloud Account​

Prerequisites​

Create the Connection​

  1. Navigate to the Oracle Settings page in the Vantage console.
  2. A set of instructions is displayed, which will walk you through how to create an IAM user and group, add an IAM policy, and obtain your Tenancy ID and User ID. This series of commands grants Vantage permission to ingest cost and usage information from your Oracle Cloud account through an API key. All commands need to be performed using the Oracle Cloud Infrastructure CLI.
  3. At the bottom of the setup screen, click Add Connection. Paste your Tenancy and Vantage User ID. Then, select your Home Region.
  4. Click Connect Account. Costs will be ingested and processed as soon as you add the integration. It usually takes less than an hour to ingest Oracle costs.
note

Oracle generally delivers usage logs once per day.

Next Steps: Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

Oracle Cloud Reporting Dimensions​

On Oracle Cost Reports, you can filter across several dimensions:

  • Compartment
  • Category (e.g., MYSQL - MySQL Database Service - Standard - AMD E4 - Memory)
  • Tag/Not Tagged (includes Oracle tags and virtual tags created in Vantage for this provider)
  • Resource (resource ID)
  • Region (e.g., Us Ashburn 1)
  • Charge Type (e.g., Usage)
  • Tenancy (tenancy OCID)
  • Service (e.g., MYSQL)
- + \ No newline at end of file diff --git a/connecting_planetscale/index.html b/connecting_planetscale/index.html index 8c8981e4..d0645020 100644 --- a/connecting_planetscale/index.html +++ b/connecting_planetscale/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

PlanetScale

Vantage integrates with PlanetScale billing data via the PlanetScale Invoices API. Vantage connects to PlanetScale organizations through an OAuth flow, handled within the PlanetScale app. Vantage supports multiple PlanetScale organization integrations. All organizations are ingested after you connect via the OAuth flow and do not need to be individually added. After authorizing Vantage access to your PlanetScale organizations, Vantage will begin to ingest data using the PlanetScale Organizations, Invoices, and Databases endpoints.

The required PlanetScale scopes to connect are:

  • User access
    • read_organizations
  • Organization access
    • read_organization
    • read_invoices
    • read_databases

No access is granted to the actual databases themselves. Vantage can see only metadata related to the databases.

The Invoices endpoint provides structured cost data, broken down by service (e.g., Database or Support), category (e.g., PS-10, PS-20), and resource (e.g., the specific database). All credentials are encrypted.

Vantage supports Databases and Support services, as well as the following services for Branches:

  • PS-10
  • PS-20
  • PS-40
  • PS-80
  • PS-160
  • PS-320
  • PS-400

Connect Your PlanetScale Account​

Prerequisites​

Create the Connection​

  1. From the Vantage console, navigate to the Integrations page.
  2. Select PlanetScale, then click Connect PlanetScale Account.
  3. You will be brought to the PlanetScale login screen. Log in to your account and select the organizations you want to connect with.
  4. Click Authorize access.
  5. After you authorize a connection, on the PlanetScale Settings page, you will see the status of your connection change to Importing.

Costs will be ingested and processed as soon as you add the integration. It usually takes less than 15 minutes to ingest PlanetScale costs. Once costs are processed, they will be available on your All Resources Cost Report.

note

PlanetScale data refreshes daily in Vantage.

Next Steps: Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

PlanetScale Reporting Dimensions​

On PlanetScale Cost Reports, you can filter costs across several dimensions:

  • Category (e.g., PS-10, PS-20)
  • Tag (virtual tags created in Vantage for this provider)
  • Resource (e.g., database name)
  • Charge Type (e.g., Usage)
  • Organization (organization ID)
  • Service (e.g., Database or Support)

You can also view credits or discounts for PlanetScale costs in Cost Reports.

  1. At the top of any PlanetScale Cost Report, click Settings.
  2. Then, toggle on/off Credits and/or Discounts.

Active Resources​

PlanetScale databases are synced as active resources and available in resource reports.

- + \ No newline at end of file diff --git a/connecting_snowflake/index.html b/connecting_snowflake/index.html index 3d085d33..10fd1faa 100644 --- a/connecting_snowflake/index.html +++ b/connecting_snowflake/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Snowflake

Vantage integrates with your Snowflake account through a secure, read-only user that has access to Snowflake usage tables. Optionally, you can create a specific schema for the Vantage user.

Vantage requires read-only access to the following tables:

note

As a best practice, it is suggested you create a schema specifically for the vantage user. Note, however, that this is optional. See the steps below for details on how to create this schema.

Connect Your Snowflake Account​

Prerequisites​

Create a free Vantage account, then follow the steps below to integrate Snowflake costs.

Snowflake IP Allowed List​

If your Snowflake cluster uses an IP allow list for access control, you will need to add the following IPs to that allowed list:

54.87.66.45
3.95.43.133
54.162.3.72
44.199.143.63
3.218.103.23

Snowflake Schema for Vantage​

After creating the below schema, you can add only the needed views to that schema and grant the vantage user access to the schema.

info

The below commands are based on the Snowflake documentation.

  1. In Snowflake, create a user named vantage, a role named vantage, and a warehouse named vantage. Grant the necessary permissions. Ensure you replace the password placeholder with a strong password for the vantage user.

    use role accountadmin;
    create database vantage;
    create role vantage;
    create user vantage;
    grant role vantage to user vantage;
    grant role vantage to role accountadmin;
    create warehouse vantage;
    grant all on warehouse vantage to role vantage;
    alter user vantage set DEFAULT_WAREHOUSE=vantage, DEFAULT_ROLE=vantage;
    alter user vantage set password='<A STRONG PASSWORD>';

  2. Set up the Vantage-specific schema to read billing and usage data from your account.

    use warehouse vantage;
    create view VANTAGE.PUBLIC.QUERY_HISTORY as select * from SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY;
    create view VANTAGE.PUBLIC.WAREHOUSE_METERING_HISTORY as select * from SNOWFLAKE.ORGANIZATION_USAGE.WAREHOUSE_METERING_HISTORY;
    create view VANTAGE.PUBLIC.USAGE_IN_CURRENCY_DAILY as select * from SNOWFLAKE.ORGANIZATION_USAGE.USAGE_IN_CURRENCY_DAILY;
    grant usage on schema vantage.public to role vantage;
    grant usage on database vantage to role vantage;
    grant select on all views in schema VANTAGE.PUBLIC to role vantage;

  3. Test your setup.

    use role vantage;
    select * from vantage.public.query_history limit 1;

  4. Navigate to the Snowflake Settings page in the Vantage console to add a new Snowflake connection. Then, click Add Connection.

  5. Add the following information to the form:

    • Server URL: In the format <account_identifier>.<region>.snowflakecomputing.com.
    • Database: The name of the database the usage views are in (e.g., vantage).
    • Schema: The name of the schema the usage views are in (e.g., public).
    • Username and Password set for the vantage user.

  6. Click Connect Account. The status of your account will change to Importing.

Costs will be ingested and processed immediately, but it may take several hours to populate all Vantage tools depending on the query volume of your warehouse. Vantage will refresh at least once daily for Snowflake.

Next Steps: Manage Workspace Access​

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

Troubleshoot Snowflake Errors​

Snowflake occasionally makes changes to the queries/tables that get used for cost and usage attribution, causing the views in Vantage to then be based on an old query. You may see an error in the Vantage console, similar to the below error:

View definition for 'VANTAGE.PUBLIC.QUERY_HISTORY' declared 66 column(s), but view query produces 77 column(s).

To fix the issue, replace the three Vantage views in Snowflake and ensure the vantage user is granted permission on those views.

note

After you've completed the below steps, contact support@vantage.sh to reimport your Snowflake data.

USE WAREHOUSE vantage;
CREATE OR REPLACE VIEW VANTAGE.PUBLIC.QUERY_HISTORY as select * from SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY;
CREATE OR REPLACE VIEW VANTAGE.PUBLIC.WAREHOUSE_METERING_HISTORY as select * from SNOWFLAKE.ORGANIZATION_USAGE.WAREHOUSE_METERING_HISTORY;
CREATE OR REPLACE VIEW VANTAGE.PUBLIC.USAGE_IN_CURRENCY_DAILY as select * from SNOWFLAKE.ORGANIZATION_USAGE.USAGE_IN_CURRENCY_DAILY;
GRANT USAGE ON SCHEMA vantage.public TO ROLE vantage;
GRANT USAGE ON DATABASE vantage TO ROLE vantage;
GRANT SELECT ON ALL VIEWS IN SCHEMA vantage.public TO ROLE vantage;

Snowflake Reporting Dimensions​

On Snowflake Cost Reports, you can filter across several dimensions:

  • Account (account name)
  • Category (e.g., Data Cloud Data Transfer)
  • Metadata (e.g., environment is staging)
  • Region (e.g., AWS Eu West 1)
  • Organization (organization name)
  • Service (e.g., Data Cloud)
  • Tag (virtual tags created in Vantage for this provider)
  • Charge Type (e.g., Usage)

Active Resources​

Snowflake queries are synced as active resources and available in resource reports.

- + \ No newline at end of file diff --git a/cost_anomaly_alerts/index.html b/cost_anomaly_alerts/index.html index 98a43b62..6bee62d4 100644 --- a/cost_anomaly_alerts/index.html +++ b/cost_anomaly_alerts/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Anomaly Detection

Cost anomalies notify teams of excess costs and help engineers fix misconfigurations or other problems before they become very expensive. All costs present in a Cost Report will be analyzed for anomalies, and all Cost Reports can be configured to send alerts. You can also configure alerts to be sent for detected anomalies.

Alerts can be sent to any number of email addresses. You can select any of your team members with a Vantage account, and add their email to the alert. You can also send alerts via Slack or Microsoft Team channels. If there are new anomalies for that day, they will be sent as a summary once per day.

note

At this time, you cannot configure an alert for a specific resource; however, you can create a Cost Report filtered to a specific tag or label and configure an alert for that report.

How Anomaly Detection Works​

A machine learning model is trained on every cost category for every service of a Cost Report. If a cost for a specific date falls outside of the expected bounds, it is considered an anomaly. Vantage also filters out very low dollar value cost anomalies to reduce alerting noise. Anomalies are detected for each service at the category level. For example, with Amazon EC2, anomalies are detected for Data Transfer or Compute Instance.

tip

To get started with cost anomaly detection and alerts, you can also view a video demo on Vantage University 🎓.

View Cost Anomalies​

To view cost anomalies, navigate to any Cost Report and select the Anomalies tab.

GIF of a Cost Report with the Anomalies tab opened

tip

Anomalies are considered Active if they have occurred in the past seven days. Once this time window passes, they move to an Archived state.

Anomaly alerts are sent only for the first time they are detected. If an anomaly persists for multiple days in a row, Vantage will not send alerts after the first day. Historical anomalies are available to view for a Cost Report, and the Anomaly Detected date will be the first day the anomaly occurred.

Take Action on Anomalies​

  1. To view more information about a specific alert, select the link in the Category column.
  2. The alert is displayed on the corresponding Cost Report. The specific day where the alert was surfaced is highlighted. At the top right of the graph, click Manage Anomaly.
  3. Select one of the following actions:
    • Create an Issue: Select this option to create an issue. A new tab is displayed with a new issue. The issue description will contain a link to the Cost Report where the anomaly was detected. This issue can be assigned to yourself or another teammate to resolve later. See the visual example below for how to create an issue.
    • Mark as Archived: The anomaly will be displayed as Archived in the anomalies list.
    • Ignore: The anomaly will be removed from the anomalies list. The Ignore Anomaly pop-up is displayed where you can provide feedback to Vantage on why you are ignoring the anomaly.
GIF of a creating an issue for an Anomaly

Configure Cost Anomaly Alerts​

note

You can configure alerts to be sent via email, Slack, or Microsoft Teams. If you want to use Slack or Teams, you will need to configure the corresponding integration with Vantage. See the Slack or Microsoft Teams integration documentation for Cost Report notifications. Once you have completed the integration steps, complete the below instructions to configure anomaly alerts.

To receive alerts for any detected cost anomalies:

  1. From the top of the anomalies list, click Configure Alert.
  2. Select any email recipients you want to send the alert to. If you have Slack or Microsoft Teams configured, the Slack channels or Microsoft Teams channels fields are displayed.
  3. Enter an Alert Threshold. You'll receive an alert only if this threshold is reached.
  4. Click Save.

To add or remove recipients or change the threshold, click Configure Alert and make those updates.

Alert Thresholds
- + \ No newline at end of file diff --git a/cost_recommendations/index.html b/cost_recommendations/index.html index 0b44adf7..b282ac37 100644 --- a/cost_recommendations/index.html +++ b/cost_recommendations/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Cost Recommendations

Vantage monitors your connected providers and shows cost recommendations as your infrastructure evolves and changes. You can implement these recommendations to lower your bill.

note

Cost recommendations are currently available for AWS, Azure, GCP, Datadog, and Kubernetes.

Types of Recommendations​

tip

To get started with cost recommendations, you can also view a video demo on Vantage University 🎓.

Your available recommendations depend on what services and resources are running in your account. In general, there are three types of recommendations:

  • Cloud-provider recommendations: Gathered from your connected provider and further enriched in Vantage
  • Custom-built recommendations: Created by Vantage
  • Cross-provider recommendations: Suggests where a service from another provider could be used
A list of cost recommendations in the console

View Cost Recommendations​

  1. From the top navigation, click Recommendations.
  2. The following columns are displayed: Service, Potential Savings, and Description.
    tip

    To filter recommendations by provider, open the Show All menu at the top right of the table and select a provider.

  3. In cases where actions are recommended for specific resources, such as adding lifecycle policies, the View resources button is displayed. Click this button to see a list of the affected resources.
  4. If you no longer want to view a recommendation, click the Archive icon (looks like an arrow pointing down). The recommendation will be moved to the Archived tab.

View Recommendations during a Trial​

If you are currently on a trial, the specific recommendations are blurred; however, the total amount of potential savings is displayed. After you activate a Vantage subscription, these recommendations are fully visible. As you make changes to your infrastructure, the recommendations are automatically updated. Recommendations are refreshed once a day.

Provider-Specific Recommendations​

The recommendations that are available for AWS, Azure, GCP, Datadog, and Kubernetes in Vantage are based on the granularity of data exposed by each provider. Notes for these providers are provided below.

AWS Recommendations​

Recommendation TypeDescription
Savings PlansVantage will look at your AWS infrastructure on a weekly basis and provide Savings Plan recommendations tailored to your actual usage of EC2, Fargate, and Lambda.
Reserved InstancesVantage will recommend Reserved Instances for services, like RDS, ElastiCache, Elasticsearch, and more with specific Reserved Instances to purchase.
Stranded resourcesVantage will look for stranded resources, such as EBS volumes, IP addresses, and more, to ensure you've cleaned up everything you're not using.
Storage optimizationsVantage will look at EBS volumes you're using to provide optimization recommendations as well as S3 object type usage to recommend actions, like changing EBS volumes or enabling S3 Intelligent-Tiering.
Networking optimizationsVantage will look for networking optimizations especially for CloudFront and S3.
Lifecycle policiesVantage will profile for services that can auto-delete data to reduce costs and expected savings noted.
EC2 rightsizing opportunitiesVantage will identify rightsizing opportunities and provide specific reasons to rightsize EC2 instances, such as over-provisioned CPU. See more information below.

EC2 Rightsizing Recommendations​

If you have EC2 instances that are over-allocated in terms of vCPU and GB of RAM, you may be paying more than needed per instance. Rightsizing recommendations can help you save significantly, by identifying rightsizing opportunities and providing specific reasons to rightsize, such as over-provisioned CPU.

Each recommendation includes potential savings as well as the number of instances identified for rightsizing.

  1. On the Cost Recommendations screen, click View Resources to view each identified EC2 instance that is recommended for rightsizing.
  2. Select a resource from the list.
  3. The Active Resources screen is displayed. Select the Rightsizing tab. The tab includes a recommended size for migration (e.g., “Migrate to m5.large”), a list of associated reasons (e.g., “CPU over-provisioned”), if available, and the potential monthly savings.
  4. Click Compare Pricing to explore an instance pricing comparison via ec2instances.info. This pricing comparison evaluates the current instance type used against the proposed instance type from the recommendation.
An EC2 rightsizing recommendation with a button to compare instance sizes in the console

Azure Recommendations​

A list of Azure-related recommendations in the console

Recommendation TypeDescription
Compute Reserved InstancesSuggestions for instances with on-demand usage that could be converted to Reserved Instances for better savings.
Compute unattached virtual hard disksDisks that have not been attached to a VM in the last 30 days.
Compute Savings PlansVantage will identify potential savings from purchasing Compute Savings Plans.
Virtual Machine (VM) RightsizingVantage will suggest VM instances that can be rightsized to offer savings. Suggestions will be made available through the Active Resource page's Rightsizing tab as well.
Blob Storage Reserved InstancesVantage will suggest purchasing Reserved Instances that can save on Blob v2 and Datalake storage Gen2 costs.
SQL PaaS DB Reserved InstancesVantage will suggest purchasing Reserved Instances that can save on your pay-as-you-go costs.
Files Reserved InstancesVantage will suggest purchasing Reserved Instances that can save on your on-demand costs.
SQL DB Reserved InstancesVantage will suggest purchasing Reserved Instances that provide a reduced rate.
App Service Reserved InstancesVantage will suggest purchasing Reserved Instances that provide a reduced rate.
Cosmos DB Reserved InstancesVantage will suggest purchasing Reserved Instances that provide a reduced rate.

GCP Recommendations​

A list of GCP-related recommendations in the console

Recommendation TypeDescription
Rightsizing recommendationsShow whether compute resources are overprovisioned. For example, We have identified 2 Compute instances for rightsizing that offer savings. See the next section for details on viewing resource-specific rightsizing recommendations.
Commitment recommendationsCommitment-related recommendations for resource-based commitment discounts. For example, We have found that your account could save by purchasing Compute Commitments.

GCP Compute Rightsizing Recommendations​

If you have GCP Compute instances that are overprovisioined, rightsizing recommendations are available. Recommendations are also provided in the case of idle instances.

Each recommendation includes potential monthly savings as well as the number of instances identified for rightsizing.

  1. On the Cost Recommendations screen, click View Resources to view each identified resource that is recommended for rightsizing.
  2. Select a resource from the list.
  3. The Active Resources screen is displayed. Select the Rightsizing tab. The tab includes a recommended size for migration (e.g., “Migrate from e2-medium to e2-small."). Any available idle resource recommendations are also displayed (e.g., "Stop idle VM idle-instance-1."). The potential monthly savings for taking action on these recommendations are also displayed.
A set of GCP rightsizing recommendations in the console

Datadog Recommendations​

A list of Datadog-related recommendations in the console

For Datadog, Vantage provides recommendations about making commitments for Datadog services where committed use discounts are offered. These recommendations are based on your actual usage of Datadog services to assist with making the right commitment.

Kubernetes Rightsizing Recommendations​

Without proper resource allocation, Kubernetes clusters can become overprovisioned, leading to wasted resources and idle costs. Vantage provides Kubernetes rightsizing recommendations to help you identify affected resources.

These recommendations are focused on managed workloads within Kubernetes clusters and do not provide rightsizing recommendations for the Kubernetes nodes themselves.

tip

For a full guide on understanding rightsizing and how to rightsize Kubernetes resources, see the following article in the Cloud Cost Handbook.

View Kubernetes Rightsizing Recommendations​

note

Rightsizing recommendations require version 1.0.24 or later of the Vantage Kubernetes agent. See the Kubernetes agent documentation for information on how to upgrade the agent. Once the upgrade is complete, the agent will begin uploading the data needed to generate rightsizing recommendations. After the agent is upgraded or installed, recommendations will become available within 48 hours. This step is required to ensure there is enough data to make a valid recommendation. Historical data is not available before the agent upgrade, so it is recommended that you recognize cyclical resource usage patterns, such as a weekly spike when you first review recommendations.

  1. From the Cost Recommendations screen, click View resources to view each identified Kubernetes workload that is recommended for rightsizing.
  2. Select a workload from the list. The workload is displayed within the Active Resources screen.
  3. Select the Rightsizing tab. A section for each container that’s identified for rightsizing is included.
    • Each recommendation includes a high-fidelity graph of CPU and RAM used within the container in the past month, the average and maximum usage for mCPU and memory, and recommendations for how to rightsize your configuration. The chart includes a per-day average usage. The table provides a 30-day average and 30-day average max usage.
      note

      mCPU refers to milliCPU, which is a fractional representation of CPU, where 1 CPU is equal to 1000 milliCPU. Current Configuration comes from the currently configured requests for the pod template within the controller spec. This is collected by the Kubernetes agent hourly and updated when the cost data is imported, roughly once per 24 hours.

    • The Potential Monthly Savings are also provided to indicate your estimated savings once these recommendations are implemented on your Kubernetes resources.
The Kubernetes Rightsizing UI with a sample recommendation displayed

How Vantage Calculates Kubernetes Rightsizing Recommendations​

Vantage takes the following steps to calculate Kubernetes rightsizing recommendations.

  1. Identify controllers with low efficiency.
    • Controllers running below an efficiency level of 80% over the last 30 days are identified.
    • Efficiency is calculated as the percentage of the average CPU or memory utilization divided by the amount allocated for that resource.
  2. Determine the target amount for rightsizing.
    • The target amount is calculated by dividing the average usage by the efficiency target of 80%. For example, if your average usage is 100, and the efficiency target is 80%, then Vantage determines the right size to be (100/.8), or 125.
    • This target amount might exceed the maximum observed usage, which is acceptable to provide room for potential spikes in resource usage. This also prevents containers from being terminated due to resource exhaustion.
  3. Calculate the potential savings.
    • Savings is the difference between current configuration and target configuration multiplied by a standard hourly base rate.
    • For Deployments and StatefulSets, these savings are further multiplied by the number of replicas configured for each controller.
    • The calculated amount of savings must be at least $5 to be considered for rightsizing recommendations.

If you make a configuration change to a pod, the Vantage Kubernetes agent will upload the new configuration for the pod within the hour that it is available. Vantage reruns recommendations once the next Kubernetes ingestion is processed, which is every 24 hours.

- + \ No newline at end of file diff --git a/cost_reports/index.html b/cost_reports/index.html index d150912e..f0b30556 100644 --- a/cost_reports/index.html +++ b/cost_reports/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Cost Reports

By default, Vantage provides you with a Cost Report, named All Resources, that will show you all costs across all your connected cloud service accounts.

You can create as many Cost Reports as you'd like and filter your costs across several dimensions. As you create Cost Reports, they will be displayed on the Overview page. Each report will automatically generate a forecast.

tip

To get started with Cost Reports, you can also watch these video demos on Vantage University 🎓.

Create a Cost Report​

  1. From the top navigation, click Cost Reporting.

  2. On the left menu, select Cost Reports.

  3. On the top right, click + New. A new, unfiltered Cost Report is displayed.

  4. From the top left of the graph, click Filters.

  5. Click + Add a Filter and select your desired filter criteria.

  6. From the top right of the graph, use the date picker to select the date range for the report. You can select a date range that encompasses both previous and future dates, up to 6 months ahead. For more information on future forecast dates, see the Forecasting documentation.

    By default, the Cost Report compares the selected dates to the same previous period. For example, the default comparison date for March 12–March 18 is February 12–18. To select a custom comparison:

    • Open the date picker menu.
    • In the left column, select Custom.
    • On the calendar section, under Custom, select the first date period field, then hover your mouse over the calendar to highlight and select a date range. (The current month is selected by default.)
    • Under Comparing to Previous Period, select the first date period field and select a custom comparison period.
    • Click Apply.
      Click to view example video

      In this example, the user makes a custom comparison to change the comparison from March and April to February and April.

      GIF that shows a user opening the date menu. The user selects a current period and then selects the custom option to choose a custom comparison date period.

  7. Select one of the following date bins:

    • Cumulative: Displayed as a line, pie, or area chart on the graph, along with a forecast for line and area charts, if available
    • Daily, Weekly, or Monthly: Displayed as a bar, line, or area chart, with date ranges binned on the bottom axis and a forecast, if available

You can perform additional filter and analysis operations on your Cost Report. See the following sections for additional instructions:

Save a Cost Report​

After you apply all desired filters to the report, you can save your changes and name the report.

  1. From the top right of the graph, click Save As New to create a new Cost Report with your changes, or Save Changes to modify the current report.
  2. Enter a name, then click Save.
    note

    If you update the date range, date bin (e.g., Last 30 Days), or grouping, you can also permanently save these changes. Once saved, the new date range, date bucket, and grouping will persist on the Overview page. If you save a report that includes only changes to filter sets, the report will be displayed on the Overview page with the last six months of costs.

tip

If you want to create a new report based on an existing report, open the existing report and click Save as New on the top right of the screen. You can then further refine your report criteria on the new report.

Organize Cost Reports​

Cost Report Folders​

You can organize your Cost Reports in folders and separate them by team or group. See the Folders documentation for more information.

Dashboards​

Cost Reports can be displayed as a group on a dashboard. The dashboard has options to display all reports by the same date range. See the Dashboards documentation for more information.

Anomalies, Forecasts, and Annotations​

Cost Reports have several other features, including anomaly detection, forecasts, and annotations. See the linked documentation for more information about these features.

Filter Cost Reports​

On the Filters menu, click Select a provider and choose from any of your connected providers (AWS, Azure, etc.). Costs are filtered to all costs for the selected provider. Within the table, costs are grouped by provider service (e.g., Amazon Relational Database Service), in descending order of Accrued Costs.

GIF of selecting a provider filter for GCP and sorting the table by cost in the console

To view available filter options, click New Rule. A list of filter options is displayed (e.g., Account or Resource). Filter options vary per provider.

Each filter includes options for exact matching and fuzzy matching. For example, in the image below, you can select is, is not, contains, does not contain, starts with, and ends with for the Resource filter. This set of options can vary per selected filter. Select a matching option, then select a filter value (e.g., where Service is Amazon Relational Database Service + Amazon Elastic Cloud - Compute)

Selecting matching criteria for a filter in a Cost Report

To continue filtering the report, perform any of the following actions:

  • To add another value for that filter, click the + icon next to the first value.
  • To remove a selected filter value, click the trashcan icon.
  • To add more filter criteria, click New Rule. The graph is updated to display costs that match the first filter criteria and the second filter criteria.
  • To add a separate filter set, click + Add a Filter. You can also use this option to add costs from another provider. The graph is updated to display costs that match the first filter set or the second filter set.
  • To remove a filter set, click the three dots (...) on the top right of the filter set, then click Delete.

Category and Subcategory Cost Filters​

Each service typically has multiple underlying category and subcategory costs. For example, you have AWS as a connected provider. You can filter by several subcategories, like the amount of storage you've used or the amount of egress traffic for retrieving S3 objects as well as for the actual HTTP requests you make to query for S3 objects.

Similarly, Azure and GCP also support category and subcategory costs on Cost Reports. For example, with Azure, if you filter by Subcategory for the Service of Virtual Machines, you can then filter for individual Azure VMs. In GCP, the labels you apply to resources will be displayed as subcategories.

To drill down in the costs table to view Category costs:

  1. Add a filter for a provider, like AWS. The table below the graph is updated to show costs grouped by service.
  2. A few icons are displayed next to each listed service. Click the Costs by Category icon (looks like a set of squares; see the example below). A full breakdown of all subcategory costs that make up the main AWS service cost is displayed.
GIF of filtering RDS costs by category and sorting the table in the console

Per-Resource Cost Filters​

For certain providers, like AWS, you can view individual resources.

  1. Add a filter for a provider, like AWS. The table below the graph contains costs grouped by service.
  2. Next to each listed service, observe a few icons. Click the Costs by Resource icon (looks like a set of different shapes). A full breakdown of all resource costs that make up the main AWS service is displayed.

In the below example, two RDS instances are present in the account. The table displays how much each instance is driving in costs—without the need for any additional tagging.

Example of Per Resource Costs

You can also view the Category and Subcategory costs on a per-resource basis. In the previous example, to view a breakdown of costs for the RDS instance named core-production-primary-01, click the Costs by Category icon (looks like a dollar sign—$). Costs are now displayed by resource, within a category, for a specific service.

Example of a Single Resource Costs

Percent-Based Cost Allocation​

With percent-based cost allocation, you can filter Cost Reports to show back shared resources, like support costs or multi-tenant databases, to the team or department that uses them. As filters are set in a Cost Report, Vantage will query for costs that meet all those conditions.

To set percent-based cost allocation:

  1. From the Filters menu, select your desired filter criteria. For example, select the AWS provider option and filter by Service for only RDS costs.
  2. Click the Add Cost Allocation button on the filter set and enter a value between 1 and 100%. The set percentage will be applied to all the matching costs and represented accordingly in the Cost Report.
Cost allocation of 50% is added to a filter set on a Kubernetes Cost Report

When percent-based cost allocation is set as a filter, forecasts will be produced in aggregate for all set conditions, and the percentage allocation will be applied to that forecast.

Amazon Elastic Container Service (ECS)-Managed Tags​

If you want to view Amazon Elastic Container Service (ECS) cluster tags, you need to enable ECS-Managed Tags. See the AWS documentation for more information.

AWS Organization Tags​

You can filter and group by AWS Organization Tags in Cost Reports. Create a filter for Tag. For the Tag Key, these tags are displayed like aws:organizations:tag.

Network Costs​

For resources that generate network traffic costs (e.g., NAT Gateways), a Network Costs button is displayed in the Cost Report list. See the Network Flow Reports documentation for details on network costs.

In the below example, this Cost Report is grouped by Service and Resource. The Network Costs button is displayed next to NAT Gateway resources.

Network Costs option on a Cost Report

Saved Filters​

You can create and use Saved Filters to apply commonly used filters across multiple reports. Review the Saved Filters documentation for more information.

Adjust Chart Visualization​

You can adjust the chart to be displayed as either a bar chart, line chart, area chart, or pie chart. To toggle these options, click one of the corresponding buttons on the top right of the chart.

tip

For the Cumulative date bin, you can view line charts, pie charts, and area charts. For Daily, Weekly, or Monthly bins, you can view bar charts, line charts, and area charts. Report groupings (see section below) are viewable on all chart types.

A square around the top right of the chart highlights where you can toggle different visualization options, like line charts and area charts

Configure Report Groups​

With the Group By option, you can select one or more dimensions to group by. If you select a grouping option, both the Cost Report table and graph will include costs aggregated by the selected groupings. Once the report is saved, the report’s corresponding Overview widget will be updated as well.

You can group by the following dimensions:

  • Account (e.g., member account on AWS, project on GCP)
  • Billing Account
  • Region
  • Service (e.g., Amazon S3, Azure VMs)
  • Resource
  • Provider (e.g., AWS, GCP, Azure)
  • Category
  • Subcategory
  • Charge Type (see the section below for definitions)
  • Tagged (e.g., see whether resources are or are not tagged)
  • Tag (includes virtual tags)

After a Cost Report has been grouped, each grouping is displayed as a column in the table below the graph. On the graph itself, group labels are displayed with dashes between each grouping, such as production - Acme - nat-123456.

A Cost Report that is enabled with Multi-dimensional Grouping
tip

To sort the table by multiple columns in the table, press Shift + Click on the column headers.

Charge Type Grouping Category​

The Charge Type grouping includes costs separated by items like usage, discounts, EDP discounts, and taxes. Expand the section below to view the associated providers and definitions for each charge type.

Click to view Charge Types
Charge TypeProviderDefinition
adjustmentGCPGCP adjustments due to reasons like goodwill or SLA violations
AllocatedAmortizedDiscountAWSThe fee that is associated with the discount
AllocatedAmortizedFeeAWSSavings Plans and Reserved Instances that have been amortized and allocated to an account with usage
AmortizedFeeAWSAmortized Savings Plan and Reserved Instance purchases
AmortizedTaxAWSTax related to amortized savings plan and reserved instance purchases
AWS MarketplaceAWSAWS Marketplace fees
Bundled DiscountAWSDiscounted usage for one product/service based on the usage of another product/service
CreditAWSAny AWS credits that were applied to your bill
COMMITTED_USAGE_DISCOUNTGCPCompute Engine resource-based committed use discounts
COMMITTED_USAGE_DISCOUNT_DOLLAR_BASEGCPSpend-based committed use discounts
DISCOUNTAny providerDiscounts applied by a provider for your usage
DistributorDiscountAWSDiscounts through the AWS Distribution Resellers Program
Enterprise Discount Program DiscountAWSDiscounts applied through the AWS Enterprise Discount Program (EDP)
FeeAWSUpfront annual fees paid for subscriptions, such as the fee paid for All Upfront subscriptions
FeeTaxAWSTax related to “Fee” type
FREE_TIERGCPCredits applied related to GCP Free Tier usage
Monthly Minimum FeeFastlyMinimum fee for Fastly
Private Rate DiscountAWSAWS discount based on private pricing rates
PROMOTIONGCPGCP promotional credits related to items like marketing promotions
PurchaseAzureRI and Savings Plans purchases in Azure
RefundAWSNegative charges, indicating money refunded by AWS
regularGCPGCP regular charges
RESELLER_MARGINGCPDiscounts for GCP Reseller Program
Reserved Instance Discounted SpendAWSThe rate for instances benefiting from Reserved Instance (RI) benefits.
Reserved Instance FeeAWSMonthly recurring fees for Reserved Instance subscriptions
RiVolumeDiscountAWSVolume discounts for large Reserved Instance purchases
rounding_errorGCPGCP cost type for rounding errors
Savings Plan Covered SpendAWSOn-demand costs covered by your Savings Plan, offsetting corresponding Savings Plan negation items
Savings Plan NegationAWSOffset costs through your Savings Plan benefit associated with covered usage items
Savings Plan Recurring FeeAWSHourly recurring charges associated with a No Upfront or Partial Upfront Savings Plan
Savings Plan Upfront FeeAWSOne-time upfront fee from purchasing All Upfront or Partial Upfront Savings Plans
Solution Provider Program DiscountAWSDiscounts through the AWS Solution Provider Program
SUBSCRIPTION_BENEFITGCPCredits earned after purchase of long-term subscriptions
SUSTAINED_USAGE_DISCOUNTGCPCredit for running certain Compute Engine resources for a large portion of the month
Tax/taxAWS, GCPTaxes applied, such as sales tax
UsageAny provider (for GCP, see "regular")Charges for usage at regular or on-demand rates

Other Grouping Category​

By default, the top five groups of costs by amount are displayed on the graph. In addition, the Other Costs category is displayed as an aggregation of all remaining costs. To add more costs to the graph and table, click the down arrow next to Other Costs. The number of other costs is displayed. Click Show X More Items, to add additional cost groups to the report.

Displaying additional costs using the Other Costs dropdown menu on a Cost Report

Configure Report Settings​

Credits, Discounts, Refunds, and Taxes​

By default, all Cost Reports include discounts and taxes. You can optionally enable credits and discounts, too.

  • Credits: Credits are often promotional codes redeemed for services or trials on your account.
  • Discounts: Discounts can include programs like the AWS Enterprise Discount program. Discounts are often negotiated with the cloud provider and based on usage. You might see discounts reflected as negative values in the Cost Report table. You can follow the below best practices for analyzing Cost Reports with discounts:
    • If you remove the Discount setting, you can view usage and costs before the discount was applied.
    • Group or filter the Cost Report by Charge Type. This grouping displays costs separated by items like usage, discounts, EDP discounts, and taxes.
  • Refunds: Any associated refunds.
  • Taxes: Any associated taxes.

To configure these options:

  1. Above the Cost Report graph, click Settings.
  2. Select an option to toggle on/off any of the included costs (e.g., discounts, etc.).

Amortization​

By default, all Cost Reports show upfront fees, such as fees for Reserved Instances, Savings Plans, Marketplace purchases, and Support, amortized day by day for the period of the fee.

In addition, Vantage uses committed use attribution for linked accounts. By default, you will see fees for Reserved Instances and Savings Plans assigned to the AWS account that benefited from the discount—not the account that purchased the commitment.

For more information about this logic, see the following Vantage blog post.

note

In contrast to AWS Cost Explorer, which displays fees associated with the account responsible for the commitment or purchase, Vantage provides a comprehensive view by showing fees based on the account where the benefits were realized.

Disabling Amortization​

You can toggle a Cost Report to not amortize upfront fees if you want to view the upfront fees on the day they were incurred.

  1. From the top of any Cost Report, click Settings.
  2. Under Amortization, uncheck Enabled.
Enabling and disabling amortization in the console

Vantage vs. Cost Explorer​

If you notice your costs in Vantage differ from what you see in Cost Explorer, this could be for many reasons, including:

  • Amortization logic: As noted above, Vantage uses a different amortization logic from Cost Explorer.
    tip

    If you want to align the view in Vantage to Cost Explorer, disable amortization in Vantage and compare the numbers to unblended costs in Cost Explorer.

  • EC2-Other: In Cost Explorer, this cost category comprises many subcategories (e.g., Data Transfer). In Vantage, EC2-Other is reallocated into direct line items. For example, if you filter for NAT gateway expenditures, the charges initially categorized under transit or egress in EC2-Other are assigned to the individual resource that created the charge.

For more tips on reviewing your cost data against Cost Explorer, see the following blog post.

Usage-Based Reporting​

Usage-Based Reporting provides infrastructure consumption in non-monetary metrics, such as virtual machine running hours, stored gigabytes of data, and read/write units consumed. These reports are available within Cost Reports, where you can toggle between viewing consumption by spend or by usage. See the Usage-Based Reporting documentation for details on how to use and view these reports.

Toggle to show Usage-Based Reporting

Comparative Cost Reporting​

To compare costs day by day, week by week, or month by month on Cost Reports, click the By Date option above the cost table. A view of costs with the same date binning selected for the graph is displayed. To switch back to the previous, current, and percent change view, select Cumulative.

Comparative View

When you view the By Date option, a Total Costs row is displayed at the top of the table.

Export Cost Reports​

You can select from two modes when you export a report: Basic or Advanced.

  • With a Basic export, you can modify only the date range of a report.
  • With an Advanced export, you can arbitrarily select the columns, a date range, and a date bin. The columns can be any combination of groupings from the following list:
    • Provider (e.g., AWS, GCP, New Relic)
    • Service (e.g., EC2, EBS)
    • Region (e.g., us-east-1)
    • Service category (e.g., Storage, Compute)
    • Service subcategory (e.g., m5.large, StandardTier)
    • Charge Type (e.g., Usage)
    • Account (e.g., AWS member account, GCP project)
    • Billing Account (e.g., billing account name)
    • Resource ID (e.g., S3 bucket ARN, MongoDB Atlas cluster name)
    • Usage (toggle to export Usage-Based Reporting data)
  • The Advanced export also has the option to select a specific Tag key. Tag key will be included as an additional column in the export, in the following format: Tag:<TAG KEY> (e.g., Tag:Project).
Cost Report Exports
  1. From the top right of any Cost Report, click the download icon (looks like an arrow with a line below it).
  2. Select the Basic or Advanced download option, and select your desired export criteria.
  3. Select or enter the emails for the users who you want to receive an emailed copy of the report. Note that these recipients must be users in your organization.
  4. Click Export.
note

For the Date Bin export option, when you select Week, the week in the export will begin on Monday, UTC. When you select Month, the month in the export will begin on the first of the month, UTC.

Cost Report Exports

When the export is finished generating, you’ll receive an email with a link to download the exported data, typically within a few minutes. An example export, with groupings of Service Category and Service Subcategory, is shown above. You can also export grouped Cost Reports and the groupings will be respected in the downloaded CSV.

Starred by Me​

If you want to save your favorite Cost Reports or folders to a convenient location, you can star specific resources.

  1. From the All Cost Reports screen, select the checkbox next to one or more Cost Reports.
  2. Above the list, click Star. A star icon will be displayed next to the report.
  3. To access all starred reports, navigate to the Starred By Me screen, also accessible from the left Cost Reporting navigation pane.
- + \ No newline at end of file diff --git a/dashboards/index.html b/dashboards/index.html index 4a590222..af03d8e9 100644 --- a/dashboards/index.html +++ b/dashboards/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Dashboards

Dashboards contain a set of Cost Reports, segment reports, resource reports, or financial commitment reports. You can apply date range and period filters (e.g., display daily costs) to all reports on the dashboard. A consistent date range across all reports on the dashboard can help with cost comparison between different reports. You can assign any number of reports to a dashboard, regardless of which folder the report is in. Once a dashboard is created, you can modify the name and date settings as well as add/remove reports from the dashboard.

Create a Dashboard​

  1. From the top navigation, click Cost Reporting.
  2. On the left menu, select Dashboards. All existing dashboards are displayed within this view.
  3. Click + New.
  4. Enter a Name.
  5. Under Add Reports, select the reports you want displayed on the dashboard.
    note

    At this time, you cannot add widgets from the Overview page, such as Provider Summary.

  6. Click Save. Reports are displayed on the dashboard in alphabetical order, by report name.
A dashboard in the console displayed with four different reports

For each displayed report, click View Report to open that report outside the dashboard.

Save a Dashboard to Favorites​

To save a dashboard to your favorites, navigate to the Dashboards page, then click the star icon to the right of the Created On column. Access your starred dashboard from the Starred By Me screen in the left navigation. Dashboards you create are also displayed on the Created By Me screen.

Delete a Dashboard​

To delete a dashboard, navigate to the Dashboards page, then click the ellipses to the right of the Created On column. Click Delete.

Customize a Dashboard​

On the dashboard, you can apply the following customizations:

  • To change the date range of all displayed Cost Reports, click Customize. Select a date range and click Apply. Click Save to keep these settings. Click Clear Filters to remove filter updates.
  • To change the date grouping, click the Choose Period menu. Select either Cumulative, Monthly, Weekly, or Daily. Click Save to keep these settings. Click Clear Filters to remove filter updates.
  • To create a new dashboard based on an existing dashboard, click the down arrow next to Save. Then, click Save as New. You can then enter a new dashboard name and add additional reports.
  • To reset each Cost Report back to its original settings, click Reset.
  • To add more reports to the dashboard or change the dashboard's name, click Edit.

Add a Saved Filter to a Dashboard​

You can use saved filters to apply consistent filter logic to multiple Cost Reports on a dashboard. If you have a dashboard of high-level Cost Reports (e.g., filtered only to connected providers or services), and you want to further filter a dashboard to a team or specific category, you can use saved filters on dashboards to quickly apply this logic.

  1. From the top right of any dashboard, click the Saved Filters dropdown menu.
  2. Select one or more saved filters. The filter logic is applied across all Cost Reports on the dashboard.
    note

    When you add a saved filter to a dashboard, if a preexisting filter on a Cost Report and the saved filter use the same provider (e.g., both use AWS), "AND" logic is used between each filter set (i.e., show costs where the preexisting filter AND saved filter are true). If the preexisting filter and saved filter use different providers, “OR” logic is used between each filter set.

Set a Default Dashboard​

You can set a default dashboard that's displayed when a user logs in to Vantage and visits console.vantage.sh, instead of the Overview screen. This default dashboard can be set for a team or by an individual user. When the user logs in to Vantage, they will be redirected to that dashboard, and will be in the workspace that is associated with that dashboard.

note
  • If a user is a member of a team with a configured default dashboard and also has a personal dashboard configured, the personal dashboard is displayed.
  • If a user is a member of two different teams with configured default dashboards, the user will see the default dashboard of the first team they were added to.

A user with Owner-level permissions can set a default dashboard for a team.

  1. From the top navigation, click Settings.
  2. From the left navigation, under General Settings, click Teams.
  3. Under Default Dashboard, select the dashboard that should be displayed when a member of the team visits console.vantage.sh. If you want to remove the default dashboard and display the Overview page instead, select None.
  4. Click Save.
tip

A user can also select their personal default dashboard from any existing dashboard. At the top right of the dashboard, click the ellipses. Click Set Default Dashboard and confirm.

Share a Dashboard​

From the top of any dashboard, click Share. A link is added to your clipboard where you can share the dashboard with any Vantage user in your organization who has access to view the dashboard. Each report on the dashboard also has a share option, with a unique link.

Usage-Based Reporting on Dashboards​

You can add a Usage-Based Report to a dashboard. See the Usage-Based Reporting documentation for details.

- + \ No newline at end of file diff --git a/data_dictionary/index.html b/data_dictionary/index.html index bae8ecb9..16e28666 100644 --- a/data_dictionary/index.html +++ b/data_dictionary/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Data Dictionary

Each provider that Vantage integrates with makes different fields available in their billing data. This data is normalized into the fields below. These fields are queryable via the Vantage API and used when constructing VQL statements.

Each provider table contains four columns: Filter, API Field Name, Data Type, and namespace.field.

  • The Filter is the friendly name that is displayed on Cost Report filters within the Vantage console.
  • The API Field Name is the normalized version of the filter name.
  • The Data Type indicates the type of data that is accepted for that field.
  • namespace.field is how that field is referenced in a VQL query (e.g., costs.provider = 'aws', where costs is the namespace and provider is the field).
info

See the list of VQL examples for information on how to use these fields.

Provider Field Values​

Each cost provider also has a normalized name within the API. The provider field is part of the costs namespace.

ProviderAPI Field NameLink to Provider Fields
AWSawsView AWS Fields
AzureazureView Azure Fields
ConfluentconfluentView Confluent Fields
CoralogixcoralogixView Coralogix Fields
Custom ProvidersSee noteView Custom Provider Fields
DatabricksdatabricksView Databricks Fields
DatadogdatadogView Datadog Fields
FastlyfastlyView Fastly Fields
GitHubgithubView GitHub Fields
Google CloudgcpView GCP Fields
KuberneteskubernetesView Kubernetes Fields
MongoDB AtlasmongoView MongoDB Atlas Fields
New RelicnewrelicView New Relic Fields
Oracle CloudoracleView Oracle Cloud Fields
PlanetScaleplanetscaleView PlanetScale Fields
SnowflakesnowflakeView Snowflake Fields
note

To reference a Custom Provider in VQL queries, navigate to the Integrations page. Use the displayed Provider ID (e.g., custom_provider:accss_crdntl_123a45bfdaf38765).

AWS​

FilterAPI Field NameData Typenamespace.field
Accountaccount_idstringcosts.account_id
Billing Accountprovider_account_idstringcosts.provider_account_id
Tagnamestringtags.name
Tag Valuevaluestringtags.value
Serviceservicestringcosts.service
Regionregionstringcosts.region
Providerproviderstringcosts.provider
Categorycategorystringcosts.category
Subcategorysubcategorystringcosts.subcategory
Marketplacemarketplacebooleancosts.marketplace
Resourceresource_idstringcosts.resource_id
Charge Typecharge_typestringcosts.charge_type

Azure​

FilterAPI Field NameData Typenamespace.field
Subscriptionprovider_account_idstringcosts.provider_account_id
Resource Groupaccount_idstringcosts.account_id
Tagnamestringtags.name
Tag Valuevaluestringtags.value
Serviceservicestringcosts.service
Regionregionstringcosts.region
Providerproviderstringcosts.provider
Categorycategorystringcosts.category
Subcategorysubcategorystringcosts.subcategory
Resourceresource_idstringcosts.resource_id
Charge Typecharge_typestringcosts.charge_type

Confluent​

FilterAPI Field NameData Typenamespace.field
Categorycategorystringcosts.category
Organizationaccount_idstringcosts.account_id
Serviceservicestringcosts.service
Resourceresource_idstringcosts.resource_id
Charge Typecharge_typestringcosts.charge_type
Tag*namestringtags.name
Tag Value*valuestringtags.value
Providerproviderstringcosts.provider

* Virtual tags associated with this provider

Coralogix​

FilterAPI Field NameData Typenamespace.field
Categorycategorystringcosts.category
Subcategorysubcategorystringcosts.subcategory
Serviceservicestringcosts.service
Resourceresource_idstringcosts.resource_id
Charge Typecharge_typestringcosts.charge_type
Tag*namestringtags.name
Tag Value*valuestringtags.value
Providerproviderstringcosts.provider

* Virtual tags associated with this provider

Custom Providers​

Available fields are based on what you've uploaded for this Custom Provider. See the Custom Providers documentation for details.

FilterAPI Field NameData Typenamespace.field
Categorycategorystringcosts.category
Subcategorysubcategorystringcosts.subcategory
Regionregionstringcosts.region
Resourceresource_idstringcosts.resource_id
Serviceservicestringcosts.service
Charge Typecharge_typestringcosts.charge_type
Tag*namestringtags.name
Tag Value*valuestringtags.value
Providerproviderstringcosts.provider

* Regular and virtual tags associated with this provider

Databricks​

FilterAPI Field NameData Typenamespace.field
Accountaccount_idstringcosts.account_id
Serviceservicestringcosts.service
Clusterresource_idstringcosts.resource_id
Tagnamestringtags.name
Tag Valuevaluestringtags.value
Categorycategorystringcosts.category
Charge Typecharge_typestringcosts.charge_type
Providerproviderstringcosts.provider

Datadog​

FilterAPI Field NameData Typenamespace.field
Organizationaccount_idstringcosts.account_id
Serviceservicestringcosts.service
Providerproviderstringcosts.provider
Tagnamestringtags.name
Tag Valuevaluestringtags.value
Charge Typecharge_typestringcosts.charge_type

Fastly​

FilterAPI Field NameData Typenamespace.field
Accountaccount_idstringcosts.account_id
Serviceservicestringcosts.service
Providerproviderstringcosts.provider
Regionregionstringcosts.region
Categorycategorystringcosts.category
Subcategorysubcategorystringcosts.subcategory
Resourceresource_idstringcosts.resource_id
Charge Typecharge_typestringcosts.charge_type
Tag*namestringtags.name
Tag Value*valuestringtags.value

* Virtual tags associated with this provider

GitHub​

FilterAPI Field NameData Typenamespace.field
Serviceservicestringcosts.service
Providerproviderstringcosts.provider
Categorycategorystringcosts.category
Subcategorysubcategorystringcosts.subcategory
Resourceresource_idstringcosts.resource_id
Charge Typecharge_typestringcosts.charge_type
Tagnamestringtags.name
Tag Valuevaluestringtags.value

Google Cloud​

FilterAPI Field NameData Typenamespace.field
Projectaccount_idstringcosts.account_id
Billing Accountprovider_account_idstringcosts.provider_account_id
Labelnamestringtags.name
Label Valuevaluestringtags.value
Serviceservicestringcosts.service
Regionregionstringcosts.region
Providerproviderstringcosts.provider
Categorycategorystringcosts.category
Resourceresource_idstringcosts.resource_id
Charge Typecharge_typestringcosts.charge_type

Kubernetes​

FilterAPI Field NameData Typenamespace.field
Accountaccount_idstringcosts.account_id
Groupingnamestringtags.name
Grouping Valuevaluestringtags.value
Clusterservicestringcosts.service
Regionregionstringcosts.region
Providerproviderstringcosts.provider
Charge Typecharge_typestringcosts.charge_type

MongoDB Atlas​

FilterAPI Field NameData Typenamespace.field
Organizationprovider_account_idstringcosts.provider_account_id
Projectaccount_idstringcosts.account_id
Serviceservicestringcosts.service
Categorycategorystringcosts.category
Resourceresource_idstringcosts.resource_id
Charge Typecharge_typestringcosts.charge_type
Tagnamestringtags.name
Tag Valuevaluestringtags.value
Providerproviderstringcosts.provider

New Relic​

FilterAPI Field NameData Typenamespace.field
Accountaccount_idstringcosts.account_id
Serviceservicestringcosts.service
Categorycategorystringcosts.category
Charge Typecharge_typestringcosts.charge_type
Tag*namestringtags.name
Tag Value*valuestringtags.value
Providerproviderstringcosts.provider

* Virtual tags associated with this provider

Oracle Cloud​

FilterAPI Field NameData Typenamespace.field
Tenancyprovider_account_idstringcosts.provider_account_id
Compartmentaccount_idstringcosts.account_id
Tagnamestringtags.name
Tag Valuevaluestringtags.value
Serviceservicestringcosts.service
Regionregionstringcosts.region
Providerproviderstringcosts.provider
Categorycategorystringcosts.category
Resourceresource_idstringcosts.resource_id
Charge Typecharge_typestringcosts.charge_type

PlanetScale​

FilterAPI Field NameData Typenamespace.field
Categorycategorystringcosts.category
Organizationaccount_idstringcosts.account_id
Serviceservicestringcosts.service
Resourceresource_idstringcosts.resource_id
Charge Typecharge_typestringcosts.charge_type
Tag*namestringtags.name
Tag Value*valuestringtags.value
Providerproviderstringcosts.provider

* Virtual tags associated with this provider

Snowflake​

FilterAPI Field NameData Typenamespace.field
Organizationprovider_account_idstringcosts.provider_account_id
Accountaccount_idstringcosts.account_id
Providerproviderstringcosts.provider
Regionregionstringcosts.region
Categorycategorystringcosts.category
Metadatanamestringtags.name
Metadata Valuevaluestringtags.value
Serviceservicestringcosts.service
Charge Typecharge_typestringcosts.charge_type
- + \ No newline at end of file diff --git a/enabling_gcp_billing_export/index.html b/enabling_gcp_billing_export/index.html index 32b7654c..7ea3e46f 100644 --- a/enabling_gcp_billing_export/index.html +++ b/enabling_gcp_billing_export/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Configure GCP Billing Exports

info

This below documentation is a streamlined version of Google Cloud Platform's official documentation.

Prerequisites​

Before you begin, ensure you have the following permissions configured. See the Google Cloud Platform documentation for information on how to configure these permissions.

  • User with permission to create a project
  • User with permission to create a BigQuery dataset
  • User with permission to modify Billing settings

Create a Billing Export​

Step 1: Select or Create a Project​

Before you enable Cloud Billing data exports, you will need to create a project to store the data. If you have multiple Cloud Billing accounts, you will need to enable Cloud Billing exports, individually, on each account.

Recommendation

We recommend you create a dedicated project to store all Cloud Billing data, rather than using an existing project.

The project needs to be linked to the same Cloud Billing account that you plan to enable the Cloud Billing data export on. If you need help assigning a project to a Cloud Billing account, follow the Cloud Billing documentation.

Step 2: Create a BigQuery Dataset​

In the GCP console, navigate to BigQuery, and follow the steps below to create a BigQuery dataset.

  1. From the Project dropdown list at the top of the BigQuery console, select the project you set up for your Cloud Billing data export.

  2. In the Explorer panel, click the three vertical dots (next to your project ID).

  3. Click Create dataset.

    Expand to view example image
    Create BigQuery dataset menu

  4. Configure your dataset:

    • Enter a Dataset ID. We recommend an ID that spans projects, such as all_billing_data, rather than a project-specific ID.

    • For Location type, select either US (multiple regions in United States) or EU (multiple regions in European Union). One of these two options is required to enable detailed usage cost data.

    • Leave the Enable table expiration checkbox unchecked to ensure that data never expires.

    • Click Advanced options. Set Encryption to Google-managed encryption key.

      Expand to view example image
      Create BigQuery dataset
    note

    Customer-managed key encryption is not supported for exporting Cloud Billing data records to BigQuery.

  5. Click the CREATE DATASET. You should see the dataset displayed in the Explorer panel, under your project.

Step 3: Enable Cloud Billing Export to the BigQuery Dataset​

  1. Still in BigQuery, click the hamburger menu (three horizontal lines) at the top left of the console, and select Billing.

  2. In the left Billing navigation menu, select Billing export. (You can also search for and navigate to Billing export from the main search bar at the top of the GCP console.)

  3. Ensure you are on the BIGQUERY EXPORT tab. (This tab should be selected by default). Then, under Detailed usage cost, click EDIT SETTINGS.

    Expand to view example image
    Create GCP Billing Export

  4. Configure the following settings:

    • From the Projects list, select the project you set up to contain your billing data.

    • For Dataset, select the dataset that you set up to contain your exported Cloud Billing data (e.g., all_billing_data).

      Expand to view example image
      GCP detailed usage cost configuration

  5. Click the SAVE.

Next Steps: Complete Your Vantage-GCP Integration​

Your Cloud Billing data will start to be stored in the BigQuery dataset you created. To continue connecting your GCP account to Vantage, complete the Create a GCP Connection instructions.

Important

It typically takes a few hours for data to start appearing. Cloud Billing data is added retroactively for the current and previous month when detailed usage cost data is configured. Full data for the current and previous month can take 24–48 hours to fully propagate.

- + \ No newline at end of file diff --git a/executive_reporting/index.html b/executive_reporting/index.html index 9e91e1de..a10b65e5 100644 --- a/executive_reporting/index.html +++ b/executive_reporting/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Executive Reporting

In many cases, company leadership has requirements to reduce cloud spend or develop strategic initiatives related to cost. Vantage provides a suite of tools, built for enterprises to understand where their cloud spending is going, how it is impacting their business, and how to report it for decision-making purposes.

Review the Overview Page​

Snowflake Cost Reports

The best way to get a quick snapshot of your cloud spend is to use the Overview page. This is the default page that is loaded when you sign in to console.vantage.sh.

The Overview page will show an executive-level summary of the key facets of cloud spend. It lists every connected provider as well as the AWS accounts, GCP projects, Azure subscriptions, and other providers that are incurring charges. Furthermore, it displays information on the amount of committed spend discounts, such as Savings Plans, that are in use and how much coverage Autopilot is providing.

Any of the widgets shown on the Overview page can also be sent in Slack, Teams, or by email. See Create Cost Report Notifications below.

Create Cost Segments​

Segments are the best way to map costs to business units, teams, apps, or services. They allow you to create flexible hierarchies of costs that bubble up from child to parent. This means you could take an organizational hierarchy of Engineering -> Platform -> AWS and assign costs to each of the steps in the hierarchy based on Vantage data. Then, you can share what costs are being incurred by which teams and business units. Navigate to the Segments feature in the Vantage console to get started.

Analyze Per Unit Costs​

Per Unit Costs help you calculate COGS for your organization. Reporting on the unit costs of your business impacts things like margin and decision-making around which customers, services, or endpoints are making positive margin contributions for the company.

Create Cost Report Notifications​

Every Cost Report in Vantage can be automatically sent to Slack, Teams, or by email. A common workflow is to create a monthly Cost Report, group it by Provider or Tag, and send the report to engineering@company.com or a DevOps-related Slack channel every month. For more information on setting up Cost Report Notifications, see the Cost Report Notifications documentation.

Export Cost Reports​

Once you have integrated all your providers into Vantage and created some reports, you may need to export data from Vantage into another system or a spreadsheet for further reporting.

For this scenario, Vantage has Cost Report Exports. With customizable controls for exporting data from Cost Reports, you can select which columns, date ranges, and date resolutions (weekly, monthly) to export to a CSV. For more details on the controls and formats, see the Cost Report Exports documentation.

Additional User Workflows​

- + \ No newline at end of file diff --git a/financial_commitment_reports/index.html b/financial_commitment_reports/index.html index 849e45fc..f91288b6 100644 --- a/financial_commitment_reports/index.html +++ b/financial_commitment_reports/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Financial Commitment Reports

A financial commitment is an agreement made with a cloud provider to spend a certain amount of money over a designated timeframe (e.g., one or three years) in return for a discounted rate on services. Examples of financial commitments include AWS Reserved Instances and Savings Plans. Other discounts include the AWS Enterprise Discount Program (EDP) and Spot Instances.

Vantage financial commitment reports provide a unified view of all your AWS financial commitments, with the ability to filter or create custom aggregations and groupings. Financial commitment reports track Savings Plans, Reserved Instances, Spot Instance usage, and EDP discounts for AWS costs.

note

This feature is currently available only for AWS, with plans to expand to Azure and GCP in the future.

Understand Discounted Coverage and Effective Savings Rate​

Financial commitment reports in Vantage help you understand your overall discounted coverage and effective savings rate. These metrics are described in detail below.

Coverage​

Coverage is the percentage of cloud spend covered by financial commitments, like Reserved Instances and Savings Plans. Coverage can be calculated as follows.

Covered UseCovered Use+On–Demand Use\frac{Covered\ Use}{Covered\ Use+On–Demand\ Use}

As a basic example, an app uses two Reserved Instances. The app also uses three On-Demand instances of the same size.

  • The two Reserved Instances cost a total of $120 per month.
  • The three On-Demand instances cost a total of $180 per month.
$120$120+$180=40% coverage\frac{\$120}{\$120+\$180} = 40\%\ coverage

With this lower coverage percentage, the app’s developers could consider purchasing more Reserved Instances, instead of On-Demand instances, and realize greater savings.

Effective Savings Rate​

Effective savings rate measures the impact of purchased financial commitments as well as discounts, refunds, and credits. If you use financial commitments with higher discounts, you’ll improve your effective savings rate. The effective savings rate can be calculated as follows.

1−Discounted SpendOn–Demand Equivalent Spend1 - \frac{Discounted\ Spend}{On–Demand\ Equivalent\ Spend}

As an example, an app uses a large-sized Reserved Instance, with a one-year no upfront commitment. It costs $0.20 per hour. The app used the Reserved Instance for 90% of the month (i.e., 657 hours, when using a value of 730 hours for the month).

  • The Reserved Instance costs a total of $146 for this month ($0.20 x 730 hours).
  • The On-Demand equivalent of this instance costs a total of $164.25 for the month ($0.25 per hour x 657 hours).
1−$146$164.25=11.11% effective savings1- \frac{\$146}{\$164.25} = 11.11\%\ effective\ savings

Create a Financial Commitment Report​

tip

Before you create a report, you can view a list of all your active (and expired) Savings Plans and Reserved Instances on the Commitments screen.

  1. Navigate to the Financial Commitment Reports screen. All existing reports are displayed. From this screen, you can edit and delete existing reports.
  2. To create a new report, click New Report.
  3. To filter costs, click the Filters button on the top left of the graph.
    • The AWS costs where... tile is displayed. Click + New Rule.
    • For Category, select an available filter category.
      note

      You can filter by service (e.g., Amazon EC2), account, billing account, commitment type (e.g., On-Demand), charge type (e.g., Spot Usage), category (e.g., Compute Instance), subcategory (e.g., AP-Requests-Tier1), instance type (e.g., m5.large), region, and tag.

    • Two additional dropdown menus are displayed. Select is, is not, contains, or does not contain based on your desired filter criteria, then select one or more corresponding values from the second dropdown menu. For Tag, the Tag Key dropdown is displayed before the operator dropdown.
    • Click Save.
      Click to view a visual example
      GIF of filtering a commitment report for AWS category costs that are not usage
  4. You can optionally edit your existing rules or add additional filter criteria.
    • To edit the rule you just created, select the rule, make your changes, and then click Save.
    • If you want to add a rule to filter multiple criteria, such as filter by certain services and another rule to filter by certain regions, click + New Rule. Add the additional criteria and save.
    • To add a separate rule set, click + New Filter. This rule set will be displayed as Or AWS costs where... in a new rule section.
    • To delete a rule set, click the trashcan icon on the top right of the rule set.
  5. Above the rule set(s), click Apply. The graph will update with your existing filter criteria.
  6. To save the report, click Save as New. Enter a report name, and click Save. (To edit this name, click the pencil icon in the breadcrumbs above the chart, next to the report's name.)

You can edit the filter criteria on a report at any time. Remember to click Save once you are done making changes.

Apply Aggregations to Reports​

You have the option to further drill down into your costs:

  • Above the graph, click the Group By dropdown menu. Select one or more grouping options. You can group by charge type, commitment type, service, account, billing account, region, category, subcategory, instance type, and tag.

    Click to view a visual example
    Filtering a commitment report for AWS category costs that are not usage
    tip

    For a detailed breakdown of the Charge Type grouping, see the Cost Reports documentation.

  • To adjust the date binning, click the data bin menu on the top right of the graph. Select either Daily, Weekly, or Monthly.

  • To change the date range, click the date menu on the top right of the graph and adjust the date range.

    note

    You can historically view back as far as your account’s retention period. By default, this period is six months.

Commitment Eligibility Filter​

You can also adjust the report to include only costs that are eligible for Reserved Instances and Savings Plan commitments. Click On-Demand Costs: and select one of the following options:

  • All Costs: Display all costs regardless of commitment eligibility. All services are included in this view.
  • Commitment-Eligible Costs: This option is the default option. Only costs that are eligible for Reserved Instances and Savings Plans are displayed. With this option, you can choose whether to include all your On-Demand AWS costs in the effective savings rate calculation or only those costs eligible for potential coverage by Savings Plans and Reserved Instances. This option includes the following services:
    • Amazon EC2
    • AWS Lambda
    • Amazon SageMaker
    • Amazon RDS
    • Amazon ElastiCache
    • Amazon OpenSearch
    • Amazon EKS
    • Amazon ECS

Review the Report​

By default, financial commitment reports are grouped by Charge Type (e.g., Savings Plan Covered Spend, Spot Usage). Groupings are represented by each colored section of the bar chart. Hover over any bar to get a breakdown of costs. The breakdown is also provided in the table below the chart.

note

Costs in the graph are unblended.

You can sort the table by any of the date or grouping columns.

The chart contains two axes: the left axis measures costs, and the right axis measures the coverage and effective savings rate. The cost axis shows positive and negative values (i.e., discounts are represented as negative dollar values).

A view of a full financial commitment report

Trend lines are displayed to illustrate the change in coverage and effective savings rate over time. Hover over any line to get a point-in-time view of each metric and associated costs.

Above the chart, the following values are displayed for the report’s lookback period:

  • Total Savings: The total amount saved by using your financial commitments and other discounts.
  • Effective Savings Rate: The percentage discount across all usage. (See the section above for a more in-depth explanation of this metric.)
  • Coverage: The percentage of total spending that is covered by financial commitments. (See the section above for a more in-depth explanation of this metric.)

Add a Financial Commitment Report to a Dashboard​

You can add financial commitment reports to a dashboard so that teams can see the coverage related to their resources. See the Dashboards documentation for more information on how to create and add reports to dashboards.

- + \ No newline at end of file diff --git a/folders/index.html b/folders/index.html index 5246c13a..35fe0a1a 100644 --- a/folders/index.html +++ b/folders/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Folders

If your organization has many Cost Reports, you can create folders to separate Cost Reports for different groups, like business units or cost centers. You can also move Cost Reports between folders and nest folders within each other to create complex organizational structures.

Create a Folder​

  1. From the top navigation, click Cost Reporting.
  2. On the left menu, select Cost Reports.
  3. On the top right, click the down arrow next to + New.
  4. Select New Folder.
  5. Enter a name for the folder, then click Create.
  6. The new folder is displayed in the Cost Report list. Select the folder to open it.
  7. At the top of the folder, click the down arrow next to + New. You can create a new Cost Report inside the folder or a sub-folder within that folder.

Move Cost Reports and Folders​

To move one or more folders or Cost Reports from the All Cost Reports screen:

  1. From the All Cost Reports screen, select the checkbox next to one or more Cost Reports or folders.
  2. At the top of the report list, click Move.
  3. Select any listed folder, then click Move Here.
GIF of moving a Cost Report from the main reports screen to a specific folder

note

When you move a folder into another folder, it becomes a subfolder. Consequently, any reports or folders contained within the moved folder will move along with it.

To move one or more Cost Reports or subfolders out of a folder and back to the main All Cost Reports screen:

  1. From the current folder, select the checkbox next to one or more Cost Reports or folders.
  2. At the top of the report list, click Move.
  3. The Moving... modal is displayed. Click < Back until All Reports (currently selected) is displayed at the top.
  4. Click Move Here.

Create a Dashboard from a Folder​

You can create a dashboard made up of all the reports within a folder.

  1. Navigate to any folder.
  2. At the top, click Dashboard. A dashboard containing all included reports is displayed.
  3. If you want to save the dashboard, click Save As New. This saved dashboard will be shareable and available within the main Dashboards screen.

Starred By Me​

If you want to save your favorite Cost Reports to a convenient location, you can star specific reports. See the Starred By Me documentation for details.

- + \ No newline at end of file diff --git a/forecasting/index.html b/forecasting/index.html index 0955be40..7ee02975 100644 --- a/forecasting/index.html +++ b/forecasting/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Forecasting

For every Cost Report, Vantage generates a forecast that projects where your costs are expected to be by the end of the current month. You can also view projected costs, several months ahead. Vantage uses a time-series model to generate these forecasts and will run through all available data ingested into the platform on a per-service basis (e.g., EC2, RDS). These costs are forecasted into the future, taking into account seasonality or one-off spikes.

View a Forecast on a Cost Report​

To view a forecast on a Cost Report, create a new Cost Report and save it. After you create a new Cost Report, a message is displayed that indicates the forecast is generating. The processing time depends on the amount of data contained in the filtered report, but it usually takes less than 10 minutes.

The forecast for the rest of the current month is displayed, by default, on the chart. Forecasts are available on line charts and bar charts. On line charts, forecasts are available for all date binning options. For bar charts, you can view forecasts for day, week, and month date binnings.

The forecast includes an upper-expected band and a lower-expected band, with a median forecast that is in the middle of these two ranges. This forecast is updated daily as new cost data arrives.

To view a future forecast, open the date picker to the top right of the chart.

  1. On the left, under Forecast Periods, select either Next Month, Next 3 Months, or Next 6 Months.
  2. Click Apply. Change to either the bar or line chart view to see a forecast.

Bar Chart View​

In the below example image, bars for future months are visible. Error bars are present for future months to represent the upper and lower bounds of the forecast. Hover over any future date to see the forecasted min, max, and median. Total forecasted costs are displayed above the chart, next to currently accrued costs. Forecasts are also present in grouped bar charts.

A Cost Report with a forecast for the next 6 months and the mouse hovering over a future date point

Line Chart View​

In the below example image, the light-purple area is the forecast range, with upper and lower bounds. The dark-purple dotted line represents the median forecast for that month. Hover over any future date to see the forecast median and the previous period's costs. Total forecasted costs are displayed above the chart, next to currently accrued costs.

A Cost Report with a forecast for the month and the mouse hovering over a future date point

View Service Forecasts​

In addition to aggregate forecasts on Cost Reports, you can also view a per-service cost forecast. On any Cost Report, select a row from the table. An individual forecast is displayed for the selected service.

- + \ No newline at end of file diff --git a/gcp_supported_services/index.html b/gcp_supported_services/index.html index e3ef81e8..3fc3ead6 100644 --- a/gcp_supported_services/index.html +++ b/gcp_supported_services/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

GCP Services & Regions

Supported Services​

Vantage will show 100% of your organization's accrued costs across all services. Vantage also offers per-resource pricing for the following services using custom logic to query APIs for each GCP service. While Vantage supports per-resource pricing for many popular services, some services are not currently supported.

info

To request new service support on Vantage, email support@vantage.sh with the subject line of New GCP Service Support. Include as much information as you can about the data you want to see.

Below is a list of currently supported GCP services for active resources. Vantage maintains read-only access to the GCP APIs for these resources.

ServiceDescription/Supported Resources
Cloud AlloyDBVantage supports showing costs for Cloud AlloyDB clusters, instances, and backups.
Cloud App EngineVantage supports showing costs for Cloud App Engine services.
Cloud BigQueryVantage supports showing costs for Cloud BigQuery instances.
Cloud BigtableVantage supports showing costs for Cloud Bigtable instances.
Cloud ComputeVantage supports showing costs for Cloud Compute engines and disks.
Cloud ContainersVantage supports showing costs for Cloud Containers clusters.
Cloud DataflowVantage supports showing costs for Cloud Dataflow jobs.
Cloud FirestoreVantage supports showing costs for Cloud Firestore databases.
Cloud FunctionsVantage supports showing costs for Cloud Functions functions.
Cloud LoggingVantage supports showing costs for Cloud Logging buckets.
Cloud RunVantage supports showing costs for Cloud Run services.
Cloud SpannerVantage supports showing costs for Cloud Spanner instances.
Cloud SQLVantage supports showing costs for Cloud SQL instances.
Cloud StorageVantage supports showing costs for Cloud Storage buckets.
Memorystore for RedisVantage supports showing costs for Memorystore for Redis instances.
Secrets ManagerVantage supports showing costs for Secrets Manager secrets.

Supported Regions​

Vantage can sync resources from all GCP regions with external connectivity.

- + \ No newline at end of file diff --git a/getting_started/index.html b/getting_started/index.html index 88dba479..d333ffe1 100644 --- a/getting_started/index.html +++ b/getting_started/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Quickstart

Get Started

This quickstart guide will help you to set up your Vantage account, connect one or multiple providers, and start using Cost Reporting and Financial Planning features.

For video tutorials, check out Vantage University 🎓.

Step 1: Create an Account​

  • To get started, create a Vantage account.
  • Optionally, you can upgrade to a paid plan to unlock additional features and track higher amounts of cloud infrastructure costs. View the Vantage Pricing page for all pricing and plan details. All paid plans have an option to trial the service before committing to a subscription.

Step 2: Connect Providers​

Next, create a data integration between at least one of your providers and Vantage. Detailed integration documentation is linked for each of the providers below.

AWS logo

Amazon Web Services (AWS)

Vantage integrates with your AWS account through a Cross-Account IAM role, giving Vantage read-only access to an organization's cost data. After the initial sync, you will be able to take advantage of features in Vantage to manage, inspect, and model your AWS spend.

View Documentation
Azure logo

Azure

Vantage integrates with your Azure account by using an Active Directory Service Principal, which can be assigned access to both management groups or individual subscriptions. Any subscriptions that are part of a resource group will be automatically imported.

View Documentation
GCP logo

Google Cloud Platform (GCP)

Vantage integrates with your GCP account through a service account, providing Vantage with read-only access to an organization's cost data. Following the creation of the role with the appropriate permissions, Vantage will initiate the synchronization of cost data and resource metadata.

View Documentation
Kubernetes logo

Kubernetes

Vantage allows you to see in-cluster costs for Kubernetes clusters, including seeing costs by container, service, namespace and label. The Vantage Kubernetes agent is the recommended integration point for ingesting Kubernetes costs into Vantage.

View Documentation
Datadog logo

Datadog

Vantage integrates with your Datadog account through a read-only Datadog OAuth token. After connecting, Vantage automatically receives read-only access to appropriate cost and usage APIs to begin ingesting Datadog cost data

View Documentation
New Relic logo

New Relic

Vantage integrates with your New Relic account through the use of New Relic Usage Data via the New Relic GraphQL API.

View Documentation
MongoDB Atlas logo

MongoDB Atlas

Vantage integrates with MongoDB Atlas account through read-only use of the Invoices API. To see Active Resources for your MongoDB Atlas account, Vantage uses the Clusters API and the Projects API.

View Documentation
Snowflake logo

Snowflake

Vantage integrates with your Snowflake account through a secure, read-only user who has access to Snowflake usage tables. Optionally, Vantage can pull from a dedicated schema that you create.

View Documentation
Databricks logo

Databricks

Vantage integrates with your Databricks account through the use of Billable Usage Logs. Vantage provides an S3 bucket for Databricks to deliver usage logs to on a periodic basis.

View Documentation
Fastly logo

Fastly

Vantage integrates with your Fastly account through a read-only API token. Fastly API tokens are free for you to create—and adding them to the Vantage console only takes a few minutes.

View Documentation
Oracle Cloud logo

Oracle Cloud

Vantage connects to Oracle Cloud using a read-only IAM user and API key to read from a Cost and Usage Reports object storage bucket.

View Documentation
Confluent logo

Confluent

Vantage integrates with your Confluent account through a revocable read/write API key and secret. Confluent API keys are free for you to create—and adding to the Vantage console only takes a few minutes.

View Documentation
PlanetScale logo

PlanetScale

Vantage integrates with your PlanetScale account via the PlanetScale Invoices API using an OAuth workflow.

View Documentation
Coralogix logo

Coralogix

Vantage integrates with your Coralogix account through a revocable read-only API key and your Coralogix domain.

View Documentation
GitHub logo

GitHub

Vantage integrates with GitHub via a Vantage-owned billing manager account that users add to their GitHub Organization or Enterprise.

View Documentation
Custom Providers logo

Custom Providers

Vantage integrates any of your Custom Providers through a schema based on the FinOps FOCUS specification.

View Documentation

Other Providers

Vantage will be launching support for additional cloud infrastructure providers in the future. If you have a particular provider that you would like supported, please reach out to support@vantage.sh.

Step 3: View Ingested Costs and Create Cost Reporting Resources​

Once you create some provider integrations, Vantage will automatically begin ingesting billing information for your account. The default landing page in the Vantage console is the Overview page. This page serves as an executive-level summary, providing a comprehensive snapshot of the cost metrics that matter most to you.

As you continue to set up your cost reporting infrastructure, you can use the below guides for some best practices in Vantage.

  • Team Accountability: To ensure team accountability in cloud cost management, follow this guide. Create Cost Report Folders for specific teams, generate Cost Reports for various dimensions, implement Cost Report notifications, set team budgets, and continually monitor and optimize to minimize unnecessary expenses, thus guaranteeing efficient cloud spending.
  • Executive Reporting: If you want to set up executive-level reporting, follow this guide. Use tools in Vantage to effortlessly gather and present comprehensive insights into your organization's cloud spending, enabling you to deliver actionable reports that facilitate informed decision-making at the executive level.
  • Find Hidden Costs: If you want to uncover hidden costs and optimize spending, follow this guide. Vantage provides tools like Active Resources for listing cost-driving resources and Cost Anomaly Alerts to automatically detect and alert on unexpected expenses.
- + \ No newline at end of file diff --git a/hidden_costs/index.html b/hidden_costs/index.html index ea5c6d92..ea536d5a 100644 --- a/hidden_costs/index.html +++ b/hidden_costs/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Find Hidden Costs

With team accountability and executive reporting in place, there are usually opportunities to turn off or optimize resources that are unexpectedly driving costs. Vantage has numerous "cost debugging" features to help you drill down into cost trends.

Review Active Resources​

Snowflake Cost Reports

The Active Resources feature provides a list of all resources currently driving costs in your account. Active resources currently support AWS, Azure, Snowflake, and MongoDB Atlas. Select each resource to see full details about where it is incurring costs.

Analyze Subcategory Costs​

Snowflake Cost Reports

To drill down into specific resources, like EC2 instances, Azure VMs, or Google Cloud VMs, you can use Cost Reports. Click through Service -> Resource -> Category -> Subcategory to reach the most granular object that the provider has billing data for.

View Cost Anomaly Alerts​

Cost Anomaly Alerts automatically detect anomalies, but these alerts must be configured.

Once you have created Cost Reports, navigate to the Anomalies tab on each report to view costs that the Vantage algorithm has detected as being outside the expected range. You can drill into these costs by clicking through the categories displayed on the report and also configure alerts to be sent to Slack, Teams, or email for future anomalies.

Additional User Workflows​

- + \ No newline at end of file diff --git a/index.html b/index.html index bb1840de..1742cf47 100644 --- a/index.html +++ b/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Vantage Documentation

Vantage is a cloud observability and optimization platform that aggregates cloud infrastructure costs across providers to deliver a centralized view into total cloud spend. Vantage has multiple tools for optimizing cloud spend and provides organizations with advanced FinOps workflows and cost governance.

Diagram of cloud providers integrating with Vantage

Quickstart

Get started creating an integration with a number of cloud and cloud service providers.

Cost Reports in the Vantage console

Cost Reports

Create your first Cost Report in the Vantage console. Create budgets, forecasts, and annotations all within your Cost Report.

Terraform icon

Terraform Provider

Use the Vantage Terraform provider and modules to automate your cloud cost monitoring infrastructure.

Additional and Community Resources​

Vantage maintains a variety of resources to help make the lives of cloud practitioners easier. All resources below are free to use and open source, when possible.

API icon

API Documentation

The Vantage API makes it easy for you to programmatically access and read your cloud pricing data. Automate the management and creation of cost reporting resources, as well as programmatically create reports and filters. View the API docs to get started.

Menu icon

EC2Instances.info

Simplifies the complex task of pricing EC2 instances on AWS. With over a million pricing permutations due to instance types, regions, and availability zones, the site streamlines the process, enabling users to quickly find and compare the best resources for their needs.

Scoreboard icon

AWS Cost Leaderboard

A ranked list of AWS services that customers spend the most on. Vantage provides this anonymized and aggregated data to the community to shed light on cloud infrastructure costs.

Handbook icon

Cloud Cost Handbook

An open-source set of guides meant to help explain the complex pricing of public cloud infrastructure and service providers in easy-to-understand terms. This guide is hosted on GitHub and is open to anyone to contribute their knowledge to the community.

Slack icon

Slack Community

While the documentation here is meant to help answer any questions, you're also welcome to join our Slack community to add to the discussion and ask questions.

Report icon

Cloud Cost Reports

Vantage uses anonymized data from thousands of connected accounts to snapshot industry spending patterns. View our quarterly Cloud Cost Reports to analyze trends over time.

Vantage Support

If you need help with anything, please feel free to reach out to support@vantage.sh.

- + \ No newline at end of file diff --git a/issues/index.html b/issues/index.html index 7b2e19cb..b2a5fb62 100644 --- a/issues/index.html +++ b/issues/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Issues

Teams can use issues to coordinate and collaborate in Vantage. Consider the below use case.

An organization notices a sudden spike or increase in costs related to a certain service. This service has an attached tag related to a particular team. The manager creates an issue on Vantage for the team to investigate the cost anomaly. The manager can quickly see comments and progress from their team and monitor associated costs on the attached Cost Report.

You can create issues, assign them to members in a workspace, and associate issues with a Cost Report. Team members can comment on issues, adjust an issue's category and status, and estimate the potential cost-savings impact associated with the issue.

Create an Issue​

  1. From the top navigation, select Financial Planning. Then, on the left navigation, select Issues.
  2. All existing issues are displayed. The Issues page has two tabs: Open and Closed.
  3. From the top right of the Issues screen, click New Issue.
  4. Add the following items:
    • Enter an issue Title (required).
    • Add an issue description (optional) in the comment box. You can use Markdown or the format bar options to format your text. Click Preview above the comment box to see the text rendered with associated formats.
    • On the right panel, click the gear icon in the Assignee (optional) box to add one or more Vantage users.
    • For Categories (optional), select an option from the list. To add a new category, click Manage Categories. The Manage Categories screen is displayed in a new tab. You can add and delete categories from this screen.
    • For Linked Cost Reports (optional), select an associated Cost Report or Segment Report where the issue was identified.
    • For Estimated Savings Value (optional), enter a monthly or annual estimated savings based on what you identified as the issue.
  5. Click Create issue. The Status will now be Open. Users can comment on issues as well as close completed issues.

Close and Reopen Issues​

  1. From the Issues list, select any issue.
  2. At the bottom of the issue, click Mark as Resolved. The issue's Status is displayed as Closed.

Receive Issue Notifications​

You will receive email notifications in the following situations:

  • When an issue is created and you're assigned.
  • When another user comments on an issue you've created, been assigned to, or also commented on.
  • When an issue you are assigned to or subscribed to is closed by another user.
  • When an issue you are assigned to or subscribed to is reopened by another user.

To manually subscribe to an issue and receive notifications, open an existing issue. In the Notifications box, click Subscribe.

Create Issues via Annotations​

Issues are automatically created when an annotation is added to a Cost or Segment Report. See the Annotations documentation for more information.

- + \ No newline at end of file diff --git a/kubernetes/index.html b/kubernetes/index.html index cf12cbbb..472a8d31 100644 --- a/kubernetes/index.html +++ b/kubernetes/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Kubernetes Costs and Efficiency Metrics

Vantage has two sets of tools for viewing and optimizing Kubernetes costs: viewing Kubernetes costs in Cost Reports and viewing Kubernetes efficiency metrics in the devoted Kubernetes page in the console.

  • Kubernetes Cost Reports. Use Cost Reports to drill into costs by Cluster, Namespace, Service, and Label, as well as combine Kubernetes costs with other providers, such as a database or cache layer.
  • Kubernetes Efficiency Metrics and Reports. Display the cost efficiency down to the pod level of a cluster. These metrics are useful for rightsizing and cost optimization. You can also create efficiency reports based on these metrics.

Kubernetes Cost Reports​

Kubernetes Cost Reports provide cost visibility by Cluster, Label, Namespace, and Service. They include Kubernetes-specific filters and filter logic. You can combine specific Kubernetes costs with other services. In the below example, the filter includes the costs of a specific service with corresponding RDS database costs.

Kubernetes and AWS Cost Report filters

Cost Reports also provide forecasts. These forecasts are updated daily and provide confidence intervals for what your costs are likely to be for the month.

Cost Data Source​

The costs displayed on these reports come from your integration with the Vantage Kubernetes agent. The agent calculates the cost of a running pod by analyzing the CPU, RAM, GPU, as well as storage usage and calculates the cost of each input based on the cost of the underlying infrastructure.

Vantage uses a formula to divide the cost of a compute instance into CPU, RAM, and GPU and then computes the cost for each type of resource. The cost calculation reflects the exact runtime of each pod, down to the minute. This means if a pod runs for only 5 minutes within an hour, Vantage recognizes only 5 minutes of spend, rather than the full hour. All the cost allocation calculations are done locally in your cluster and make this data available for querying.

note

Kubernetes costs are not included in monthly tracked infrastructure costs as they’re already captured from underlying EKS, GKE, or AKS costs.

Kubernetes Efficiency Metrics and Reports​

Discounts on Efficiency Reports

CPU/memory rates are based on the underlying instances the pod is scheduled on. In Kubernetes Efficiency Reports, this is the undiscounted rate of the instance. Discounts are not reflected on these reports. You can view discounts on Kubernetes Cost Reports.

View Kubernetes Efficiency Metrics​

  1. Navigate to the Kubernetes page in the Vantage console.
  2. On the left navigation menu, select an option to view connected Clusters, Namespaces, or Labels. Each view contains a graph as well as a table with the following headings:
    • Name: The name of the Cluster, Namespace, or Label you’re viewing.
    • Idle Costs: A dollar value representation of the number of resources requested that are idle.
    • Total Costs: A dollar value representation of the total cost of the resources.
    • Cost Efficiency: The ratio of idle costs and total costs.
  3. Filter a cluster's efficiency metrics by date or resource:
    • From the top right of the graph, change the date range to see how costs have changed over time.
    • From the resource list below each chart, click the icons next to each resource to view different aggregations. Click the View on chart button to isolate that specific resource on the chart.

Create Efficiency Reports​

With Kubernetes efficiency reports, you can filter your Kubernetes cost data and create reports based on these filters. You have the option to filter for costs by Cluster, Namespace, or Label.

note

Labels will include namespace labels and annotations if enabled in your Vantage Kubernetes agent integration.

  1. Navigate to the Kubernetes page in the Vantage console.
  2. On the left navigation menu, select Efficiency Reports. All existing Kubernetes efficiency reports will be listed, along with who created the report as well as the date when the report was created.
  3. From the top right of the screen, click New Report. Like the efficiency metrics view, a chart/graph with idle costs is displayed. Below the chart, a table is displayed with the following columns: the resource's name, Idle Costs, Total Costs, and Cost Efficiency.
  4. To filter costs, click the Filters button on the top left of the chart.
    • The Kubernetes costs where... tile is displayed. Click + New Rule.
    • From the filter dropdown menu, select either Cluster, Namespace, Category (cpu, ram, or gpu) or Label.
      note

      See the section below for information on how to enable GPU metrics.

    • Two additional dropdown menus are displayed. Select is or is not based on your desired filter criteria, then select one or more Clusters, Namespaces, or Labels from the second dropdown menu.
    • Click Save.
      Click to view visual example
      Create Kubernetes Efficiency filters
  5. You can optionally edit your existing rule or add additional filter criteria.
    • To edit the rule you just created, select the rule, make your changes, and click Save.
    • If you want to add a rule to filter multiple criteria, such as filter by certain Clusters and another rule to filter by certain Namespaces, click + New Rule. Add the additional criteria and save.
    • To add a separate rule set, click + New Filter. This rule set will be displayed as Or Kubernetes costs where... on the new tile.
    • To delete a rule set, click the trashcan icon on the top right of the rule set.
      Click to view visual example
      Add OR clause to Kubernetes Efficiency Report
  6. Above the rule set(s), click Apply. The graph will update with your existing filter criteria.
  7. You have the option to further drill down into your costs.
    • Above the graph, click the Aggregate By dropdown menu. Select either Idle Costs or Total Costs.
      tip

      Selecting one of these options will also make those costs the default sort for the table.

    • To adjust aggregation dimensions, above the graph, click the Group By dropdown menu. Select one or more of the following options: Cluster, Namespace, and specific Label Key/Label Value.
    • To adjust the date binning, select the menu on the top right of the graph. Select either Daily, Weekly, or Monthly.
    • To change the date range, click the date picker menu on the top right of the graph and adjust the date range.
      Click to view visual example
      Add additional filters to Kubernetes efficiency report
  8. To save the report, click Save as New and enter a report name. Then, click Save. (To edit this name, click the pencil icon in the breadcrumbs above the chart, next to the report's name.)

You can edit the filter criteria on a report at any time. Remember to click Save once you are done making changes.

Add an Efficiency Report to a Dashboard​

You can add your efficiency reports to dashboards. These reports will be displayed on the dashboard, along with other cost and segment reports.

  1. From the top navigation, click Cost Reporting.
  2. From the side navigation, click Dashboards.
  3. Select an existing dashboard, or click + New to create a new dashboard.
    • If you are creating a new dashboard:
      • Enter a Name.
      • Under Add Reports, find and select your Kubernetes efficiency report.
      • Click Save.
    • If you want to add the report to an existing dashboard:
      • From the top right of the existing dashboard, click Edit.
      • Under Add Reports, find your efficiency report.
      • Click Save.

Efficiency Calculations​

Pod resource efficiency is defined as the resource utilization versus the resource request over a given time window. These resource utilization metrics include CPU and RAM. When viewing efficiency, it will be shown as a percentage. 100% means the resource allocation is fully efficient.

Idle costs are defined as the difference between the cost of requested resources (CPU and Memory) and the associated usage of those costs:

idle_cost = (cpu_request_cost - cpu_usage_cost) +
            (memory_request_cost - memory_usage_cost)

Kubernetes GPU Idle Costs​

For each Kubernetes pod, you can view the idle and total costs for NVIDIA GPU usage within a Kubernetes cluster. GPU memory usage is available on Kubernetes efficiency reports as an option for the Category filter and is included in the cost efficiency score per pod.

How GPU Idle Costs Are Calculated​

When an instance includes GPUs, 95% of the cost of the node will be allocated to the memory of the GPU. The number of GPUs requested by the pod will dictate how much of the total memory is allocated to the pod. Idle costs for allocated GPUs are determined by calculating the difference between the total allocated and the total used memory for the pod, down to the container level:

idle_memory = total_allocated_memory - used_memory
note

GPU utilization is not factored into the efficiency calculation; only GPU memory is tracked. If you have a workload that requires tracking GPU utilization, contact support@vantage.sh.

Configure GPU Metrics​

The Vantage Kubernetes agent automatically collects GPU usage information via the NVIDIA DCGM Exporter. The exporter is included as part of the NVIDIA GPU Operator, but it can also be installed independently. The agent scrapes the exporter directly and exposes the configuration for the namespace, service name, port name, and path. The default values are configured for the GPU operator default case. NVIDIA GPU idle costs are available for the agent-supported infrastructure providers—AWS, Azure, and GCP.

Vantage Kubernetes Agent Configuration​

Install or upgrade to Vantage Kubernetes agent version 1.0.26 or later, available as part of Helm Chart version 1.0.34. To collect GPU metrics, set the following parameter to true in the agent's values.yaml: -set agent.gpu.usageMetrics=true.

The agent also provides some additional GPU configuration options. The defaults match the operator's defaults. Refer to the agent’s values.yaml for option configuration details.

Configure the Operator​

For net-new installations:

  1. To configure the dcgm-exporter to collect custom metrics, retrieve the metrics file and save it as dcgm-metrics.csv:
    curl <https://raw.githubusercontent.com/NVIDIA/dcgm-exporter/main/etc/dcp-metrics-included.csv> > dcgm-metrics.csv
  2. Add the DCGM_FI_DEV_FB_TOTAL memory metric to the metrics file:
    ....
    # Memory usage
    DCGM_FI_DEV_FB_FREE, gauge, Framebuffer memory free (in MiB).
    DCGM_FI_DEV_FB_TOTAL, gauge, Framebuffer memory total (in MiB).
    DCGM_FI_DEV_FB_USED, gauge, Framebuffer memory used (in MiB).
    ...
  3. Create a gpu-operator namespace:
    kubectl create namespace gpu-operator
  4. Create a ConfigMap from the metrics file: 
    kubectl create configmap metrics-config -n gpu-operator --from-file=dcgm-metrics.csv
  5. Follow the steps provided in the NVIDIA GPU Operator installation guide to install the operator. Set the following options on the operator:
    • --set dcgmExporter.config.name=metrics-config
    • --set dcgmExporter.env[0].name=DCGM_EXPORTER_COLLECTORS --set dcgmExporter.env[0].value=/etc/dcgm-exporter/dcgm-metrics.csv.

Once the operator is installed, the Vantage Kubernetes agent will begin to upload the data needed to calculate the idle costs. The data will be available on efficiency reports within 48 hours as the costs from the infrastructure provider are ingested.

Kubernetes Rightsizing Recommendations​

Vantage syncs Kubernetes managed workloads as active resources in your account. In cases where any of these workloads are identified to be overprovisioned, Vantage provides Kubernetes rightsizing recommendations. On the Kubernetes Efficiency Reports screen, a notification is displayed when rightsizing recommendations are available. Click Review Recommendations to view identified workloads.

Kubernetes notification for rightsizing recommendations

See the Cost Recommendations documentation for details on how to view this information and rightsize Kubernetes workloads.

Kubernetes Integration Method: The Vantage Kubernetes Agent​

Agent usage data is uploaded several times throughout the day and updated within the Vantage platform nightly. However, Kubernetes costs will not be calculated until the costs from the cluster’s corresponding infrastructure provider are available. These costs might encounter delays based on their associated cloud integration's cost data. For instance, if there is a one-day delay in an AWS Cost and Usage Report, the clusters dependent on that data will experience a similar delay. This often takes 48 hours to complete.

- + \ No newline at end of file diff --git a/kubernetes_agent/index.html b/kubernetes_agent/index.html index c09d3817..26af349d 100644 --- a/kubernetes_agent/index.html +++ b/kubernetes_agent/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Vantage Kubernetes Agent

The Vantage Kubernetes agent is the default, recommended configuration to ingest cost and usage data from Kubernetes clusters to Vantage. The agent is a Docker container that runs in your Kubernetes cluster. The agent collects metrics and uploads them to Vantage.

note

A primary provider (e.g., AWS, Azure, or GCP) is required to connect Kubernetes costs.

Agent Functionality​

The Vantage Kubernetes agent relies on native Kubernetes APIs, such as kube-apiserver for metadata and kubelet for container data. Access to these APIs is controlled via Kubernetes RBAC using a Service Account and ClusterRole included in the Vantage Kubernetes agent Helm chart.

Data is periodically collected and stored for aggregation, then sent directly to the Vantage service through an API, with your Vantage API token for authentication. This process avoids extra storage costs incurred by the OpenCost integration. The agent's architecture eliminates the need for deploying OpenCost-specific Prometheus pods, which makes scaling easier.

Vantage Kubernetes agent architecture diagram

Service Compatibility​

The Vantage Kubernetes agent is compatible with the following services:

  • Amazon Elastic Kubernetes Service (EKS)
  • Azure Kubernetes Service (AKS)
  • Google Kubernetes Engine (GKE)
note

At this time, the agent does not support custom rates for on-premises servers. Note that this is a planned future feature. If you have an on-premises cluster and would like to track these costs, see the OpenCost documentation.

As long as the cost data for an underlying cluster instance is ingested into Vantage via a cloud integration, it is possible to calculate the corresponding pod costs.

Google Kubernetes Engine (GKE) Autopilot​

For GKE Autopilot users, you don’t need to install the agent. These costs will already be present under Cost By Resource for the Kubernetes Engine service in a Cost Report.

GKE Autopilot filters on a Cost Report

Install Vantage Kubernetes Agent​

Prerequisites​

The following prerequisites are required before you install the Vantage Kubernetes agent:

Create a Connection​

info

The following steps are also provided in the Vantage Kubernetes agent Helm chart repository. See the Helm chart repository for all value configurations. If you would like to use a manifest-based option instead, see the section below

To set up a new Kubernetes agent connection:

  1. Add the repository for the Vantage Kubernetes agent Helm chart.

    helm repo add vantage https://vantage-sh.github.io/helm-charts

  2. Install the vantage-kubernetes-agent Helm chart. Ensure you update the values for VANTAGE_API_TOKEN (obtained in the Prerequisites above) and CLUSTER_ID (the unique value for your cluster).

    helm upgrade -n vantage vka vantage/vantage-kubernetes-agent --install --set agent.token=$VANTAGE_API_TOKEN,agent.clusterID=$CLUSTER_ID --create-namespace

Azure Kubernetes Service (AKS) Connections​

If you are creating an AKS connection, you will need to configure the following parameters to avoid AKS-specific errors:

  • Set the VANTAGE_KUBE_SKIP_TLS_VERIFY environment variable to true. This setting is controlled by agent.disableKubeTLSverify within the Helm chart. For details, see the TLS verify error section.
  • Configure the VANTAGE_NODE_ADDRESS_TYPES environment variable, which is controlled by the agent.nodeAddressTypes in the Helm chart. In this case, the type to use for your cluster will most likely be InternalIP. For configuration details, see the DNS lookup error section.

(Optional) Enable Collection of Annotations and Namespace Labels​

You can optionally enable the collection of annotations and namespace labels.

  • Annotations: The agent accepts a comma-separated list of annotation keys, called VANTAGE_ALLOWED_ANNOTATIONS, as an environment variable at startup. To enable the collection of annotations, configure the agent.allowedAnnotations parameter of the Helm chart with a list of annotations to be sent to Vantage. Note there is a max of 10 annotations, and values are truncated after 100 characters.
  • Namespace labels: The agent accepts VANTAGE_COLLECT_NAMESPACE_LABELS as an environment variable at startup. To enable the collection of namespace labels, configure the agent.collectNamespaceLabels parameter of the Helm chart.

Manifest-Based Deployment Option​

You can use helm template to generate a static manifest via the existing repo. This option generates files (YAML) so that you can then decide to deploy them however you want.

  1. Add the repository for the Vantage Kubernetes agent Helm chart.

    helm repo add vantage https://vantage-sh.github.io/helm-charts

  2. Generate the static manifest.

    helm template -n vantage vka vantage/vantage-kubernetes-agent --set agent.token=$VANTAGE_API_TOKEN,agent.clusterID=$CLUSTER_ID

Resource Usage​

The limits provided within the Helm chart are set low to support small clusters (approximately 10 nodes) and should be considered the minimum values for deploying an agent.

Estimates for larger clusters are roughly:

  • ~1 CPU/1000 node
  • ~5 MB/node

For example, a 100-node cluster would be approximately 500 MB and 100 mCPU. These amounts are estimates, which will vary based on pod density per node, label usage, cluster activity, etc. The agent should reach an approximate steady state after about one hour of uptime and can be tuned accordingly after the fact.

To set these options, extend the --set flag. You can also include the values using one of the many options Helm supports:

--set agent.token=$VANTAGE_API_TOKEN,agent.clusterID=$CLUSTER_ID,resources.limits.memory=100Mi,resources.requests.memory=100Mi

Validate Installation​

Follow the steps below to validate the agent's installation.

  1. Once installed, the agent's pod should become READY:
    ➜ kubectl -n vantage get po
    NAME                             READY   STATUS    RESTARTS   AGE
    vka-vantage-kubernetes-agent-0   1/1     Running   0          54m
  2. Logs should be free of ERROR messages:
    ➜  containers kubectl -n vantage logs -f vka-vantage-kubernetes-agent-0
    {"time":"2023-10-23T22:01:12.065481528Z","level":"INFO","msg":"found nodes","nodes":231}
    ...
    {"time":"2023-10-23T22:01:15.471399742Z","level":"INFO","msg":"finished initializing"}
  3. Agent reporting should occur once per hour at the start of the hour and should not generate an ERROR log line. It should also attempt a report soon after the initial start:
    {"time":"2023-10-23T22:01:00.015243974Z","level":"INFO","msg":"reporting now"}
    {"time":"2023-10-23T22:01:01.168390414Z","level":"INFO","msg":"finished reporting"}
    {"time":"2023-10-23T22:01:01.169876296Z","level":"INFO","msg":"next report window","start":"2023-10-23T22:00:00Z","end":"2023-10-23T23:00:00Z","sleeping_seconds":3598.830199804}

Costs are exported from the cluster hourly and then made available nightly. It's important to note that these costs might encounter delays based on their associated cloud integration's cost data. For instance, if there is a one-day delay in an AWS Cost and Usage Report, the clusters dependent on that data will experience a similar delay.

tip

You can view and manage your Kubernetes integration on the Kubernetes Integration page in the console. Hover over the integration in the list, and click Manage.

Monitoring​

The agent exposes a Prometheus metrics endpoint via the /metrics endpoint, exposed by default on port 9010. This port can be changed via the Helm chart's service.port value.

The metrics endpoint includes standard Golang process stats as well as agent-related metrics for node scrape results, node scrape duration, internal data persistence, and reporting.

For users who want to monitor the agent:

  1. vantage_last_node_scrape_count{result="fail"} should be low (between 0 and 1% of total nodes). Some failures may occur as nodes come and go within the cluster, but consistent failures are not expected and should be investigated.
  2. rate(vantage_report_count{result="fail"}[5m]) should be 0. Reporting occurs within the first 5 minutes of every hour and will retry roughly once per minute. Each failure increments this counter. If the agent is unable to report within the first 10 minutes of an hour, some data may be lost from the previous window, as only the previous ~70 data points are retained.

Upgrade the Agent​

To see which version of the Kubernetes agent you are running:

  1. From the top navigation, click Settings.
  2. On the side navigation, click Integrations.
  3. A list of all your provider integrations is displayed. Select the Kubernetes integration.
  4. On the Manage tab, click the settings button (looks like a cog wheel) next to a specific integration.
  5. Scroll down to the Clusters section. Each cluster that is integrated with the agent is listed along with the current agent version and indicates if the agent is out of date.
The Settings Clusters section with two sample clusters displayed along with the most recent version

To upgrade the agent, use the following command:

helm repo update && helm upgrade -n vantage vka vantage/vantage-kubernetes-agent --reuse-values

The version noted in the console for your agent is updated when cost data is imported nightly.

note

AKS users should remember to follow the AKS-specific instructions again when updating.

Common Errors​

DNS Lookup Error​

The agent uses the node status addresses to determine what hostname to look up for the node's stats, which are available via the /metrics/resource endpoint. This can be configured with the VANTAGE_NODE_ADDRESS_TYPES environment variable, which is controlled by the agent.nodeAddressTypes in the Helm chart. By default, the priority order is Hostname,InternalDNS,InternalIP,ExternalDNS,ExternalIP.

To understand which type to use for your cluster, you can look at the available addresses for one of your nodes. The type corresponds to one of the configurable nodeAddressTypes.

➜  kubectl get nodes -o=jsonpath='{.items[0].status.addresses}'
[{"address":"10.0.12.185","type":"InternalIP"},{"address":"ip-10-0-12-185.ec2.internal","type":"InternalDNS"},{"address":"ip-10-0-12-185.ec2.internal","type":"Hostname"}]

EOF Error When Starting​

The agent uses local files for recovering from crashes or restarts. If this backup file becomes corrupted, most commonly due to OOMKill, the most straightforward approach to get the agent running again is to perform a fresh install or remove the PersistentVolumeClaim, PersistentVolume, and Pod.

An example error log line might look like:

{"time":"2023-12-01T00:00:00.000000000Z","level":"ERROR","msg":"failed to setup data store","err":"unexpected EOF"}

To uninstall the agent via helm, run:

helm uninstall vka -n vantage

Then, follow the original installation steps outlined in the above sections.

TLS Verify Error When Scraping Nodes​

The agent connects to each node to collect usage metrics from the /metrics/resources endpoint. This access is managed via Kubernetes RBAC, but in some cases, the node's TLS certificate may not be valid and will result in TLS errors when attempting this connection. This most often affects clusters in AKS. To skip TLS verify within the Kubernetes client, you can set the VANTAGE_KUBE_SKIP_TLS_VERIFY environment variable to true. This setting is controlled by agent.disableKubeTLSverify within the Helm chart. This does not affect requests outside of the cluster itself, such as to the Vantage API or S3.

An example error log line might look like:

{"time":"2024-02-10T12:00:00.000000000Z","level":"ERROR","msg":"failed to scrape node","err":"Get \"https://10.100.20.20:10250/metrics/resource\": tls: failed to verify certificate: x509: cannot validate certificate for 10.100.20.20 because it doesn't contain any IP SANs","node":"aks-nodepool9ids-1234567-vm0000001"}

Once changed, you can validate the change by looking for the scraping summary log line and ensuring no more ERROR level messages appear:

{"time":"2024-02-10T12:00:00.000000000Z","level":"INFO","msg":"finished scraping metrics from nodes","success":25,"failure":0,"duration_ms":102}

Pod Scheduling Errors​

The most common cause for pod scheduling errors is the persistent volume not being provisioned. By default, the agent is deployed as a StatefulSet with a persistent volume for persisting internal state. The state allows the agent to recover from a restart without losing the historical data for the current reporting window. An example error for this case would be present in the events on the vka-vantage-kubernetes-agent-0 pod and include an error that contains unbound immediate PersistentVolumeClaims.

The resolution to this error is based on the cluster's configuration and the specific cloud provider. More information might be present on the persistent volume claim or persistent volume. For Kubernetes clusters on AWS, S3 can be used for data persistence, which is documented in the next section.

Additional provider references are also listed here:

Volume Support Error​

If you see an error related to binding volumes: context deadline exceeded, this means you may not have volume support on your cluster. This error typically occurs when your cluster is unable to provision or attach persistent storage volumes required by your applications. Check your cluster's configuration and ensure the storage provider is properly set up.

(Optional) Use S3 for Data Persistence​

The agent requires a persistent store for periodic backups of time-series data as well as checkpointing for periodic reporting. The default deployment option uses a Persistent Volume and works for clusters ranging from tens to thousands of nodes; however, if Persistent Volumes are not supported with your cluster, an alternative configuration, using S3, is available for agents deployed in AWS. If you require persistence to a different object store, you can contact support@vantage.sh.

Configure Agent for S3 Persistence​

The agent uses IAM roles for service accounts to access the configured bucket. The default vantage namespace and vka-vantage-kubernetes-agent service account names may vary based on your configuration.

Below are the expected associated permissions for the IAM role:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "s3:GetObject",
        "s3:PutObject",
        "s3:ListBucket",
        "s3:AbortMultipartUpload",
        "s3:ListMultipartUploadParts",
        "s3:DeleteObject"
      ],
      "Resource": [
        "arn:aws:s3:::example-bucket-name/*",
        "arn:aws:s3:::example-bucket-name"
      ]
    }
  ]
}

Once the permissions are available, the agent can be configured to start with S3 persistence via the environment variable VANTAGE_PERSIST_S3_BUCKET or, if using the Helm chart, via the --set persist=null --set persistS3.bucket=example-bucket-name values.

The agent will write persisted data to the $CLUSTER_ID/ prefix within the bucket. Multiple agents can use the same bucket as long as they do not have overlapping CLUSTER_ID values. An optional prefix can be prepended with VANTAGE_PERSIST_S3_PREFIX resulting in $VANTAGE_PERSIST_S3_PREFIX/$CLUSTER_ID/ being the prefix used by the agent for all objects uploaded.

Active Resources and Rightsizing Recommendations​

note

Rightsizing recommendations require version 1.0.24 or later of the Vantage Kubernetes agent. See the upgrading section for information on how to upgrade the agent. Once the upgrade is complete, the agent will begin uploading the data needed to generate rightsizing recommendations. After the agent is upgraded or installed, recommendations will become available within 48 hours. This step is required to ensure there is enough data to make a valid recommendation. Historical data is not available before the agent upgrade, so it is recommended that you observe cyclical resource usage patterns, such as a weekly spike when you first review recommendations.

Vantage syncs Kubernetes managed workloads as active resources in your account. In cases where these workloads are identified to be overprovisioned, Vantage provides Kubernetes rightsizing recommendations. See the Cost Recommendations documentation for details on how to view rightsizing recommendations for Kubernetes workloads.

tip

For a full guide on understanding rightsizing and how to rightsize Kubernetes workloads, see the following article in the Cloud Cost Handbook.

Migrate Costs from OpenCost to Vantage Kubernetes Agent​

If you are moving from an OpenCost integration to the agent-based integration, you can contact support@vantage.sh to have your previous integration data maintained. Any overlapping data will be removed from the agent data by the Vantage team.

Maintaining OpenCost Filters​

If you previously used the OpenCost integration and are transitioning to the new agent-based integration, your existing filters will be retained. It's important to note that in situations where labels contained characters excluded from Prometheus labels, such as -, the OpenCost integration received the normalized versions of those labels from Prometheus. The Vantage Kubernetes agent, on the other hand, directly retrieves labels from the kube-apiserver, resulting in more precise data. However, this change may necessitate updates to filters that previously relied on the normalized values. You can contact support@vantage.sh to have these filters converted for you.

- + \ No newline at end of file diff --git a/network_flow_reports/index.html b/network_flow_reports/index.html index d7e2580f..0d05733e 100644 --- a/network_flow_reports/index.html +++ b/network_flow_reports/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Network Flow Reports

For any network-enabled resource, Network Flow Reports provide visibility by source and destination to the flows within your network that are driving costs. You can filter these reports to identify resources that are accruing network costs, generate detailed views of the sources and destinations of the network traffic, and investigate metadata on specific resources in the flow. This feature makes it possible to correlate data transfer charges with both external services, such as Datadog, and internal applications.

note

At this time, only AWS is supported. Additional support for providers with flow log functionality, such as Azure and Google Cloud, is planned for the future.

Set Up VPC Flow Log Integration​

Network Flow Reports require an existing AWS provider integration. The Vantage AWS account-specific IAM role needs to be granted access to the S3 buckets where you publish your VPC Flow Logs. Vantage can automatically detect any existing S3 buckets that contain VPC Flow Logs. You need to configure this integration for each AWS account that has an S3 bucket with VPC Flow Logs.

note

The Vantage configuration does not work with Amazon CloudWatch because of the high cost of querying CloudWatch. Logs need to be published to S3 for the Vantage integration to work.

Prerequisites​

Ensure you have at least the following fields in your VPC Flow Log format to increase the discoverability of network-related costs. If you do not have these fields enabled, Vantage may be unable to properly correlate your network flows to estimated costs.

${action} ${bytes} ${dstaddr} ${start} ${end} ${flow-direction} ${log-status} ${region} ${srcaddr} ${account-id} ${instance-id} ${interface-id} ${subnet-id} ${vpc-id} ${az-id}

See the AWS documentation for information on how to set up VPC Flow Logs that publish to S3. Vantage can ingest both Text and Parquet log file formats.

Cost to Enable VPC Flow Logs in AWS​

When you enable VPC Flow Logs, you incur both S3 storage costs and CloudWatch data ingestion costs on your AWS bill. These charges are represented in the costs for the S3 bucket where your flow logs are written to as well as an S3-Egress fee from CloudWatch. Unfortunately, there is no way around these costs being incurred. Vantage has contacted various AWS platform teams to attempt to remove this cost, but this is likely a limitation that AWS is unwilling to change or remove.

These logs are considered Vended Logs. You can create a Cost Report that monitors these charges:

  • Set Provider to AWS.
  • Set Subcategory to AmazonCloudWatch contains VendedLog.

Note that Vended Logs can include other cost sources besides VPC Flow Logs, but you can expect an increase in those costs after enabling them. The filters for this Cost Report are provided below.

Cost Report with filters for Vended Logs

info

For more information about VPC Flow Logs pricing, see this Cloud Cost Handbook article.

Enable the Integration​

  1. From the top navigation bar, click Active Resources.
  2. From the side navigation bar, select Network Flow Reports.
  3. Click Configure VPC Flow Logs.
    note

    See the Troubleshooting section if you are running into issues with seeing some of your flow logs on the onboarding workflow.

  4. All flow logs that have been synced as active resources in Vantage are displayed in the left panel of the onboarding workflow. Click the checkbox next to any listed flow log to select all log files. You can also click the down arrow to the right of any flow log and select or deselect specific log files listed.
    tip

    If you do not see specific flow log files, check whether they are synced as active resources in Vantage. Ensure that all accounts where there are flow logs have active resources enabled in Vantage.

  5. When you select the checkbox, the Sync All toggle is automatically enabled. You can disable this option if you do not want the files to automatically sync again each night.
  6. The right panel contains instructions on how to get set up using the AWS CLI, AWS Management Console, or the Vantage Terraform provider. Select the tab for your preferred option. If you have multiple connected accounts with VPC Flow Logs, instructions or code samples are provided for each account.
  7. After you run the code in the AWS CLI, deploy your Terraform configuration, or complete the steps in the AWS Management Console, click Check Permissions. A message is displayed that indicates whether the bucket permissions were successfully set up or if they are missing. A red X is displayed next to any buckets in the left panel that do not have sufficient permissions. Some log files may also be unsupported. See the section below for details.
  8. Once permissions are successfully set up, click Connect. A message is displayed that indicates your flow logs are being imported. Click Check Import Status to review the status of your integration. A Processing… status is displayed until the import is complete.

Data is usually available within 24 hours of initially enabling the integration. You will receive an email once the data import is complete. Vantage ingests your logs nightly.

Unsupported Logs​

When a particular log cannot be imported, Vantage displays either an UNSUPPORTED TRAFFIC, UNSUPPORTED DESTINATION, or UNSUPPORTED LOG FORMAT label next to the log name in the Manage VPC Flow Logs window. Hover your mouse over this label to see additional information about the issue.

IssueDescription
UNSUPPORTED TRAFFICVantage does not import any REJECT flows, nor any flows that do not generate corresponding costs.
UNSUPPORTED DESTINATIONThis message is displayed if a log is going to any destination other than S3. Logs need to be published to S3 to be imported by Vantage.
UNSUPPORTED LOG FORMATUnsupported log format means that your log may be missing some required columns. Hover over the UNSUPPORTED LOG FORMAT label to see a list of missing columns. Ensure your logs contain the columns noted in the Prerequisites section.

Troubleshooting​

When you click Check Permissions during the onboarding process, an error is displayed when you the correct permissions are not set up. Ensure that you add the correct permissions displayed in the onboarding workflow for each account.

KMS Encrypted Buckets​

An error is displayed for buckets that are encrypted with AWS Key Management Service (KMS). You will need to either remove encryption on these buckets or provide Vantage the necessary permissions to decrypt (i.e., kms:Decrypt).

No Logs Displayed​

You may see a message indicating No VPC flow logs with log destination found. If you have recently created these resources it may take up to 24 hours for Vantage to sync the metadata. Wait at least 24 hours if you recently created new resources. This can also be an issue if you have not enabled active resource syncing. To enable syncing:

  1. Navigate to the Workspaces section of the console.
  2. Select the workspace your AWS integration is set up.
  3. At the top, ensure Active Resource Syncing is turned on.
Active Resource Syncing in the Workspaces UI

Manage Existing Integrations​

You can view your integration status and add additional flow logs from the VPC Flow Logs integration page. At the top of the Manage Connected VPC Flow Logs panel, click Manage. The Manage Flow Logs pop-up window is displayed. After the initial import, you can perform the following actions from this window:

  • Select additional S3 buckets and logs to sync
  • Deselect an S3 bucket or log files to remove the bucket from syncing
note

If you add additional fields to your VPC Flow Log format in AWS, and you already sync these logs to Vantage, this new data will be imported to Vantage on the next nightly import.

Create a New Network Flow Report​

Follow the steps below to create a new Network Flow Report:

  1. From the top navigation, click Active Resources.

  2. From the side navigation, click Network Flow Reports. All your existing Network Flow Reports are displayed, along with who created the report and the date it was created.

    tip

    Three reports are provided, by default, on this page: All Network Flow Logs, Cross-AZ Traffic, and Public Traffic Destinations. See the Network Flow Report Examples section below for tips on how to get started with these reports.

  3. To create a new report, click New Network Flow Report.

  4. A new Network Flow Report is displayed.

    • At the top of the report, a Sankey diagram is provided. This diagram shows different network flows, based on your selected filters and grouping criteria. For example, in the image below, the nodes on the left side of the diagram show the sources of network traffic. Links, or network flows, flow from the nodes to their traffic destination (in this example, cross-AZ or public). The width of each flow corresponds with the volume of traffic or estimated cost, based on your settings, and the color corresponds with the source of the node (e.g., yellow for public in the example below).
      Sample Network Flow Report with cross-AZ and public traffic
    • In the table below the diagram, the network flow information is displayed along with the volume of traffic (in bytes). The table is sorted in descending order by the Estimated Cost column. Click any column header to change the sort order. Each flow shows the estimated cost associated with that specific traffic route, helping you identify the most expensive data transfers. (See the section below for details on how the Estimated Cost column is calculated.)
    • For each listed resource, a link to the Active Resources screen is provided. Click this link to view additional metadata about the resource. From the Active Resources screen, click the Relationships tab to view any associated resources, such as a corresponding IGW for a VPC resource.

  5. You can update the criteria displayed in the Sankey diagram with the following options:

    • By default, both egress and ingress traffic are displayed. Expand the Flow Direction menu above the diagram to change the flow to only Egress or Ingress.
    • From the top right of the diagram, update the date range that’s displayed. Click the calendar icon and select an option, such as Last 7 Days, This Month, etc.
      note

      By default, Vantage ingests 7 days of network flows into your account and keeps the data available for 31 days. For Enterprise customers, this retention period can be adjusted. Contact support@vantage.sh if you need a longer retention period.

    • You can move the columns in the table at the bottom to visualize different flows. The diagram is also updated to depict the new order in the table.
      Click to view example image
    • You can also filter and group/add more columns to the report. See the next section for details.

  6. To save the report, from the top right of the screen, click Save as New. Enter a report name, then click Save. (To edit this name, click the pencil icon in the breadcrumbs above the chart, next to the report's name.)

Filter and Group a Network Flow Report​

By default, a Network Flow Report is grouped by the following fields:

  • Source Resource UUID
  • Peer Resource UUID
  • Traffic Category

You can filter and group by multiple criteria in Network Flow Reports. Expand the box below to see all available filter and grouping criteria with a description of each option.

Click to view all fields
Vantage FieldDescriptionExample
Account IDAWS account ID of the source networkproduction, 123456789012
Availability Zone IDID of the source Availability Zoneus-east-1a
Destination AddressSpecific IP address that identifies the location of where the traffic is being sentAn IP, like 1.23.456.90
Destination HostnameDomain name that corresponds with the IP address of the destination (see note below table)01234.broadband.com

OR

Datadog

A dsthostname:null value means Vantage is unable to reverse DNS the dst_address IP address.
Flow DirectionMovement of network traffic relative to a specific network interfaceIngress or egress
Interface IDSource ENI IDeni-001d78b2agh4caa05
Instance IDSource instance IDi-0b22a22eec53b9321
Peer Resource UUIDDestination resource ARN or tag (if available)eni-c123ab7f9c55af9a6d

OR

example-tag
Peer Account IDDestination account IDproduction, 123456789012
Peer VPC IDDestination VPC IDvpc-12a34567b8g8a03ef
Peer Region IDAWS Region of destinationus-west-2
Peer Availability Zone IDID of the Availability Zone for the destinationus-east-1b
Peer Subnet IDDestination subnet IDsubnet-123ab7f9c55af9a6d
Peer Interface IDDestination ENI IDeni-001d78b2agh4caa12
Peer Instance IDDestination instance IDi-0b22a22eec53b9321
RegionAWS Region of the sourceus-east-1
Resource UUIDSource resource ARN or tag (if available)eni-c123ab7f9c55af9a6d

OR

example-tag
Source AddressSpecific IP address from which the network traffic originatesAn IP, like 1.23.456.90
Source HostnameDomain name that corresponds with the IP address of the source (see note below table)100.123.456.789.bc.googleusercontent.com

OR

Datadog
Subnet IDID of the source subnetsubnet-123ab7f9c55af9a6d
Traffic CategoryThe type of trafficpublic, cross-AZ, cross-region, unknown

An Unknown value means Vantage is unable to categorize the type of traffic based on the available metadata.
Traffic PathPath traffic takes to reach the destination, such as through a virtual private gateway
  • In VPC
  • Internet Gateway or Gateway VPC Endpoint
  • Virtual Private Gateway
  • Intra-Region VPC Peering
  • Inter-Region VPC Peering
  • Local Gateway
  • Gateway VPC Endpoint (Nitro-based instances)
  • Internet Gateway (Nitro-based instances)
VPC IDID of the source VPCvpc-12a34567b8g8a03ef
note

To derive the hostname, Vantage checks against some hardcoded IP ranges, and then falls back to reverse DNS lookup for the IPs. If you have services with known IP ranges you want added, contact support@vantage.sh.

Apply Filter Criteria​

You can add additional fields via grouping and filtering criteria. To add a new filter:

  1. Click the Filters button on the top left of the diagram.
    • The AWS costs where... tile is displayed. Click + New Rule.
    • From the filter dropdown menu, select an option, like Account ID, Instance ID, etc.
    • Two additional dropdown menus are displayed. Select is, is not, contains, or does not contain based on your desired filter criteria, then select one or more values from the second dropdown menu. For contains or does not contain, enter any text criteria to filter by.
      note

      If you are unable to see any values for a filter, this means that you are not capturing this information in your VPC Flow Logs format, and therefore, Vantage is unable to import this data.

    • Click Add.
      Click to view example image
  2. You can optionally edit your existing rule or add additional filter criteria.
    • To edit the rule you just created, select the rule, make your changes, and click Add.
    • If you want to add a rule to filter multiple criteria, such as filter by certain Regions and another rule to filter by certain Destination Hostnames, click + New Rule. Add the additional criteria and click Add.
    • To add a separate rule set, above the filter set, click + New Filter. This rule set will be displayed as Or AWS costs where... on the new tile.
    • To delete a rule set, click the trashcan icon on the top right of the rule set.
      Click to view example image
  3. Above the rule set(s), click Apply. The diagram will update with your existing filter criteria.

Apply Grouping Criteria​

To add additional columns to the table and diagram, expand the Group By menu. Select or deselect grouping criteria. As you add grouping criteria, additional nodes and flows are displayed on the diagram. Additional columns are also added to the table for any new grouping criteria.

Adjust Flow Weight​

By default, the Sankey diagram is weighted by estimated cost. You can change this view to be weighted by bytes, or volume. Above the chart, click the Flow Weight menu and select Costs or Bytes. The Sankey diagram is updated accordingly. When you hover over a flow, the corresponding cost or volume in bytes is displayed in the tooltip.

View Flow Log Metadata​

For certain grouping criteria, you can view additional details about specific resources. Vantage provides this information when it can fetch provider resource metadata. If Vantage can resolve the IP address for the Source Address and Destination Address grouping criteria, it will also provide metadata for these groupings.

  1. Expand the Group By menu and add one or more of the following options to your grouping criteria:
    • Interface ID/Peer Interface ID
    • Subnet ID/Peer Subnet ID
    • VPC ID/Peer VPC ID
    • UUID/Peer UUID
  2. In the table, select the row for any resource. The Flow Log Metadata panel is displayed on the right side of the screen. Data is provided for the Peer and Peer Resource. In this panel, click the link for any listed resource to see a provider resource report displayed.

Estimated Cost Calculation for Network Flows​

The estimated cost for each flow is calculated by applying your blended data transfer rates to the flow of traffic. For example, if a flow is moving between one subnet to another and those subnets are in different Availability Zones, Vantage applies your cross-AZ data transfer rate to those bytes.

note

Because data transfer rates can be tiered, and the metadata associated with the destination may change, this calculation is a best-effort calculation; however, it does help to identify cost hotspots within your network.

The flow logs cost calculation is based on the following formula:

Estimated Cost=∑i=1N(Ratei×Volumei)Estimated\ Cost=\sum_{i=1}^{N} (Rate_{i} \times Volume_{i})
  • NN is the total number of data flows.
  • RiR_i is the rate (cost per unit of data) for the ii-th flow.
  • ViV_i is the volume of data transferred for the ii-th flow.

Vantage first identifies the different flows of data within your network. It uses information provided within the AWS Cost and Usage Reports (CUR) to determine the specific rate (cost per unit of data) that applies to each type of data flow (e.g., cross-AZ, public). Each rate for each data flow is multiplied by the amount of data transferred in that flow. The estimated cost is then determined by the sum of these products.

Network Costs on Cost Reports​

On Cost Reports, for resources that generate network traffic costs (e.g., NAT Gateways), a Network Costs button is displayed in the Cost Report list. Click this button to view a Network Flow Report that is filtered to flows coming from that specific resource.

The below Cost Report is grouped by Service and Resource.

Network Costs option on a Cost Report

Network Flow Report Examples​

The following examples demonstrate common scenarios for using Network Flow Reports. These examples are based on the three reports that Vantage provides by default: All Network Flow Logs, Cross-AZ Traffic, and Public Traffic Destinations.

Sample Network Flow Report with cross-AZ and public traffic

Example 1: View All Network Traffic​

The All Network Flow Logs report shows all your network flows. The flow’s Resource UUID and Peer Resource UUID are provided as well as the traffic category (e.g., public). Review this report to get a high-level view of all your traffic flows.

Sample Network Flow Report with cross-AZ and public traffic

Example 2: Identify Cross-AZ Traffic​

Cross-AZ data transfer within AWS incurs higher costs compared to intra-AZ data transfer. According to AWS, “For data transferred between a Local Zone and an Availability Zone within the same AWS Region, "in" to and "out" from Amazon EC2 in the Local Zone” data is charged at $0.01/GB for both transfer in and transfer out. Transferring data between AZs requires more network bandwidth compared to transferring data within the same AZ. This additional bandwidth consumption contributes to higher costs.

In the provided cross-AZ report, you can view all cross-AZ traffic along with flow size and estimated cost. The Peer Availability Zone ID column shows exactly where the traffic is flowing. You can see both the source and peer AZs along with the associated source and peer resources.

Sample Network Flow Report with all cross-AZ traffic

Review the highest-costing flows and consider the following tips:

  • Try to place dependent resources within the same AZ to minimize cross-AZ data transfer.
  • Use VPC endpoints to route traffic internally within AWS, reducing the need for cross-AZ traffic. This can help in minimizing data transfer costs and enhance security by keeping everything in the same VPC.

Example 3: Examine Public Traffic​

When monitoring network costs, analyzing public traffic can reveal significant insights about where your traffic is going when it reaches the public internet. By analyzing destination details, you can ensure that traffic is taking the correct path or is going only to trusted and necessary endpoints. In this report, the Destination Hostname grouping/column provides a human-readable format of the destination, helping you quickly identify known destination services or endpoints.

Sample Network Flow Report with all public traffic

Vantage identifies hostnames using a reverse DNS lookup, or when vendors publish static IP address ranges, such as Datadog, Vantage can associate these IP addresses with the name of the service. The Destination Address provides the exact IP address, which is useful for detailed analysis to ensure traffic is reaching the intended destinations.

Examine this report to understand which resources are generating public traffic and where that traffic is going. Consider whether you might use alternative services, like AWS Direct Connect, CloudFront, or PrivateLink, to optimize data transfer and reduce costs.

- + \ No newline at end of file diff --git a/overview/index.html b/overview/index.html index 775bad46..046ce9dd 100644 --- a/overview/index.html +++ b/overview/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Overview

Once you create some provider integrations, Vantage will automatically begin ingesting billing information for your account. The default landing page in the Vantage console is the Overview page. This page serves as an executive-level summary, providing a comprehensive snapshot of the cost metrics that matter most to you. Review widgets on the Overview page for high-level cost summaries.

note

When a user navigates to console.vantage.sh, the Overview page is displayed. An individual user or owner of a team can configure a default dashboard to be displayed instead of the Overview page. See the Default Dashboards documentation for details.

Overview page

Depending on your provider connections, you will see some of the following widgets:
A widget that provides a clear comparison between your total on-demand vs. committed spend. This view helps you understand your expenses for on-demand resources in contrast to cost-saving strategies, like Savings Plans, Reserved Instances, Enterprise Discount Programs, and Committed Use Discounts.
- + \ No newline at end of file diff --git a/partners/index.html b/partners/index.html index e2a706b0..579bd6d6 100644 --- a/partners/index.html +++ b/partners/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Vantage for MSPs

Vantage provides an administrative portal for Managed Service Providers, or MSPs (also sometimes referred to as Resellers), to provision and centrally manage Vantage accounts on behalf of their end customers. MSPs can access this portal from their management account and move between each of their customer accounts.

Getting Started

If you are interested in this functionality, contact partnerships@vantage.sh. Your Vantage account will be set up to include a Vantage for MSPs administrative portal.

If you already have separate accounts for your customers in Vantage and want to consolidate them to this model, contact support@vantage.sh.

Partner Settings​

The Partner Settings section in Vantage has two different sections: Managed Accounts and Billing Rules.

  • The Managed Accounts screen is the central administrative portal that MSPs can use to perform the following actions:
    • Create new customer accounts and update their name/contact email
    • Delete existing customer accounts
    • Log in to a customer’s account
    • Add integrations on behalf of a customer’s account
    • Assign billing rules to a customer’s account
  • On the Billing Rules screen, you can create custom billing adjustments, one-time charges, re-rating, and MSP-level discounts. See the Billing Rules section for additional information.

Create a New Customer Account​

A customer account functions just like a regular Vantage account; however, customers cannot view or manage subscriptions to Vantage. All Vantage features, like reports, SSO, and Slack/MS Teams integrations, are available and scoped to each customer account.

To provision a new customer account:

  1. Log in to your Vantage for MSPs management account.
  2. From the top navigation, click Settings.
  3. From the left navigation, under Partner Settings, select Managed Accounts.
  4. The Managed Accounts administrative portal is displayed. All existing customer accounts are displayed along with the Account Name, Contact Email, and the date when the account was created. At the top, click New Managed Account.
    Managed accounts screen with two existing accounts
  5. Enter an Account Name and a Contact Email Address. The email address is your administrator ID for this account and therefore must match your company’s email domain. The email address cannot exist for another customer account; however, an alias is acceptable, like admin+customer@yourdomain.com.
    Pop-up window for creating a new managed account
  6. Click Create Account.

Access a Customer Account​

From the Managed Accounts screen, you can move between each of your customer accounts.

  1. Next to any customer account’s name, click Enter Account →.
  2. The customer account is displayed. When you enter a customer's account, you are considered the Manager User for that account.
    • A yellow bar is displayed around the border of the screen to indicate you are logged in to the customer's account.
    • On the bottom left, a pop-up is displayed to indicate which customer account you are logged in to.
      A bar is displayed around a customer's account that the manager user is logged into

Perform one of the following actions to return to your management account:

  • On the top right, click your user icon. Then, click Return to MSP account.
  • On the bottom left of the screen, click the X in the Logged in as pop-up.

Once you are back in the management account, a confirmation message is displayed at the top.

Confirmation message that indicated you returned to the MSP account

Single Sign-On for Customer Accounts​

After a customer account is created, you can enable Single Sign-On (SSO) for each customer account. Enter the customer account and then follow the instructions provided in the SSO documentation to enable SSO directly within the customer's account. Customers can also enable SSO directly from their customer account. SSO is scoped to the customer’s account.

Add Integrations to Customer Account​

The way you add integrations to a customer account depends on how your MSP is set up. There are two available workflows:

  • Workflow 1 - Unconsolidated Organizations: An example MSP structure for this workflow might be where you have completely separate AWS Organizations set up for each customer. As an MSP, you have access to the payer account, and the customer has access to a member account. In this case, follow the steps below to Configure Integrations in the Customer Account.
  • Workflow 2 - Consolidated Organizations: In this setup, the MSP uses a single AWS Organization that includes multiple linked accounts under a centralized management account. In this case, follow the steps below to Configure Integrations in the Management Account

Configure Integrations in the Customer Account (Unconsolidated Organization Workflow, Most Common)​

If this is the first time you are adding an integration:

  1. From the Managed Accounts screen, enter a customer’s account. If this is the first time you are connecting integrations for a customer, the Connect Accounts screen is displayed.
  2. Select an integration and follow the steps provided in the console.

If you are adding another integration:

  1. From the top navigation, select Settings.
  2. On the right navigation, click Integrations. All available integrations are displayed. Select an integration to get started.
tip

See the Quickstart for a list of all other existing Vantage provider integrations, with links to each provider integration walkthrough.

Configure Integrations in the Management Account (Consolidated Organization Workflow, Less Common)​

This workflow requires that you first set up an integration in your MSP account. From the Managed Accounts screen, you can add any of your connected integrations to a customer account.

To get started, ensure that you have connected a provider integration to your management account. See the AWS multiple accounts documentation for information on how to connect a management account with multiple linked accounts. Note that provider integrations passed down to customer accounts from an MSP's provider integrations will only be available in the first workspace of that customer. After you have connected an integration to your MSP account, follow the steps below to associate them with customer accounts.

  1. From the Managed Accounts screen, select a customer’s account.
  2. Select the Integrations tab. All connected provider integrations for that customer are displayed. The account status, such as Stable or Error, is also displayed.
  3. To add a new connection, click Connect next to any listed provider.
  4. Select any of the listed provider accounts that you want to import data from.
  5. Click Save.
The Integrations screen for a managed account

Customer Managed Account Integration View​

When an MSP manages an integration in their MSP management account, a customer can view the managed integration’s status. The customer cannot remove this type of integration.

  1. From a customer’s account, click Settings in the top navigation.
  2. On the left navigation, under MSP Settings, click Managed Integrations.
  3. Any connected integrations managed by the MSP are displayed.
Customer's view of the managed accounts screen

Create Resources in a Customer Account​

When you are logged in to a customer’s account, you can create Vantage resources, like Cost Reports, Virtual Tags, etc. For any resources, such as a Cost Report, that a management account user creates in a customer’s account, the Created By field displays the name Manager User.

Resource in a customer's account with the Manager User as the creator

Billing Rules​

Custom billing rules can be created in the management account and optionally applied to any of your customer accounts. The following billing rules are available:

  • Exclusion: Exclusion of specific line items (such as EDP discounts)
  • Credits and Charges: Additional charges or credits (such as one-time management fees)
  • Adjustment: Re-rating of existing services (such as Amazon CloudFront data transfer charges)

Create Custom Billing Rules​

To add new billing rules:

  1. Log in to your Vantage for MSPs management account.
  2. From the top navigation, click Settings.
  3. From the left navigation, under Partner Settings, select Billing Rules.
  4. All your existing billing rules are displayed. Click New Billing Rule, then select Adjustment, Charge, Credit, or Exclusion. Click the tabs below for instructions on each billing rule type.

With adjustments, you can set adjusted rates per service (e.g., Amazon CloudFront) or category (e.g., Data Transfer).

  1. Enter a rule Title, such as CloudFront Re-rating.
  2. Select a Service, such as Amazon CloudFront.
  3. Optionally, enter a Category, such as Data Transfer.
    • Tip: To see Category names, navigate to the Cost Reports screen and create a new Cost Report. Above the graph, expand the Group By menu and select Category. A list of existing category options is displayed.
  4. Enter a percentage value that will be shown to the customer. For example, if you enter 75.0, then in the example above, 75% of Amazon CloudFront Data Transfer costs will be shown to the customer.

Assign Billing Rules to Customer Account​

You can select which rules you want added to customer accounts.

  1. From the Managed Accounts screen, select any of your listed customer accounts.
  2. Select the Billings Rules tab.
  3. Click Assign a Billing Rule.
  4. Select one or more billing rules and click Save. The billing rule is applied to the customer’s costs. A customer will only be able to see credits and charges. Exclusions and adjustments are not shown in the customer view.

Role-Based Access Control​

Vantage for MSPs has additional role-based access control permissions for the management account. See the Role-Based Access Control documentation for additional information on RBAC in Vantage.

RoleDescription
OwnersHave full control over the management account and customer accounts. They can add new customer accounts, create resources in customer accounts, and create integrations in customer accounts. They can also delete customer accounts.
EditorsEditors can switch into customer accounts and manage customer accounts, but they cannot make changes to the management account.
ViewersViewers will only be able to view the management account.

Remove a Customer’s Account​

You can either unlink or delete a customer’s account. MSP customers cannot delete accounts.

note

If you are a customer and want your account deleted, contact your MSP.

  • If you want to only unlink an account, but not delete the account, contact support@vantage.sh. The account will still exist in Vantage.
  • When an account is completely deleted, the account is unlinked from the MSP and also completely deleted from Vantage. To delete a customer account, click the trash can icon next to the account name on the Managed Accounts screen.
Warning

Deleting a customer's account is a permanent action and will remove any connected customer integrations.

Customers: Getting Started with Vantage​

As you onboard your customers to Vantage, the following resources are available to help customers get started with Vantage features.

  • Quickstart: Information on how to get started with each Vantage provider integration and the cost reporting data that’s collected
  • Vantage University: A suite of training videos and guides to introduce basic Vantage concepts and features
  • Cost Reports: Create your first Cost Report on Vantage
- + \ No newline at end of file diff --git a/per_unit_costs/index.html b/per_unit_costs/index.html index 9d3fe7bf..eb82c1af 100644 --- a/per_unit_costs/index.html +++ b/per_unit_costs/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Unit Costs

A unit is any metric that your business tracks, such as users, requests, transactions, customers, vendors, and so on. Unit costs can help you analyze the cost of goods sold (COGS). You can add unit costs as a visualization on Cost Reports to visualize your cloud infrastructure costs on a per unit basis. Business metrics are the units of data from your business that are aggregated and combined with costs to produce per unit costs on Cost Reports. By importing these business metrics into Vantage, you can track unit costs, like cost per daily active user, COGS per customer, cost per million API requests, etc.

In the visual example below, the business metric Per Requests per Second is visualized in the graph as a red line alongside daily costs. You can use this visualization to understand how changes in the request metric contribute to changes in your costs.

Per Unit Costs displayed as a trend line on the graph in a Cost Report

Labeled Business Metrics​

You can optionally include a label for each uploaded metric. The label identifies the source of the metric—like an associated application or cost center. For example, a metric like Monthly Active Users typically applies to more than one application. The ability to allocate these metrics is important for analyzing both overall user activity and individual application performance, enabling more informed decision-making at the application level.

In the above example, you can create labels like Active Users App A, Active Users App B, etc. When you assign this metric to a Cost Report, you can decide which labels to include on the Cost Report and in the per unit cost calculation. Any labels you decide to include will be aggregated in the per unit cost calculation. So, in this example, if you decide to include only data with the Active Users App A label, then unit costs will be calculated only for that set of data. If you also include Active Users App B, then the per unit cost calculation will aggregate both sets of labeled data.

Import Business Metrics​

tip

To get started with business metrics and unit costs, you can also view a video demo on Vantage University 🎓.

Business metrics can be imported from other systems directly into Vantage and analyzed alongside cost data. You can create automatic import integrations with Amazon CloudWatch, manually import these metrics from a CSV file, or automatically upload metrics via the Vantage API.

note

The following steps are for importing via CloudWatch or a CSV file. If you want to automatically import metrics, see Import via the Vantage API.

  1. From the top navigation, click Financial Planning.
  2. On the left navigation, click Business Metrics. All existing business metrics are displayed. You can edit or delete business metrics from this screen.
  3. From the top right of the screen, click New Business Metric.
  4. Enter a business metric Title and click Create Business Metric.
  5. The Business Metrics screen is displayed:

Import from a CSV File​

You can upload a CSV file that uses the following three-column format. This CSV file can replace existing data or be used to import new data. You can supply up to six months of metrics.

The date column must be in YYYY-MM-DD format. The amount column must be a number. The label column is optional. See the section above for more information about labels.

note

A label can be added once per date.

date,amount,label
2024-01-09,295,app1
2024-01-16,909,app1
2024-01-23,934,app1
2024-01-30,772,app1
2024-01-09,344,app2
2024-01-16,789,app2
2024-01-23,922,app2
2024-01-30,768,app2
...

Click Upload a CSV. Select the CSV file and upload. After the file is imported, a dropdown menu for each month is displayed. For months with imported metrics, the date and associated metric number are displayed. Months with no metrics are blank.

Click to view visual example
The Imported Costs section with costs displayed for a month

To add additional metrics or change the value of a metric, update your source CSV file. Then, click Edit and upload the edited file. The new or updated metric is displayed in the table. See the Assign Business Metrics to Cost Reports section for the next steps.

Import from Amazon CloudWatch​

To import business metrics from Amazon CloudWatch, you need a specific metric name and AWS account, as described below. Ensure AWS is one of your connected providers

note

If Vantage does not have a Cross-Account IAM Role associated with your AWS account, you need to create one. See the AWS integration documentation for details.

  1. From the Import Business Metrics section, click Import via CloudWatch.
  2. For AWS Account, select the connected AWS account you want to import metrics from.
  3. Select an AWS Region.
  4. Enter a Namespace. A complete list of available namespaces can be found in the AWS documentation for AWS services that publish CloudWatch Metrics. Namespaces start with AWS/ followed by the service name (e.g., AWS/EC2).
  5. Enter a Metric name. Each AWS service has metrics that it sends to CloudWatch. Available metrics can be found in CloudWatch or the AWS documentation.
    tip

    The AWS documentation includes a list of available metrics for services. For example, you can view EC2 instance metrics. An example metric to track in this instance is CPUUtilization. For Amazon RDS, an example metric to track is WriteIOPS or ReadIOPS.

  6. For Dimensions, enter a Name and Value. Dimensions are used to pull specific statistical data for a metric. For example, enter InstanceId with a value of i-1234567890abcdef0. Each CloudWatch metric has a set of dimensions you can select. Click + Add a Dimension to add more than one dimension.
  7. For each import, you must specify the Aggregation function to be used because metrics will be aggregated to the day. Select either Sum, Average, Maximum, or Minimum.
  8. Optionally, enter a dimension name for the Label Dimension field.
  9. Click Import Data.
    Click to view visual example
    The CloudWatch metrics import screen with data added to each field

Metrics are imported for the last six months. The metrics will be automatically synced, daily, along with cost data from other integrations. See the Assign Business Metrics to Cost Reports section for the next steps.

Import from Datadog​

To import business metrics from Datadog, ensure Datadog is one of your connected providers. If you do not have Datadog as one of your connected providers, you will be prompted to connect your Datadog account the first time you try to create a metric.

  1. From the Import Business Metrics section, click Import via Datadog.
  2. For Account, select the connected Datadog account for which you want to import metrics. If this is your first Datadog metric, you may be prompted to reauthorize your Datadog credentials and the required scopes for Vantage (i.e., usage_read, metrics_read, and timeseries_query scopes).
  3. For Metric, enter a metric along with any specific filter criteria for the metric, as shown in the example below: 
    aws.applicationelb.request_count{availabilityzone:us-east-1c, region:us-east-1}
    info

    For more information on the Datadog filtering syntax, see the Datadog documentation.

  4. For Aggregation, select either Sum, Average, Maximum, or Minimum. The metric is aggregated to the day based on your selection.
    Click to view visual example
    The Datadog metrics import screen with data added to each field
  5. Optionally, enter a tag name for the Label Tag field.
  6. Click Import Data.

Metrics will be imported for the last six months. The metrics will be automatically synced, daily, along with cost data from other integrations. See the Assign Business Metrics to Cost Reports section for the next steps.

Import via the Vantage API​

You can import business metrics to Vantage, from other applications, with the Vantage API. Use the /business_metrics endpoint to view, create, update, and delete business metrics.

info

The basic steps for using this endpoint are provided below. See the API documentation for details on parameters, sample requests, and sample responses.

Prerequisites​

Ensure you have a valid Read/Write Vantage API token.

Create a Business Metric​

The following example shows how to create a business metric by sending a POST request to the /business_metrics endpoint.

curl --request POST \
     --url https://api.vantage.sh/v2/business_metrics \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <AUTH_TOKEN>' \
     --header 'content-type: application/json' \
     --data '
{
  "title": "API Requests",
  "cost_report_tokens_with_metadata": [
    {
      "unit_scale": "per_unit",
      "cost_report_token": "rprt_12abc345def678gh"
    }
  ],
  "values": [
    {
      "date": "2024-02-01",
      "amount": 1512,
      "label": "app1"
    },
    {
      "date": "2024-02-01",
      "amount": 1816,
      "label": "app2"
    },
    {
      "date": "2024-02-02",
      "amount": 1236,
      "label": "app1"
    },
    {
      "date": "2024-02-02",
      "amount": 1711,
      "label": "app2"
    }
  ]
}
'
  • title is a string that represents the business metric title (e.g., Requests or CPUUtilization).
  • cost_report_tokens_with_metadata is an array of objects that represents one or more Cost Reports you want the business metric to be added to.
    • cost_report_token is the unique token for the Cost Report.
      tip

      You can access cost_report_tokens via the /cost_reports endpoint.

    • The unit_scale determines the scale of the business metric's values within the Cost Report. It has a default value of per_unit. Other options include per_hundred, per_thousand, per_million, and per_billion.
  • values is an array of objects that comprises the date and amount key/value pairs associated with each business metric data point.
    • date needs to be in YYYY-MM-DD format.
    • amount needs to be a number.
    • label is an optional field. See the section above for details.

The following JSON is returned in a successful 201 response, which includes the unique business metric token. Dates in the response are displayed in ISO 8601 format.

{
  "token": "bsnss_mtrc_ab12345cde67fg8",
  "title": "API Requests",
  "created_by_token": "usr_0a123456789abcde",
  "cost_report_tokens_with_metadata": [
    {
      "cost_report_token": "rprt_12abc345def678gh",
      "unit_scale": "per_unit"
    }
  ],
  "values": [
    { "date": "2024-02-01T00:00:00Z", "amount": "1512.0", "label": "app1", },
    { "date": "2024-02-02T00:00:00Z", "amount": "1816.0", "label": "app2" },
    { "date": "2024-02-03T00:00:00Z", "amount": "1236.0", "label": "app1" },
    { "date": "2024-02-03T00:00:00Z", "amount": "1711.0", "label": "app2" },
  ]
}

Update a Business Metric​

If you need to update or add additional data to a business metric, send a PUT request to the /business_metrics/{business_metric_token} endpoint. In the below example, an additional month of data is added to the business metric that was previously created. The request url includes the unique business metric token, received in the response from the POST call, to update the data.

curl --request PUT \
     --url https://api.vantage.sh/v2/business_metrics/bsnss_mtrc_ab12345cde67fg8 \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <AUTH_TOKEN>' \
     --header 'content-type: application/json' \
     --data '
{
    "values": [
        {"date": "2024-03-01", "amount": 1743},
        {"date": "2024-03-02", "amount": 1356},
        {"date": "2024-03-03", "amount": 1563}
    ]
}
'

The following JSON is returned in a successful 201 response.

{
  "token": "bsnss_mtrc_ab12345cde67fg8",
  "title": "API Requests",
  "created_by_token": "usr_0a123456789abcde",
  "cost_report_tokens_with_metadata": [
    {
      "cost_report_token": "rprt_12abc345def678gh",
      "unit_scale": "per_unit"
    }
  ],
  "values": [
    { "date": "2024-02-01T00:00:00Z", "amount": "1512.0" },
    { "date": "2024-02-02T00:00:00Z", "amount": "1816.0" },
    { "date": "2024-02-03T00:00:00Z", "amount": "1236.0" },
    { "date": "2024-03-01T00:00:00Z", "amount": "1743.0" },
    { "date": "2024-03-02T00:00:00Z", "amount": "1356.0" },
    { "date": "2024-03-03T00:00:00Z", "amount": "1563.0" }
  ]
}

You can also upload data via a CSV. Send a PUT request to the /business_metrics/{business_metric_token}/values.csv endpoint using the business metric’s token. Specify a path to the CSV in the csv parameter.

curl --request PUT \
     --url https://api.vantage.sh/v2/business_metrics/bsnss_mtrc_ab12345cde67fg8/values.csv \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <AUTH_TOKEN>' \
     --header 'content-type: multipart/form-data' \
     --form 'csv=@<PATH_TO_CSV>'

Additional API Actions​

To get all business metrics your API token has access to, send a GET request to the endpoint.

curl --request GET \
     --url https://api.vantage.sh/v2/business_metrics \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <AUTH_TOKEN>'

You can also specify a specific business metric token in the url to get data for only one business metric.

curl --request GET \
     --url https://api.vantage.sh/v2/business_metrics/bsnss_mtrc_ab12345cde67fg8 \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <AUTH_TOKEN>'

If you want to remove values for certain dates, you can pass an empty value as the amount for that date. Send a PUT request to the /business_metrics/{business_metric_token} endpoint using the business metric’s token. In the below example, an existing amount is removed for March 10th.

curl --request PUT \
     --url https://api.vantage.sh/v2/business_metrics/bsnss_mtrc_ab12345cde67fg8 \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <AUTH_TOKEN>' \
     --header 'content-type: application/json' \
     --data '
{
  "values": [
    {
      "date": "2024-03-10T00:00:00Z",
      "amount": null
    }
  ]
}
'

If you want to completely delete a business metric, send a DELETE request to the /business_metrics endpoint, and specify the token for the business metric you want to delete in the url.

curl --request DELETE \
     --url https://api.vantage.sh/v2/business_metrics/bsnss_mtrc_ab12345cde67fg8 \
     --header 'accept: application/json' \
     --header 'authorization: Bearer <AUTH_TOKEN>'
danger

Keep in mind that the DELETE action is permanent, and you will no longer have access to that business metric or see it displayed on corresponding reports.

Assign Business Metrics to Cost Reports​

Assign metric to cost report

Once your import is complete you can assign metrics to one or more Cost Reports. You can also assign as many different business metrics to a Cost Report as you want.

  1. Under Assigned Cost Reports, click Assign a Report.
  2. The Assign a Report popup window is displayed. In the Report dropdown menu, search for and select a Cost Report.
  3. For Unit Scale, select either Per Unit, Per Hundred, Per Thousand, Per Million, or Per Billion. The scale is used to divide the business metric before calculating the cost per unit. Use this scale to create a per-unit cost, such as Cost per Thousand Requests. If you select Per Unit, no division occurs, and the actual metric number will be used within the Cost Report.
  4. For Label Filter, select any labels that were imported with your data.
    • Any selected labels will be aggregated and applied to the Cost Report to calculate the per unit costs. For example, if you select the labels app1 and app2, the per unit cost calculation will be an aggregate of the corresponding values for those labels. If you select only app1, then the per unit cost calculation will only apply to values that correspond with the app1 label.
    • You can also select the unlabeled option, which includes any values that don't have a corresponding label.
  5. Click Save. The metric is displayed on the corresponding Cost Report based on the selected scale and optionally selected labels.

View Per Unit Costs on Cost Reports​

Per Unit Costs displayed on a Cost Report

To inspect your unit costs, navigate to the assigned Cost Report. The average unit cost for the date range selected is displayed at the top of the screen.

tip

To see the cost per unit line, ensure your view is set to daily, weekly, or monthly.

Hover over a data point to see the cost per unit for that day, week, or month. If you add multiple business metrics to the same Cost Report, each business metric is displayed as a separate line, as shown in the example above.

- + \ No newline at end of file diff --git a/rbac/index.html b/rbac/index.html index 46831383..778fd03d 100644 --- a/rbac/index.html +++ b/rbac/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Role-Based Access Control (RBAC)

note

Advanced role-based access controls are available only for Enterprise tier accounts.

Role-based access control (RBAC) facilitates fine-grained management of resource access. Team-based access determines the specific Cost Reporting resources—such as Cost Reports, dashboards, or folders—that a user can view and/or edit.

By default, all users are members of the Everyone team. Owners can control which workspaces/resources the Everyone team can access.

The Owner, Team Owner, Team Editor, and Team Viewer roles are described below.

RoleDescription
OwnerA global account owner who has full access to all items. This role can also manage teams, integrations, and workspaces within an account. Even if the Everyone team is removed from an item, the Owner will still be able to manage that item.
Team OwnerA Team Owner has full control over resources to which that team is granted access. Team Owners also have the ability to change which teams can access their team's resources. They can also manage members of their team.
Team EditorA Team Editor has full control over resources to which that team is granted access; however, they cannot manage the members of the team.
Team ViewerA Team Viewer has read-only access to all resources to which that team is granted access.

Manage Account Access​

Owner is the only role that can invite users to and remove users from Vantage as well as change another user's role.

  1. From the top navigation, click Settings.
  2. From the left navigation, under General Settings, click People.
  3. On the right, click Invite People.
  4. Enter the new user's email, then select their Role and any Teams.
  5. Click Send Invitation.

Manage Team Access​

Create or Delete Teams (Owners Only)​

note

By default, all Vantage users are part of the Everyone team. Users cannot be removed from this team.

Team management window
  1. From the top navigation, click Settings.
  2. On the left navigation, under General Settings, click Teams.
  3. On the Teams view, Owners can manage, add, or delete teams.
    • To add a team, click Create a Team. Add a Name and Description, then click Create Team.
    • To delete a team, hover over the team's name in the team list, then click the trashcan icon.

Map Team to SSO Group (Owners Only)​

Account Owners can map SSO groups to teams within Vantage. The matching teams first need to be created following the steps above. Then, follow the Set Up SSO Group Mapping for Teams instructions for information on how to map teams.

Manage a Team (Team Owners)​

To manage a team, select the team from the Teams list. Four tabs are displayed: General, Members, Access, and API Access Tokens.

Team management tabs and options
  • On the General tab, you can edit the team name and description as well as set a default team dashboard.
    note

    If you set a default dashboard, members who belong to other teams with default dashboards or with a personal default dashboard already configured, may be directed to those dashboards instead.

  • On the Members tab, you can add and remove members from a team as well as change a member's team role. Only Owners will be able to perform these actions. Additionally, Team Owners can perform these actions for their respective teams.
  • On the Access tab, Owners and Team Owners can manage workspace access for the team as well as view resources with granted access.
  • On the API Access Tokens tab, Owners and Team Owners can create API service tokens at the account level that inherit permissions from the team.
  1. From the Members tab, click Add Members.
  2. Select member(s) from the list.
  3. Click Add People.

Manage Resource Access​

You can manage access for individual Cost Reporting resources, including Cost Reports, Cost Report Folders, Dashboards, Saved Filters, Resource Reports, and Segments.

Manage access to a Cost Reporting dashboard
note

You can manage resource-level access from the Cost Reporting navigation list or from directly within a resource. If you are granted access to a report in a workspace outside of your regularly accessed workspace, when you access the link to that report you will have temporary access to the new workspace and can view the items that you were granted access to.

tip

If you want to grant access to a resource (for example, a Dashboard) to only a specific team (for example, the Marketing team), set the Everyone team to Cannot Access, and set the Marketing team to Can Access. See the Team-Only Resource Access permissions table below.

  1. From the top navigation, click Cost Reporting. (For Resource Reports, click Active Resources > Resource Reports.)
  2. Select the resource category from the left navigation (e.g., Cost Reports or Segments).
  3. Hover over any resource in the list, then click the ellipses (...) on the right.
  4. Select Manage Access.
  5. Select a team from the list, and indicate the team's access level to the resource:
    • Can Access: The team will have access to the resource.
    • Cannot Access: The team will not have access to the resource.
    • Reset Access: The team will not have access to the resource unless the team is assigned to the workspace the resource is associated with. For instance, if a specific resource from the Marketing workspace, such as a Saved Filter, was shared with the Management team, which has access only to the Management workspace, resetting the access will result in the Management team no longer having access to the Saved Filter.

Team-Only Resource Access​

In the following table, the Everyone team's access to a resource (for example, a Cost Report) has been revoked. The member's team has been granted access to that specific resource.

Team AccessTeam RoleCreate?Update?*Delete?View?Manage Access?
No AccessOwner
No AccessEditor
No AccessViewer
View AccessOwner
View AccessEditor
View AccessViewer
Edit AccessOwner
Edit AccessEditor
Edit AccessViewer

* Update refers to saving changes

note

If a user is on multiple teams that have conflicting permissions, the higher level of permissions will be granted.

Multiple Teams Resource Scenario
  • A user is on the Marketing team with Team Owner permissions.
  • They are also on the Engineering team with Team Viewer permissions.
  • Both teams are granted access to a Saved Filter.

The user will be granted Owner-level permissions to that resource, in other words, they can view and manage that resource.

Multiple Workspace Access Scenario
  • A user is on the Data Analyst team and the Data Engineering team.
    • The Data Engineering team has Can Edit access to the Engineering workspace.
    • The Data Analyst team has Can View access to the Engineering workspace.
  • The user has edit privileges to resources in the Engineering workspace because of their Can Edit abilities from the Data Engineering team.

Settings Permissions​

Settings permissions are relevant to specific functions in the console, including Authentication, Billing & Plans, Integrations, People, Teams, and Workspaces. Only Owners can manage Settings-related functions.

note

Team Owners can manage their team within the Teams UI — but only the team for which they hold the Team Owner role.

Settings Permissions Examples
  • Scenario 1: You want to create a new provider integration, such as a new Azure connection. An Owner will need to create the connection.
  • Scenario 2: You are a Team Owner for the Engineering team. You can manage the Engineering team in the Teams UI. You will not be able to manage other teams.

Financial Planning Permissions​

Financial planning permissions are relevant to specific screens in the console, including Autopilot, Budgets, Budget Alerts, Business Metrics, Issues, Reserved Instances, Savings Models, and Savings Plans Usage.

Users with the Editor or above role will be able to create resources and manage the above functions.

note

Any user who is assigned to an issue will have update permissions for that issue.

Financial Planning Permissions Examples
  • Scenario 1: You want to create a new Budget Alert. A user with an Editor or above role will need to create and manage the alert. All other users will only be able to view the alert.
  • Scenario 2: Editors and above can create and manage issues. You have a Viewer role and are assigned a new issue. You can now edit and comment on only this new issue.
- + \ No newline at end of file diff --git a/report_notifications/index.html b/report_notifications/index.html index 6e550dfe..043b3c98 100644 --- a/report_notifications/index.html +++ b/report_notifications/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Cost Report Notifications

Cost Report notifications provide either daily, weekly, or monthly reports for one or more Cost Reports. You can receive these notifications from the following methods:

  • Slack: You can send a notification to one or more public or private channels in a Slack workspace.
  • Microsoft Teams: You can send a notification to one or more public or private channels in a Microsoft Teams account.
  • Email: You can send a notification to one or more email addresses.
note

You can create either a Slack integration or a Microsoft Teams integration, but not both.

Before any notification is sent, Vantage ensures it has the most up-to-date representation of your cost data to give you an accurate report.

Cost Report Notifications vs. Cost Anomaly Alerts​

Vantage also has a separate feature called cost anomaly alerts to alert you on excess costs. Cost Report notifications provide a digest of individual reports and are sent on a scheduled basis. Cost anomaly alerts are sent when costs exceed a predetermined alert threshold. They are sent as a summary, once per day, if there are new anomalies for that day. See the Cost Anomaly Alerts documentation for more information.

Set Up Slack Integration​

Vantage users can add Vantage to their team's Slack account in a specific channel. To complete the integration, ensure you have permission to add integrations to your team's Slack account.

  1. Navigate to the Report Notifications page in the console.
  2. Click Setup Slack Integration. Enter your workspace's Slack URL. A Slack page that describes the requested permissions for Vantage is displayed. The Vantage integration has permission to list and join channels as well as post messages to those channels.
    note

    Vantage does not read any message posted within your channels.

  3. Select any channel where you would like to add the integration. The first notification will be sent the next day after the integration set up.
Expand to view example Slack notifications
Example Cost Report notification in Slack message

To add the integration to a private channel, open the channel in Slack, create a new message in the channel, and type /invite @Vantage. See the Set Up Cost Report Notifications section for instructions on how to set up notifications for specific reports.

Set Up Microsoft Teams Integration​

Vantage also integrates with Microsoft Teams. You can adjust cost report notifications to be delivered to a specific public or private channel in Microsoft Teams. To complete the integration, ensure you have permission to add integrations to your team's Microsoft Teams account.

  1. Navigate to the Report Notifications page in the console.
  2. Click Setup Microsoft Teams Integration.
  3. Log in with your Microsoft 365 account and provide Vantage with authorization to access your account. Vantage will ask for the following permissions on your Teams account:
    • Read names and descriptions of Teams
    • Read names and descriptions of channels
    • Send messages to channels
Expand to view example MS Teams notifications
Example Cost Report notification in an MS Teams message

The Vantage app for Microsoft Teams has been verified by Microsoft. Vantage interacts with Microsoft Office 365 to set the approved permissions for the app in your account and makes use of the Microsoft Graph API to get and send info to your Microsoft Teams account. See the Set Up Cost Report Notifications section for instructions on how to set up notifications for specific reports.

Set Up Cost Report Notifications​

Once you have set up either a Slack or Microsoft Teams integration, follow the steps below to create Cost Report notifications.

If you instead want to create an email notification, the email report will contain a list of all of your views and a point-in-time cost for each view. The bottom of the email will include cost recommendations. Cost recommendations are not sent for Slack or Microsoft Teams alerts.

Expand to view example email notification
Example Cost Report notification in an email
  1. Navigate to the Cost Report Notifications screen.
    tip

    You can also click the bell icon in the top right of the console.

  2. Click New Report Notification.
  3. Enter a Title for the report.
  4. If you want to send the report as an email, select the emails for any current Vantage users you want to receive the report.
  5. Depending on which integration you've enabled, a Slack Channels or Microsoft Teams Channels field is displayed. Select the channels you want to send the notification to. You can add as many channels as you want, and they will all receive the notification.
  6. Select a report from the dropdown list, then select a Frequency (e.g., daily, weekly, or monthly).
    note

    Monthly notifications will be sent on the second of the month. Weekly notifications will be sent on Mondays.

  7. For Change, select Dollars or Percentage.
  8. Click Save.

You can edit the notification's settings (e.g., add or remove recipients or change which channels it's sent to) from this screen.

- + \ No newline at end of file diff --git a/saved_filters/index.html b/saved_filters/index.html index a5d104d6..40437872 100644 --- a/saved_filters/index.html +++ b/saved_filters/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Saved Filters

Use saved filters to reuse filter logic across multiple Cost Reports. If you update the filter logic on a saved filter, all Cost Reports that use the saved filter will be automatically updated.

For example, you may have multiple Cost Reports for a specific team, business unit, or environment. If any filter criteria changes, such as tag names or account numbers, you can update the saved filter for all affected reports, without having to individually update each report.

tip

You can also add saved filters to dashboards. See the dashboards documentation for more information.

Create a Saved Filter​

  1. From the top navigation bar, click Cost Reporting.
  2. On the left menu, select Saved Filters. All existing saved filters are displayed.
  3. Click New Filter.
  4. Enter a Filter Name.
  5. If you want to add a filter to a folder, select the Folders tab. Then, select any applicable folders. The saved filter will be added to any existing Cost Reports within that folder, as well as any new Cost Reports you create within that folder. The saved filter will also apply to any sub-folders within that folder. For individual Cost Reports, saved filters can be assigned only from within that Cost Report. (See the next section for details.)
  6. Under Filters, click + Add a Filter. Select your filter criteria.
    info

    For more information about creating filters and filter options, see the Cost Reports filter documentation.

  7. At the top, click Save.

Make a Copy of an Existing Saved Filter​

You can also create a copy of any existing saved filter to use when creating a new saved filter.

At the top of any saved filter, click the Duplicate icon (to the left of Save). This action will replicate the filter logic but not the associated reports.

Add Saved Filter to a Cost Report​

  1. Open any Cost Report.

  2. At the top, click Filters.

  3. Click Saved Filters. A list of existing saved filters is displayed.

  4. Select a saved filter to add it to the Cost Report. You can select multiple saved filters. You can also add additional ad-hoc filter criteria as a separate filter set.

    GIF of filtering RDS costs by category and sorting the table in the console

  5. At the top, click Save.

    note

    When you combine multiple saved filters on Cost Reports that have the same provider (AWS, Azure, etc.) as an ad-hoc filter or another saved filter, "AND" logic is used between each filter set (i.e., costs where Saved Filter 1 AND Saved Filter 2 are true).

Saved Filters within Folders​

If a saved filter is applied to a folder, you will be unable to remove it from the individual Cost Reports within that folder.

  1. To remove the saved filter from a folder, navigate to the Saved Filters page.
  2. Then, click the ellipses (...) next to the saved filter and click Edit.
  3. Remove the folder from the Folders list and click Save.
- + \ No newline at end of file diff --git a/savings_planner/index.html b/savings_planner/index.html index b2577311..86a27dc5 100644 --- a/savings_planner/index.html +++ b/savings_planner/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Savings Planner

Savings Planner is a planning and forecasting tool you can use to view and model AWS Savings Plans and maximize cost savings. Savings Planner provides a view into your on-demand vs. committed spend. You can create models and see the future impact of committing to additional Savings Plans. Vantage automatically detects all existing AWS Saving Plans within your account. Historical cost data and forecasted on-demand usage values for the next 12 months are displayed.

note

At this time, Savings Planner is available only for AWS.

Savings Planner Calculations​

Vantage has ingested over two million different savings rate permutations that are possible across EC2, Lambda, and Fargate. As Vantage processes your Cost and Usage Reports (CUR), it will use your usage data to infer what compute you're running and what your specific savings rates would be for each potential Savings Plan you buy.

This methodology for forecasting savings is as accurate as possible and is more accurate with each additional CUR that's processed. Vantage uses the most recent previous month for forecasting the potential savings rate. As your infrastructure changes each month, Vantage will automatically infer new savings rates.

Savings model predictions are based on raw compute spend and provide a projected savings rate. Descriptions and calculations are provided below.

Raw Compute Spend​

Raw compute spend is defined as any spend on AWS services that is coverable by a Savings Plan. This includes spending on services such as EC2, Lambda, ECS for Kubernetes, SageMaker, and Fargate ECS.

To calculate the raw compute spend, Vantage sums the costs of all coverable services before applying any discounts from Savings Plans. For a given period, this can be expressed as:

raw_compute_spend=∑coverable_services{raw\_compute\_spend}= ∑coverable\_services

Projected Savings Rate​

When calculating financial commitment discounts, Vantage uses the last full month of AWS Cost and Usage Reports to categorize the compute spend based on each AWS SKU. This allows Vantage to calculate the total cost (cost_for_period) for a given period per SKU. Vantage then uses the AWS API to obtain the hourly rate of the instance type (sku_hourly_rate) and the discounted hourly rate (discounted_rate), dimensioned by type, term, and payment for the possible discounts.

The following values are calculated for each EC2, Fargate, and Lambda SKU and all discount dimensions (type, term, payment) based on data available from the AWS API. Total hours and instances per hour are calculated as follows:

total_hours=cost_for_periodsku_hourly_ratetotal\_hours = \frac{cost\_for\_period}{sku\_hourly\_rate}
instances_per_hour=total_hourshours_in_periodinstances\_per\_hour = \frac{total\_hours}{hours\_in\_period}

Vantage then calculates the cost and discounted cost for the instances per hour:

cost=sku_hourly_rate×instances_per_hour{cost} = {sku\_hourly\_rate} \times{instances\_per\_hour}
discounted_cost=discounted_rate×instances_per_hour{discounted\_cost} = {discounted\_rate} \times {instances\_per\_hour}

These individual SKU costs are summed by type, term, and payment to get the total costs:

total_cost=∑cost{total\_cost} = \sum {cost}
total_discounted_cost=∑discounted_cost{total\_discounted\_cost} = \sum {discounted\_cost}

Finally, the projected savings rate is calculated using the total cost and total discounted cost:

projected_savings_rate=total_cost−total_discounted_costtotal_cost{projected\_savings\_rate} = \frac{total\_cost - total\_discounted\_cost}{total\_cost}

Create a Savings Model​

  1. From the top navigation, select Financial Planning.
  2. On the left navigation, select Savings Models. Any savings models you already created will be displayed on this screen.
  3. At the top, click New Model. Two sections are displayed: one that contains a set of values related to the last six months of committed vs. on-demand spend, with future predicted spend. Plans you've already purchased are displayed in the bottom table, with the option to model new plans.
  4. To save a savings model, click Save As New Model.
  5. Enter a name for the model, then click Save.

View Current and Future Spend and Coverage​

The table at the top contains a projected growth rate for the next 12 months based on the last 6 months of spend. A visualization above the table provides a view of covered/uncovered spend for each month.

A full view of the Savings Planner table with on-demand and committed spend

The following data is included in the table:

MetricDescription
Raw Compute SpendThe raw compute cost your account uses before any Savings Plans or Reserved Instances are applied. Raw compute comprises spend for EC2, Lambda, ECS for Kubernetes, SageMaker, and Fargate ECS services.
On-demand SpendThe amount of on-demand costs that your account has incurred.
Savings Plan CommitmentsThe amount of Savings Plan costs that your account has incurred.
Savings Plan SavingsThe amount saved by using the Savings Plan.
Savings Plan CoverageA percentage coverage rate of AWS Savings Plans for your compute cost spend.
Reserved InstancesThe amount of Reserved Instance costs that your account has incurred.
Net Compute SpendThe total compute cost that your account has incurred after on-demand, Savings Plans, and Reserved Instance costs.

To adjust the predictions for future compute spend, click any future date cell within the Raw Compute Spend row and manually edit the prediction value. Consider updating these values based on predicted events over the next few months. The Savings Plan Savings/Coverage and Net Compute Spend rows are automatically updated based on changes to predicted Raw Compute Spend.

GIF that shows a future cell in the Raw Compute Spend row. All other values within the column automatically update.

In the Savings Plan Coverage row, cells are color-coded to provide a visual indication of coverage percentage levels:

  • If the Savings Plan Coverage is greater than 100% or less than 20%, the cell will be red. When coverage is over 100%, this means you are overcommitted.
  • If the Savings Plan Coverage is greater than or equal to 80%, the cell will be green, signaling good coverage.
  • Cells that are greater than or equal to 20% but less than 80% will be gray.

Model Future Savings Plan Purchases​

In the Savings Plans table, you can add potential future Savings Plans. All your existing Savings Plans are listed, along with type, term, payment (e.g., No Upfront), purchase date, and expiration date. Upfront payment, recurring hourly payment, and a projected saving rate are also provided for each plan.

The latest savings rate for the plan is calculated by looking at the last full month of usage. You can click the top of any column to sort the table by that column.

info

For more information about Savings Plans and factors such as term, prepayment, and EC2 vs. Compute plans, see this Vantage blog article.

  1. To add a new Savings Plan, click Add potential savings plan.
  2. Enter an Hourly Commitment in dollars.
  3. For Type, select Compute or EC2.
  4. For Term, select 1 Year or 3 Year.
  5. For Payment, select No Upfront, Partial Upfront (50%), or All Upfront.
  6. Select a Purchase Date.
A savings model option is added to the Savings Planner and an hourly commit is entered. The table at the top is updated automatically to show new predicted spend and savings.

Observe any change in the metrics within the table at the top. You can continue to change the hourly commitment and see how that affects your Savings Plan Coverage over time. Adjust other options, like the term or start date, to see how these changes affect coverage. You can also add additional potential Savings Plans.

To remove a Savings Plan, click the X in the last column of the Savings Plans table.

note

Vantage won't purchase the plans you model within the tool. The Savings Planner is available only for modeling purposes.

- + \ No newline at end of file diff --git a/search/index.html b/search/index.html index d4a40440..d227f67d 100644 --- a/search/index.html +++ b/search/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Search the documentation

- + \ No newline at end of file diff --git a/security/index.html b/security/index.html index 9065e065..bb53df16 100644 --- a/security/index.html +++ b/security/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Security

As an infrastructure tool that requires access to your cloud provider, we understand there may be questions, concerns, and necessary clarification around our infrastructure, processes, and procedures. We, as developers at Vantage, are also customers of Vantage, which more closely aligns our security concerns with those of our customers.

Read-Only Billing Access​

Vantage uses read-only service accounts, service roles, API keys, and other read-only means to access billing data across all the integrations we use. This means we don't store sensitive information, like account access keys and access key secrets, to use Vantage. Should you have any other questions, please feel free to email us at security@vantage.sh.

Cross-Account IAM Roles on AWS​

Vantage uses a Cross-Account IAM Role to sync information about your infrastructure resources. This method is the AWS-recommended approach. When you grant Vantage access to your account by running the provided CloudFormation stack, the stack creates a cross-account role with in-line policies selected by Vantage. These policies are a trimmed-down version of the policies in the AWS-managed ReadOnlyAccess policy, but we've removed actions that would otherwise allow us to access sensitive information in databases, buckets, and certain services. Our CloudFormation template is open source and hosted publicly for transparency.

Customizing Cross-Account Role Permissions​

Vantage requests various in-line read-only permissions when creating the cross-account role on your behalf; however, we understand this can be too broad of a permission set for certain use cases. As a result, we do allow you to create Cross-Account IAM roles with whatever permissions you're comfortable with. However, keep in mind that narrowing the scope of the role's permissions will limit certain functionality in Vantage.

If you email support@vantage.sh in advance, we can facilitate provisioning your account with a custom role. Please note that we will provide you with some custom attributes to associate with your Cross-Account IAM Role to prevent the "confused deputy" problem. As a result, you will need to contact Vantage support before you create the role.

Data Revocation​

In the account Settings section, you can revoke the Cross-Account IAM Role at any time. Automatically and nearly instantly, Vantage will delete all data associated with that Cross-Account IAM Role. Note that the deletion doesn't remove the set of custom Vantage views you've created; however, these views will be empty, as there are no longer any resources.

In the account Settings section, you also can delete your account. Once you delete your account, all data is deleted as well.

Data Sharing​

We do not share any data externally. We do not sell or share any user data with any third parties.

Frequently Asked Questions​

Does Vantage periodically perform penetration tests?

Yes. Vantage has outsourced penetration tests to a third party that regularly performs these tests.

Does Vantage hold any security certifications, such as SOC 2 or ISO 27001?

Yes. Vantage is SOC 2 Type 2 certified. To request a copy of our report, visit the Vantage Security Page. We believe that we already roughly adhere to the standards outlined in ISO 27001.

In terms of application security, how does Vantage deal with security reports received from security researchers? In other words, does Vantage have a bug bounty program or a straightforward process to report security issues?

Vantage receives reports via security@vantage.sh. We review every single report that we receive. We do not have a formal bug bounty program, but we do have a process as well as a set of policies and standards we follow to process security requests.

Does Vantage support 2FA, SSO, or any defensive options?

Yes. We support SAML SSO, and 2FA is on the roadmap.

How is customers’ data protected, and who has access to Vantage data?

All data is encrypted in transit and at rest. Only a subset of senior employees has access to data on the Vantage side. We regularly review and revise the list of individuals on the Vantage team with access to customer data.

Do you have a list of third parties Vantage uses that explains what each third party is allowed to access and its purpose?

We use a subset of third parties, largely for analytics, support, and payment processing. There is no PII sent to third parties, and no cost data is shared with third parties. A list of third parties is provided below:

  • Mixpanel: Customer analytics
  • Segment: Customer analytics
  • Customer.io: Customer communications
  • HubSpot: Sales management
  • Intercom: Support management
  • Stripe: Payment processing
Do you have a security contact person in case of breaches?

A team responds to messages at security@vantage.sh. Upon request, a security employee can be temporarily assigned to your account as well.

Do you log access activities of Vantage’s employees who have access to the data?

Yes.

Does Vantage store any information regarding cloud infrastructure in the database?

Yes. We store basic metadata on cloud infrastructure to be able to show corresponding costs for associated resources. We cannot access any of the underlying resources.

- + \ No newline at end of file diff --git a/segments/index.html b/segments/index.html index 0e36e961..b7dfa5b9 100644 --- a/segments/index.html +++ b/segments/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Segments

note

To enable segments in your account, contact Vantage Support at support@vantage.sh.

A segment is a set of filters that represents a portion of costs for your organization (e.g., costs allocated to a business unit or team). With segments, you can perform cost allocation and enforce cost governance for your organization. You can create nested hierarchies of costs that can map to teams, departments, apps, or services within your organization. Segments ensure that costs are allocated only once and not duplicated in cases of showback/chargeback scenarios.

The below diagram shows an example of a segment hierarchy. All child and grandchild segment costs roll up to the top-level organization segment. Any costs not assigned to a segment are considered unallocated costs. By analyzing your segments, you can identify and burn down these unallocated costs to improve financial accountability and resource management.

Tree diagram of segments with an Organization at the top, three child business unit segments, and two grandchild segments per child segment that represent teams. Each child and grandchild segment has an arrow that points up to the organization segment at the top.
tip

To get started with cost allocation segments, you can also view a video demo on Vantage University 🎓.

Segments Use Cases​

You can leverage segments for many use cases, including the below examples.

  • Map costs to business units. You can use nested hierarchies for cost allocation. For example, you can see costs grouped by an “Infrastructure Engineering” team, then drill down into all the various sub-teams, like "Infrastructure Engineering Team 1” and “Infrastructure Engineering Team 2." The costs for Team 1 and Team 2 together comprise the total cost allocation line item for Infrastructure Engineering.
  • Maintain tag governance. You can create a segment for a particular tag key you want to enforce across your organization. Whenever there are costs in the “Unallocated” portion of the report, you can go and identify resources to assign to the proper team or service. Unallocated costs are costs that are captured by a segment's filters but are not allocated to any child segments. For example, if you have two segments defined for OPEX and R&D, any costs that do not match the logic associated with either of these filters will fall into the unallocated segment. The unallocated segment report is automatically displayed at the root or parent segment level.

Create a Segment​

Follow the steps below to create a segment.

  1. From the top navigation, click Cost Reporting.
  2. On the left navigation, select Segments. If you have segments present in your account, a full list of top-level segments is displayed in the view on the right, sorted alphabetically.
  3. To create a new segment, click New Segment.
  4. Set the following parameters for the new segment:
    • For Name, enter a unique string (e.g., OPEX). This field is required.
    • For Description, optionally enter a text description for the segment.
    • For options, you can select whether you want to include or exclude credits, refunds, discounts, taxes, and amortization. You can also optionally track unallocated costs.
      note

      These options are displayed only for the root or parent segment, and the selections you make will apply to child segments. Track unallocated applies only to the parent segment.

    • For Priority, enter a numeric value (e.g., 100). Costs are allocated in order of priority, with 0 as the highest priority. This field is required if filters are specified (as described in the next step). If you do not specify filters, this field is optional.
      note

      Once a cost is allocated to a segment, it will not appear in a segment with a higher priority; however, you likely will not need to worry about priority unless your organization has deep scrutiny on cost allocation collision.

  5. Filters allocate costs to the segment and are optional. To create a filter, click + Add a Filter and configure the following values:
    • Select a Provider.
    • Click New Rule to add additional logic, such as Region or Category filters. Segment filters are like filters in Cost Reports. See Filter Cost Reports for a more detailed explanation of filters. Note that you cannot use saved filters from Cost Reports in segments.
      Click to view example image

      This example shows a root- or parent-level segment called "Management." Child segment parameters will be the same—except for the Track unallocated option, which is not displayed for child segments.

      The segment creation screen with all cost filters displayed for the segment.
  6. At the bottom, click Save. You will see a message indicating "A Segment Report will appear here when the segment is finished refreshing" while the report for the segment is generated. Depending on the filter's complexity, it can take some time for the segment report to generate (up to 24 hours).

Edit a Segment​

note

If you make additional changes to a filter or segment metadata, like title, it can take up to 24 hours after you regenerate the segment to see those changes reflected in the console.

You can edit a segment's title, description, priority, and filters within the console. On parent-level segments, you can also edit the settings, such as discounts and taxes.

  1. To edit these criteria, click the pencil icon next to the segment name.
    The Segments screen with a list of segments. A box is displayed around the pencil icon where you can edit the segment's settings.
  2. Update and save the new criteria.
  3. On the main Segments screen, the segment's Status column indicates if a segment needs to be regenerated. Click Refresh Segment.
    The Segments screen is displayed with a list of segments. The Status of the first segment is displayed with the Refresh Segment icon.
  4. The Status will be displayed as Refreshing while the segment is being updated. This process may take up to 24 hours.
    The Segments screen is displayed with a list of segments. The Status of the first segment is displayed with the Refreshing... icon.

View and Create Child Segments​

You can create child segments and nest segments within one another. Costs associated with nested segments/filters will be rolled up to any parent segments. To add a child segment to a parent segment, navigate to the parent segment, and click New Segment Dimension. The image below shows an example of a group of nested segments.

A list of child segments is displayed. The status indicates they are in sync. It is a list of nested segments called OPEX and R&D. The Unallocated segment is also listed.
  • In the above example, Vantage is the top-level segment (as displayed in the breadcrumbs at the top of the screen).
  • The Vantage segment report is displayed at the bottom of the list.
  • In this example, we selected the option to show Unallocated costs when creating this parent segment. The corresponding Unallocated segment report is displayed in the list.
  • The Vantage parent segment has two child segments: OPEX and R&D.

Select a child segment. You will see additional third-level child segments as well as the associated child segment report. In the below image, the R&D child segment report is displayed. R&D contains no additional child segments; however, you can add them if you want. Observe the breadcrumbs at the top, which also indicate R&D is a child segment of Vantage.

Create Cost Filters for segment

View Segment Reports​

Select a segment report to view the associated costs. On the report, costs are displayed for all associated child segments.

  • The report is filtered to Group By: Segment to show costs broken out by the child segments within that segment. In the below example, costs are grouped by OPEX and R&D within the Vantage parent segment. The parent segment is also tracking unallocated costs.
  • Change the filter to view the data by another grouping, such as Account.
  • From the resource list at the bottom, click the icons next to each resource to isolate costs displayed within the chart.
  • From the top right of the chart, you can change the date range and date bin (e.g., daily, weekly, monthly).
  • Click Settings to view the currently enabled settings, like discounts and taxes. From the Settings menu, click the Manage settings link to update the segment's settings. Settings are updated at the parent-level segment. In this example, settings are updated for the Vantage segment and also apply to the OPEX and R&D child segments.
GIF of viewing and manipulating a segment

note

If you would like to transition existing Cost Report filters to segments, you must manually re-create them. For assistance, contact Support at support@vantage.sh.

Segments in Overview​

A segment widget is displayed for each top-level segment on the Overview screen. This segments widget shows a table of second-level segments and a comparison of costs for this month vs. last. You can select any of these segments to view the corresponding Cost Report.

- + \ No newline at end of file diff --git a/snowflake_cost_by_query/index.html b/snowflake_cost_by_query/index.html index 6d87af03..041d96f5 100644 --- a/snowflake_cost_by_query/index.html +++ b/snowflake_cost_by_query/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Snowflake Costs per Query

Vantage calculates a weighted cost per query by breaking down the use of Snowflake compute credits. This allows users to easily identify the most expensive queries.

Snowflake cost per query

How It Works​

Snowflake Compute is billed only when a query is running, rounded up to the hour; however, if multiple queries are running simultaneously, the cost is still only reported for that hour. This shared credit pool makes it difficult to understand which individual queries are contributing the most to costs.

Each day, Vantage ingests the compute credits used, and their equivalent cost, and assigns a weighted cost to each query based on the total duration for which the query ran. For example, if you had 3 queries that ran for 1, 2, and 3 minutes respectively, and a total bill of $500, the query that ran for 3 minutes would be assigned a cost of $250 as it accounted for half of the overall query time.

Grouping Queries​

Vantage groups queries based on the source and structure of a query, so users can easily identify it. To determine the source, Vantage looks at the warehouse in which the query was run as well as the user who ran the query. To determine the structure of a query, Vantage will strip all query values and the order of columns and generate a normalized, unique fingerprint for the query.

Viewing the Costs​

Query costs are available in two views: on Cost Reports and in Active Resources.

Query Costs in Cost Reports​

To view query costs on a Cost Report:

  1. In the console, navigate to Cost Reports.
  2. Create a new report and add a provider filter for Snowflake.
  3. Click the Cost by Resource icon next to the Snowflake Data Cloud line item and see a paginated list of each query, as well as a day-by-day breakdown of that query's costs.

Query Costs in Active Resources View​

To view query costs in the Active Resources view:

  1. Navigate to the Active Resources page in the console.
  2. Select Snowflake Query and see a list of active queries, as well as their associated costs. Queries are considered active if they have incurred costs in the past 30 days and are in the top 1,000 queries by cost for that account.

Security​

Vantage ensures that any sensitive data contained in queries is never stored in Vantage systems. When the QUERY_HISTORY view is queried from Snowflake, that data is immediately processed to strip all values from queries before they are stored.

- + \ No newline at end of file diff --git a/sso/index.html b/sso/index.html index 5b8dcc86..799e553a 100644 --- a/sso/index.html +++ b/sso/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Single Sign-On (SSO)

Vantage supports single sign-on (SSO) via self-service single sign-on as well as several other supported IdPs. You can use self-service SSO to connect your SAML (Security Assertion Markup Language) Identity Provider (IdP) to your Vantage account. With self-service SSO, you can use your existing credentials to authenticate and access your Vantage account. SSO streamlines the login process since users don't need to create a new account or remember another set of login credentials for Vantage.

Vantage uses Just-in-Time (JIT) provisioning for user provisioning. As long as a user is granted access to your IdP, the user will be provisioned an account in Vantage when they first log in.

Self-Service SSO via SAML​

note

Currently, Vantage supports self-service connection for SAML. If you'd like to connect one of the other supported IdPs (e.g., Google Workspace or Windows Active Directory), view the instructions below. If you do not see your IdP listed, contact Vantage Support.

What Is SAML SSO?​

SAML is an XML-based open standard for exchanging authentication and authorization data between parties. It enables secure and standardized communication between identity providers, service providers, and users. SAML allows for seamless and secure access to web applications and services.

Before you can connect your IdP to Vantage, you will need the following:

  • A valid account with a SAML IdP
  • Owner role access to Vantage
  • Your IdP's signing certificate and sign-on URL

Connect Your SAML IdP​

  1. From the Vantage console, navigate to the Authentication page.
  2. Click New Connection.
  3. Select the SAML connection type.
    Expand to view example image
    Create SSO integration in Vantage console
  4. Copy the Single Sign-On URL and Audience URL that are provided on screen. You will need both of these URLs for your IdP's configuration.
    Expand to view example image
    Configuration for SAML SSO integration in Vantage console
  5. To add a logo to your connection's thumbnail, use the provided Vantage Logo.
  6. Once you create the Vantage application within your IdP, copy the following information:
    • Copy the SAML Sign-On URL provided by your IdP, then paste it into the SAML 2.0 Endpoint field of the Vantage SAML page.
    • Copy the Signing Certificate provided by your IdP, then paste it into the Public Certificate field of the Vantage SAML page.
  7. Ensure you've entered the correct credentials, then click Create Connection. You'll be redirected back to the Authentication page, where you will be able to see your connection.
  8. To enable the connection, switch the Active toggle to on. You will remain logged in to Vantage, but the next time you attempt to log in, you will be redirected to your IdP's sign-on page.
  9. Optional: If you would like to set up SSO group mappings based on your existing Vantage teams, see the SSO Group Mappings instructions below.
Important

For security reasons, Vantage does not recommend IdP-initiated sessions. For Okta, our recommended best practice is to create a tile called Vantage with a link to https://console.vantage.sh/login. For more information, see the Create a Bookmark App instructions, on the Okta documentation site.

If you want to use an IdP-initiated session configuration, please contact Vantage Support.

Example: Create a SAML SSO Connection with Okta​

info

For detailed instructions, see the Okta support documentation.

  1. Create an app integration on Okta.
  2. For Sign-in method, select SAML 2.0. Click Next.
    Expand to view example image
    Create a new Okta app integration
  3. For App Name, enter Vantage.
  4. For App Logo, upload the Vantage Logo, then click Next.
    Expand to view example image
    Okta app settings
  5. Enter the requested Single sign on URL (for example, https://auth.vantage.sh/login/callback?connection=company-com) and Audience URI (SP Entity ID) (for example, urn:auth0:vantage-production:company-com), provided on the Vantage Authentication setup page.
    Expand to view example image
    Okta SAML settings
  6. Set the Application username to Email.
  7. Once the app integration is set up, copy the Okta-provided Identity Provider Single Sign On URL and X.509 Certificate back into Vantage.
  8. To enable the connection, switch the Active toggle to on. You will remain logged in to Vantage, but the next time you attempt to log in, you will be redirected to the Okta sign-on page.

Test Your SSO Configuration​

The recommended steps for testing your SSO configuration are as follows:

  1. Once your connection is enabled, do not close or log out of your current Vantage application session.
  2. Open a private browser or incognito window, and visit https://console.vantage.sh.
  3. Enter your email address. If your SSO connection is configured correctly, you will be redirected to your IdP.
  4. Enter your login credentials. If you can complete the login, your configuration is correct.

If you experience any issues with logging in after you've enabled your connection, contact Vantage Support.

Disconnect Your IdP​

If you ever need to disconnect your IdP from Vantage:

  1. Navigate to the Authentication page.
  2. To disable your connection, switch the Active toggle off. To permanently remove your IdP, click the Delete button.

After disabling/removing the connection, you will be able to log in to the app with your original Vantage login credentials.

Set Up Other IdPs​

note

If you do not see your IdP listed, please contact Vantage Support.

Authenticate with Azure AD​

info

The following instructions are based on the Microsoft documentation.

Step 1: Register an Application with Azure AD​

Expand to view example image
Configuration for Azure app registration

Source: Microsoft

  • From the Azure portal, navigate to App registrations, then click New registration.
  • Enter a name for your app (e.g., Vantage).
  • Set the Supported account types option to the appropriate setting for your organization.
  • For Redirect URI, select Web and enter https://auth.vantage.sh/login/callback.
  • Click Register.
  • Once the app registration is complete, copy the Application (client) ID displayed on the app's Overview page to send to Vantage.

Step 2: Generate a Client Secret​

Expand to view example image
Configuration for Azure client secret

Source: Microsoft

  • On the left navigation, select Certificates & secrets.
  • Under the Client secrets tab, click New client secret.
  • Enter a description and select an expiration for the secret.
    caution

    If this secret expires, you will need to supply Vantage with a new secret before the expiration date.

  • Click Add.
  • Copy the secret's Value.

Step 3: Add API Permissions​

Expand to view example image
Configuration for Azure app API permissions

Source: Microsoft

  • On the left navigation, select API permissions.
  • Select Add a permission.
  • Under the Microsoft APIs tab, find and select the appropriate permissions required by Vantage (e.g., Directory.Read.All, User.Read).
  • At the bottom, click Add permissions.
Expand to view example image
Configuration for Azure app admin consent

Source: Microsoft

  • Still under API permissions, you may see a section for Grant admin consent for {your domain}.
  • Click Grant admin consent, and follow the prompts.

Step 5: Contact Vantage Support​

Contact Vantage Support for information on how to send the following items to finish the connection with the Vantage app:

  • Application (client) ID
  • Client secret
  • Azure AD Domain
note

You can obtain your Azure AD Domain name on the Overview page of Azure Active Directory.

After your connection is complete, if you would like to set up SSO group mappings based on your existing Vantage teams, see the SSO Group Mappings instructions below.

Authenticate with Google Workspace​

info

The following instructions are based on the Google documentation.

Step 1: Register an OAuth Application with Google​

  • From the Google API Console, select an existing project or click CREATE PROJECT.
  • From the left navigation menu, click Credentials.
  • At the top, click CREATE CREDENTIALS > OAuth client ID.
    note

    If this is your first time working with this Google project, you will have to configure your consent screen. Follow the Google documentation linked above.

  • For Application type, select Web application.
  • Enter a Name for your application (e.g., Vantage).
  • For Authorized JavaScript origins, click ADD URI and enter https://auth.vantage.sh.
  • For Authorized redirect URIs, click ADD URI and enter https://auth.vantage.sh/login/callback.
  • Click CREATE.
Click to view example image
Google Workspace app setup

Step 2: Obtain Application Credentials and Contact Vantage Support​

  • Copy your app's CLIENT ID and CLIENT SECRET.
  • Contact Vantage Support for information on how to send these credentials to finish connecting with the Vantage app.

After your connection is complete, if you would like to set up SSO group mappings based on your existing Vantage teams, see the SSO Group Mappings instructions below.

Authenticate with Rippling​

Vantage is available in the Rippling App Shop, where you can find instructions for connecting your Vantage account to Rippling.

Set Up SSO Group Mapping for Teams​

With the SSO Team Assignment feature, you can automatically assign users to Vantage teams that match the name of a corresponding SSO group.

Prerequisites​

To use the SSO Team Assignment feature, you will need to have teams already set up in Vantage. See the Role-Based Access Control: Create Teams documentation for information on how to create teams in Vantage.

Enable SSO Team Assignment​

  1. From the top menu of the Vantage console, click Settings.
  2. On the left navigation menu, select Authentication. You will see your SSO connection listed.
  3. In the SSO Team Assignment section of the connection, click the toggle button to enable the feature.

Vantage will match SSO groups to Vantage teams based on the case-sensitive name of the SSO group. If a team name in Vantage matches an SSO group name, the user will be placed into that team in Vantage. Users will be mapped into the appropriate teams during their next login.

Important

After the SSO Team Assignment setting is enabled, users will be removed from Vantage teams that are not present in the SSO groups. If you want to modify this behavior, contact support@vantage.sh. The Everyone team will remain unchanged.

Create Custom Mappings​

If your team names in Vantage do not match your identity provider, or you want multiple groups to be added to the same team, you can create custom mappings.

  1. To create custom mappings, click the Show dropdown menu next to Custom Mappings.
  2. In the SSO Group Name column, enter the group names from your SSO provider. The SSO Group Name you enter should match the corresponding name in your identity provider. Note that the mapping is case-sensitive.
  3. From the Vantage Team dropdown, select the corresponding Vantage team.
  4. Click Add to add additional mappings.
    SSO team assignment toggle in the console
  5. When you are finished, click Save.
note

A user’s teams are updated on every login. Vantage will also automatically remove users from teams that are no longer present in the SSO groups list.

Group Mapping in Okta — Enabling groups Attribute​

Vantage uses the groups field in the SSO payload for matching SSO groups to Vantage teams. As long as your identity provider can pass a groups attribute in the payload, you can use SSO group mapping. For some providers, like Okta, you may need to enable group mapping.

To enable group mapping in Okta:

  1. Navigate to the Vantage SAML application in Okta.
  2. Edit your SAML Settings.
  3. For Name, enter groups.
  4. If you would like to pass through all groups, set the Filter to Matches regex with a value of .*.
    Click to view example image
    Okta group attribute settings
info

If you need help with your specific identity provider, contact support@vantage.sh.

- + \ No newline at end of file diff --git a/team_accountability/index.html b/team_accountability/index.html index 806a4396..f861b505 100644 --- a/team_accountability/index.html +++ b/team_accountability/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Team Accountability

Managing the cost of cloud services can be challenging—especially when multiple teams are involved. However, it is essential to ensure that each team is accountable for their cloud costs. By following these steps, you can hold your team accountable for cloud cost management using Vantage.

Optional Prerequisites​

  • Apply cost allocation tags or labels to groups of resources for different owners, teams, customers, products, apps, or services.
  • Utilize account, resource group, project, or subscription hierarchy to create divisions in your resources.

Step 1: Create a Cost Report Folder for a Specific Team​

The first step in team accountability for cloud cost management is to create a Cost Report folder for a specific team. This will help you to group resources using appropriate tags and labels that can be used to identify and group those resources into the same report.

Step 2: Create Cost Reports on Various Dimensions​

Within the Cost Report folder, create Cost Reports based on various dimensions for the resources that can be attributed to the relevant team. You can use filter sets that can filter on provider, tag, service, resource, account, and category/subcategory.

Step 3: Use Cost Report Notifications​

Once the report is created, use Cost Report notifications to send daily, weekly, or monthly roll-up reports to a set email address or Slack channel for the appropriate team. You can also set up Cost Anomaly alerts on the same report to go to a set email or channel for that team, which will identify unknown or unexpected increases in daily spending for a service.

Step 4: Set a Team Budget Assigned to a Cost Report​

Use Budgets to set a team budget assigned to a Cost Report for that team. This will help to ensure that the team is aware of their budget and will be held accountable for their cloud costs.

Step 5: Monitor and Optimize​

As you continue to monitor and optimize your cloud costs, you can adjust your team’s budget and reports as needed. This will help to ensure that each team is accountable for their cloud costs and is actively working to reduce unnecessary expenses.

Managing cloud costs can be challenging, but by following these steps, you can hold your team accountable for their cloud cost management and ensure that your cloud spending is optimized and efficient.

Additional User Workflows​

- + \ No newline at end of file diff --git a/terraform/index.html b/terraform/index.html index 3094ae52..9021eee8 100644 --- a/terraform/index.html +++ b/terraform/index.html @@ -10,7 +10,7 @@ - + @@ -21,7 +21,7 @@

Terraform Provider

Vantage is an official HashiCorp partner and offers a Terraform module for getting up and running with Vantage using Infrastructure as Code (IaC). Vantage also offers a Terraform provider with several resources.

  • Vantage Terraform Integrations module for AWS: The Vantage Terraform Integrations module is available for registered users, across all Vantage tiers, to create the primitives needed to broker a connection with AWS. With the module, you can create a Cross-Account IAM Role as well as a Cost and Usage Report (CUR).
  • Vantage Terraform provider: The Terraform provider comprises several Vantage resources you can create, such as Cost Reports, dashboards, etc. Use the provider to automate and manage Vantage from within your existing Terraform codebase. Organizations with IaC practices can set up, create, and sync their cost reporting structure with Vantage.

Vantage Terraform Integrations Module for AWS​

Use the Vantage Integrations module to link your AWS and Vantage accounts. Organizations can leverage the module to integrate thousands of AWS accounts with Vantage. To get set up with this module, see the additional documentation on the Terraform Registry.

note

For root AWS accounts, you will need to provision a CUR bucket using the cur_bucket_name variable. For sub-accounts, you will need to link access, but you won't need to configure the CUR bucket.

The below example shows how to add the management (root) AWS account integration where CUR and an S3 bucket are provisioned:

provider "aws" {
  region = "us-east-1"
  assume_role {
    role_arn = "arn:aws:iam::123456789012:role/admin-role"
  }
}

module "vantage-integration" {
  source  = "vantage-sh/vantage-integration/aws"

  # Bucket names must be globally unique. It is provisioned with private acl's
  # and only accessed by Vantage via the provisioned cross account role.
  cur_bucket_name = "my-company-cur-vantage"
}

The below example shows how to add a member account without a CUR integration. As a result, an IAM Role is created, which Vantage can assume to ingest the cost and resource metadata that are displayed within the Vantage console. See the Terraform documentation for more details.

provider "aws" {
  region = "us-east-1"
  assume_role {
    role_arn = "arn:aws:iam::123456789012:role/admin-:ew
    role"
  }
}

module "vantage-integration" {
  source  = "vantage-sh/vantage-integration/aws"
}

Vantage Resources and Data Sources​

Using the Terraform provider, you can automate Vantage resources, such as Cost Reports, via the Vantage Write API—or the backbone of the provider.

With the Terraform provider, you can create many resources, like Cost Reports, report notifications, folders, dashboards, etc. The provider also includes many data sources you can use to pull data from the Vantage console. See the documentation for details.

By using these Terraform resources, engineering teams automate cost reporting in Vantage. Below are some example use cases.

  • Build Cost Reports for hundreds of teams stored in another source of truth (e.g., database or GitHub)
  • Update filters as resource names or tags change
  • Add new reports to team dashboards when new services are deployed
  • Create teams and access grants based on teams within an identity provider (IdP)
Important

The ability to create, edit, and destroy resources is keyed to the permissions of the user associated with the API token. For Enterprise customers, role-based access controls also affect these actions. Review the documentation on RBAC for further information.

Terraform Import​

terraform import is a command used in Terraform that allows you to bring existing infrastructure resources into Terraform management. This command helps integrate resources that were created outside of Terraform—such as those provisioned directly in the Vantage console or API—into Terraform's state file. For example, if you initially set up your cost reporting resources through the Vantage console, you can use this command to import these resources into your Terraform state, which allows you to maintain a single source of truth for your infrastructure.

To use terraform import, run the following command:

terraform import vantage_cost_report.demo_report rprt_1abc23456c7c8a90

In the above example, a Cost Report that was created within the Vantage console is brought into the Terraform state.

  • vantage_cost_report.demo_report: The type of infrastructure component managed by Terraform (e.g., vantage_cost_report); followed by a user-defined identifier assigned to a resource in your Terraform configuration.
  • rprt_1abc23456c7c8a90: Example of a Cost Report token. This can be found in the URL for a report within the console or via the API.

See the example below for a walkthrough of how to use this command.

Terraform Examples​

Before you begin, ensure you have a valid Write API token.

Create a Cost Report​

The following example describes how to create a Cost Report for AWS using Terraform.

  1. First, declare the Vantage provider.

    terraform {
      required_providers {
        vantage = {
          source = "vantage-sh/vantage"
        }
      }
    }

    provider "vantage" {
      api_token = var.api_token
    }
    tip

    You can optionally save your API token as an environment variable and remove the provider "vantage"{...} block. Export your token with: export VANTAGE_API_TOKEN=<YOUR_API_TOKEN>.

  2. Create the vantage_folder resource, with "AWS Costs" as the title.

    resource "vantage_folder" "aws" {
    title = "AWS Costs"
    }

  3. Create the vantage_cost_report resource using the token output from the vantage_folder resource. The Cost Report will be stored in the newly created AWS folder. The Cost Report's title is "AWS Costs." In addition, the vantage_saved_filter resource includes a filter parameter that uses Vantage Query Language (VQL), a SQL-like language for querying cloud cost and usage data. Here, the filter is set to show only AWS costs. Set the groupings parameter to have the report grouped by region and service.

    tip

    Valid groupings include: account_id, billing_account_id, charge_type, cost_category, cost_subcategory, provider, region, resource_id, service, tag:<tag_value>. Enter multiple groupings as comma-separated values: groupings=provider,service,region.

    resource "vantage_cost_report" "aws" {
      folder_token = vantage_folder.aws.token
      filter       = "costs.provider = 'aws'"
      title        = "AWS Costs"
      groupings    = "region,service"
    }

Using Multiple Vantage Terraform Resources​

In the following example, we will create a filter, report, and folder to track database costs. This example assumes you've already declared the appropriate providers.

  1. First, create an RDS instance using the aws_db_instance resource from the AWS provider. Then, create a saved filter using the output of the arn from the RDS instance as part of the filter criteria.

    resource "aws_db_instance" "rds" {
      allocated_storage    = 10
      db_name              = "primary-database"
      engine               = "mysql"
      instance_class       = "db.t3.micro"
      username             = "admin"
      password             = "password"
    }

    resource "vantage_saved_filter" "rds" {
      title  = "rds-costs"
      filter = "costs.provider='aws' AND costs.resource_id = '${aws_db_instance.rds.arn}' AND costs.service = 'Amazon Relational Database Service'"
    }

  2. Then, create a folder to keep your RDS Cost Reports organized.

    resource "vantage_folder" "rds" {
      title = "RDS Costs"
    }

  3. Finally, use the tokens that are output from the saved filter and folder as input to create a new Cost Report.

    resource "vantage_cost_report" "rds_costs" {
      folder_token        = vantage_folder.rds.token
      saved_filter_tokens = [vantage_saved_filter.rds.token]
      title               = "RDS Costs"
    }

In this manner, initial setup, deployments, and infrastructure changes are synced to Vantage. Further examples can be found in the terraform-provider-vantage GitHub repository.

Use terraform import to Manage External Resources​

In the following example, you created a Cost Report in the Vantage console. You want to update the filter on this Cost Report to pull data for different RDS instances, and you want to do this automatically using Terraform. To update data on a resource made outside Terraform, you need to use the terraform import command.

  1. First, obtain the token for this Cost Report. You can access this token using one of the following methods:

    • If you are viewing the report in the Vantage console, copy the report's token from the end of the URL (e.g., in https://console.vantage.sh/reports/rprt_123a47b5ba1234e1, copy rprt_123a47b5ba1234e1).
    • You can access a list of your reports from the /cost_reports Vantage API endpoint. The token is one of the values returned in the response.
    • Use the vantage_cost_reports Terraform data source. You can call the data source and create an output value to access a list of Cost Reports.

  2. Ensure the vantage_cost_report Terraform resource that you want to update is defined in the configuration. Below it is defined with the current parameters.

    resource "vantage_cost_report" "demo_report" {
      title               = "Terraform Demo Report"
      filter              = "costs.provider = 'aws' AND costs.service = 'Amazon Relational Database Service' AND costs.resource_id IN ('arn:aws:rds:us-east-1:123456789:db:primary-01', 'arn:aws:rds:us-east-1:123456789:db:primary-02')"
      workspace_token     = "wrkspc_12c3254c789e0123"
    }

  3. At this point, Terraform is aware of the resource, but it doesn't manage it yet because the Cost Report was created outside of Terraform, in the Vantage console. To bring the external resource under Terraform's control, you need to import it using the terraform import command. Replace the placeholder <token> with the token you just obtained for the Cost Report.

    terraform import vantage_cost_report.demo_report <token>

    For example, if your Cost Report token is rprt_123a47b5ba1234e1, run the following command:

    terraform import vantage_cost_report.demo_report rprt_123a47b5ba1234e1

  4. After importing the resource, you can modify its attributes in your Terraform configuration. In this example, you can adjust the ARNs in the filter parameter to reflect two different RDS instances.

    resource "vantage_cost_report" "demo_report" {
     title = "Terraform Demo Report"
     filter = "costs.provider = 'aws' AND costs.service = 'Amazon Relational Database Service' AND costs.resource_id IN ('arn:aws:rds:us-east-1:123456789:db:primary-03', 'arn:aws:rds:us-east-1:123456789:db:primary-04')"
     workspace_token = "wrkspc_12c3254c789e0123"
    }

  5. Finally, apply the changes to your configuration:

    terraform plan
    terraform apply

    Terraform will detect the new filter and update the external resource accordingly. You can see this reflected in the Vantage console.

Feature Requests​

To request additional features, please open an issue on GitHub or email us at support@vantage.sh.

- + \ No newline at end of file diff --git a/usage_based_reporting/index.html b/usage_based_reporting/index.html index 8e24205a..5d3a749d 100644 --- a/usage_based_reporting/index.html +++ b/usage_based_reporting/index.html @@ -10,7 +10,7 @@ - + @@ -19,8 +19,8 @@
-

Usage-Based Reporting

Usage-Based Reporting provides infrastructure consumption in non-monetary metrics, such as virtual machine running hours, stored gigabytes of data, and read/write units consumed. These reports are available within Cost Reports, where you can toggle between viewing consumption by spend or by usage.

note

Usage-Based Reporting is currently available for AWS, GCP, Azure, and Oracle. Vantage plans to add support for other providers. Please contact support@vantage.sh with other providers you’d like to see added.

Create Usage-Based Reports​

You can view usage from any Cost Report.

  1. Navigate to any Cost Report, or create a new report. By default, the report displays Spend.
  2. Apply any desired filters and Group By criteria. Then, click the Usage toggle to the right of the Settings menu.
tip

To get the most value from these reports, create a filter that represents a single unit of measure, comparing like resources (e.g., GB or Hours).

Toggle to show Usage-Based Reporting
  1. The following elements are displayed on the Usage view:
    • The graph and chart display usage over the selected timeframe.
    • The total cost is displayed as a trendline on the chart.
    • In the table below the graph, the Usage Unit (e.g., GB-Hours or Metrics) and Accrued Usage (a numerical value of calculated usage for that unit) columns are displayed to show accrued usage for each grouping. The Usage Unit column is normalized for consistency across usage type for spelling, abbreviation, and capitalization.
    • Accrued Cost, Previous Period Cost, and Change between these cost values are also displayed. Click the By Date option above the table to see the usage data split out by date.
  2. Save the report.
note

Usage data refreshes daily in the Vantage console. At this time, you cannot view retroactive usage metrics. Contact support@vantage.sh if you want to view historical usage data.

Export Usage Reports​

To export usage reports, follow the steps provided in the Cost Reports documentation. Ensure you are on the Usage view and Usage Unit is selected.

Exporting a Cost Report on the Usage view

View Usage Data for Custom Costs​

When you create a Custom Provider, you can add usage data to your CSV upload files. Ensure you complete the ConsumedQuantity and ConsumedUnit columns. See the Custom Providers documentation for information on the required schema.

Understand Usage Units​

The Usage Units displayed on Usage-Based Reporting include any dimension that a supported provider (e.g., AWS) meters and bills. Vantage standardizes these dimensions for inconsistencies in unit case and spelling across providers. For example, Vantage standardized Hours, hrs, Hrs, and hours to Hours.

note

If a provider does not have usage data, the Usage Unit column is empty and the Accrued Usage column displays 0.00.

Use Virtual Tags with Usage-Based Reporting​

Virtual Tags work across both cost and usage consumption for supported providers. If you created Virtual Tags based on cost, the associated usage consumption will inherit the same Virtual Tag. You can use Virtual Tags within your filter criteria to apply Virtual Tags based on usage.

Usage-Based Reporting on Dashboards​

You can add Usage-Based Reports to dashboards. Ensure you are on the Usage toggle, save the report, and then add it to a dashboard. Follow the Dashboards documentation for details on how to add a report to a dashboard.

Usage Reports Examples​

The following examples provide some common use cases for working with Usage-Based Reporting.

Understand EC2 Running Hours​

As an Engineering Manager, you want to view your Amazon EC2 usage by instance hours, so that you can get a profile of your compute usage. This is important because it helps you identify patterns in compute resource consumption. This type of report can help you create more efficient resource planning and cost optimization based on your team's workload needs.

You create the following Usage-Based Report in Vantage:

  • Filter: All costs from AWS where Category Amazon Elastic Compute Cloud - Compute is Compute Instance
  • Group By: Subcategory
Example of Usage-Based Report displaying EC2 instance running hours

The table below the chart includes the accrued usage and the unit of measure for each line item being viewed, such as EC2 instance bill code. To get the most value from this report, focus on identifying high-usage instance families and regions to optimize compute resources and explore opportunities for cost-saving strategies, like instance rightsizing or transitioning to Savings Plans.

View S3 Storage by Tier​

As a Storage Admin or Engineering Manager, you want to view detailed storage metrics across specific AWS services, such as the total data stored in S3 by tier. With this report, you can better understand the overall profile and efficiency of stored assets and potentially determine whether additional storage policies are required to optimize storage usage and growth.

You create the following Usage-Based report to see total data stored in S3 in Vantage:

  • Filter: All costs from AWS where Category Amazon Simple Storage Service is Storage
  • Group By: Subcategory
Example of Usage-Based Report displaying S3 storage options

In the table below the graph, usage data is displayed in GB-Months for subcategories like:

  • TimedStorage-INT-AIA-ByteHrs (Infrequent Access Tier)
  • TimedStorage-INT-IA-ByteHrs (Intelligent Tiering)
  • TimedStorage-ByteHrs (Standard Tier)

These metrics provide an overview of how data is distributed across different S3 storage tiers. Next steps could include analyzing whether data in the Infrequent Access and Intelligent Tiering categories is optimally stored, or you could decide whether more aggressive lifecycle policies are needed to move infrequently accessed data to cheaper storage tiers, like Glacier. You could also use this usage information to identify potential cost savings by reducing the storage volume in higher-cost tiers, such as the Standard Tier.

- +

Usage-Based Reporting

Usage-Based Reporting provides infrastructure consumption in non-monetary metrics, such as virtual machine running hours, stored gigabytes of data, and read/write units consumed. These reports are available within Cost Reports, where you can toggle between viewing consumption by spend or by usage.

note

Usage-Based Reporting is currently available for AWS, GCP, Azure, and Oracle. Vantage plans to add support for other providers. Please contact support@vantage.sh with other providers you’d like to see added.

Create Usage-Based Reports​

You can view usage from any Cost Report.

  1. Navigate to any Cost Report, or create a new report. By default, the report displays Spend.
  2. Apply any desired filters and Group By criteria. Then, click the Usage toggle to the right of the Settings menu.
tip

To get the most value from these reports, create a filter that represents a single unit of measure, comparing like resources (e.g., GB or Hours).

Toggle to show Usage-Based Reporting
  1. The following elements are displayed on the Usage view:
    • The graph and chart display usage over the selected timeframe.
    • The total cost is displayed as a trendline on the chart.
    • In the table below the graph, the Usage Unit (e.g., GB-Hours or Metrics) and Accrued Usage (a numerical value of calculated usage for that unit) columns are displayed to show accrued usage for each grouping. The Usage Unit column is normalized for consistency across usage type for spelling, abbreviation, and capitalization.
    • Accrued Cost, Previous Period Cost, and Change between these cost values are also displayed. Click the By Date option above the table to see the usage data split out by date.
  2. Save the report.
note

Usage data refreshes daily in the Vantage console. At this time, you cannot view retroactive usage metrics. Contact support@vantage.sh if you want to view historical usage data.

Export Usage Reports​

To export usage reports, follow the steps provided in the Cost Reports documentation. Ensure you are on the Usage view and Usage Unit is selected.

Exporting a Cost Report on the Usage view

View Usage Data for Custom Costs​

When you create a Custom Provider, you can add usage data to your CSV upload files. Ensure you complete the ConsumedQuantity and ConsumedUnit columns. See the Custom Providers documentation for information on the required schema.

Understand Usage Units​

The Usage Units displayed on Usage-Based Reporting include any dimension that a supported provider (e.g., AWS) meters and bills. Vantage standardizes these dimensions for inconsistencies in unit case and spelling across providers. For example, Vantage standardized Hours, hrs, Hrs, and hours to Hours.

note

If a provider does not have usage data, the Usage Unit column is empty and the Accrued Usage column displays 0.00.

Use Virtual Tags with Usage-Based Reporting​

Virtual Tags work across both cost and usage consumption for supported providers. If you created Virtual Tags based on cost, the associated usage consumption will inherit the same Virtual Tag. You can use Virtual Tags within your filter criteria to apply Virtual Tags based on usage.

Usage-Based Reporting on Dashboards​

You can add Usage-Based Reports to dashboards. Ensure you are on the Usage toggle, save the report, and then add it to a dashboard. Follow the Dashboards documentation for details on how to add a report to a dashboard.

Usage Reports Examples​

The following examples provide some common use cases for working with Usage-Based Reporting.

Understand EC2 Running Hours​

As an Engineering Manager, you want to view your Amazon EC2 usage by instance hours, so that you can get a profile of your compute usage. This is important because it helps you identify patterns in compute resource consumption. This type of report can help you create more efficient resource planning and cost optimization based on your team's workload needs.

You create the following Usage-Based Report in Vantage:

  • Filter: All costs from AWS where Category Amazon Elastic Compute Cloud - Compute is Compute Instance
  • Group By: Subcategory
Example of Usage-Based Report displaying EC2 instance running hours

The table below the chart includes the accrued usage and the unit of measure for each line item being viewed, such as EC2 instance bill code. To get the most value from this report, focus on identifying high-usage instance families and regions to optimize compute resources and explore opportunities for cost-saving strategies, like instance rightsizing or transitioning to Savings Plans.

View S3 Storage by Tier​

As a Storage Admin or Engineering Manager, you want to view detailed storage metrics across specific AWS services, such as the total data stored in S3 by tier. With this report, you can better understand the overall profile and efficiency of stored assets and potentially determine whether additional storage policies are required to optimize storage usage and growth.

You create the following Usage-Based report to see total data stored in S3 in Vantage:

  • Filter: All costs from AWS where Category Amazon Simple Storage Service is Storage
  • Group By: Subcategory
Example of Usage-Based Report displaying S3 storage options

In the table below the graph, usage data is displayed in GB-Months for subcategories like:

  • TimedStorage-INT-AIA-ByteHrs (Infrequent Access Tier)
  • TimedStorage-INT-IA-ByteHrs (Intelligent Tiering)
  • TimedStorage-ByteHrs (Standard Tier)

These metrics provide an overview of how data is distributed across different S3 storage tiers. Next steps could include analyzing whether data in the Infrequent Access and Intelligent Tiering categories is optimally stored, or you could decide whether more aggressive lifecycle policies are needed to move infrequently accessed data to cheaper storage tiers, like Glacier. You could also use this usage information to identify potential cost savings by reducing the storage volume in higher-cost tiers, such as the Standard Tier.

Usage-Based Reporting Video Demonstration​

The below video talks about how to get started with Usage-Based Reporting.


+ \ No newline at end of file diff --git a/vantage_account/index.html b/vantage_account/index.html index aaf9cda2..d820b8c3 100644 --- a/vantage_account/index.html +++ b/vantage_account/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Account Settings

From the Vantage account Settings page, you can edit your personal profile, create API access tokens, and configure organizational settings.

General Settings​

note

Only Organization Owners can configure organization settings. See the Role-Based Access Control (RBAC) documentation for details.

From the top navigation bar of the Vantage console, click Settings. On the side navigation bar, review the options under General Settings.

Currency Conversion​

note

At this time, presentational currency conversion is available only on Vantage reports, such as Cost Reports, Kubernetes Efficiency Reports, Financial Commitment Reports, and Provider Resource Reports. Additional scopes will be added soon.

By default, Vantage displays costs in US Dollars (USD). You can set a presentational currency, on a per-workspace basis, to visualize cost reporting data in a currency of your choice. When you configure currency for a workspace, you can choose between using the previous month’s closing exchange rate or the daily exchange rate. Vantage calculates the exchange rate based on a public API.

To enable currency conversion:

  1. From the top navigation, click Settings
  2. On the side navigation, click Workspaces. All your existing workspaces are displayed. Select the workspace where you want to enable currency conversion.
  3. At the top of the Workspaces page, under Preferred Currency, click the toggle to enable this setting. (You can click this toggle again to disable the setting.)
  4. Select your preferred currency from the list.
  5. For Exchange Rate Dates, select one of the following conversion date options. For the most accurate results, use the currency method in which you are billed:
    • Daily Rate: Vantage maintains a daily snapshot of exchange rates to provide estimated currency conversions. With the Daily Rate option, the costs' corresponding daily exchange rate will be used for the conversion.
    • End of Billing Period Rate: Vantage matches each cost entry to the last date of the corresponding month in which the cost was incurred.

Your settings are automatically saved and available on your reports.

note

If you disable currency, your presentational currency will default back to USD.

Manage Workspaces​

Provider integrations are organized into workspaces. From the Workspaces section, you can manage each of your workspaces as well as create a new one. See the Workspaces documentation for more information.

View Billing & Plans​

From the Billing & Plans section, you can view your usage, current plan, and previous payments/invoices.

If you need to use a different email address for invoicing, please contact Vantage Support at support@vantage.sh.

Invite Users to Your Account​

From the People section, you can invite new users, view a user's role and team associations, and remove users. To invite a new user:

  1. Under General Settings, select People.
  2. Click Invite People.
  3. Enter the user's email and select a role and associated teams.
  4. Click Send Invitation. The new user's name will appear in the People list with Invite Pending as well as a link to Resend the invite.

Click the ellipses (...) next to a user's name to edit or remove a user.

Configure Teams​

See the Role-Based Access Control (RBAC) documentation for details on team configuration.

Configure Authentication​

Vantage supports many Single Sign-On (SSO) options. See the SSO documentation for more information.

Configure Integrations​

Configure provider integrations from the General settings. See the Integrations documentation for more information.

Create an API Token​

You can use the Vantage API to programmatically access cloud pricing data.

Create a Vantage API Service Token​

Service tokens are associated with an account, not with an individual user. For Enterprise customers who use teams and role-based access control, you have the option of selecting a team to inherit permissions from.

To generate an API service token:

  1. On the left navigation of the Settings screen, select API Access Tokens.
  2. Enter a new token name, choose a team (if applicable), select the Read and/or Write scope, and click Create.
  3. Click Show to reveal and copy your token.

To revoke a token, click Delete.

Create a Vantage API Personal Access Token​

Personal access tokens are associated with the user who created the token.

To generate an API personal access token:

  1. On the left navigation of the Settings screen, select API Access Tokens, then navigate to the Personal Access Tokens tab.
  2. Enter a new token name, select the Read and/or Write scope, and click Create.
  3. Click Show to reveal and copy your token.

To revoke a token, click Delete.

Personal Settings​

From the top navigation bar of the Vantage console, click Settings. On the side navigation bar, review the options under Personal Settings.

Update Your Profile​

In the Profile section, you can change your display name as well as your email address. Note that changing your email will log you out and require you to re-confirm. You can also select a default dashboard that's displayed when you navigate to console.vantage.sh. See the Default Dashboards documentation for details.

Reset Your Password​

note

The following steps are for users who directly sign in to Vantage.

If you forget your password or would like to change your password, follow the below steps.

  1. From the top-right corner of the console, click the profile icon, then click Logout.
  2. You will return to the Login screen. Type your email in the Email Address field. Then, click Continue.
  3. On the Sign In page, click Forgot your password? and enter your email again.
  4. You will receive an email with a link to reset your password. Click confirm the password change, then enter a new password.
  5. Click the right-facing arrow, then go to console.vantage.sh to sign in with your new password.
- + \ No newline at end of file diff --git a/vantage_university/index.html b/vantage_university/index.html index c74e947c..e7810b47 100644 --- a/vantage_university/index.html +++ b/vantage_university/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

🎓 Vantage University

Observability, Visibility, Optimization

Vantage is an observability, visibility, and optimization tool that provides you with clear insights into your cloud cost data. Create reports and dashboards, monitor your costs for anomalies, and view recommendations for how to optimize your resources. Vantage has multiple provider integrations to help you view all your cloud costs in one place.

Welcome to Vantage University!

Select a topic below to explore Vantage features. Each topic includes a set of video lessons that you can follow along with as you get set up in your own Vantage account. With each topic, you'll be provided with a list of additional resources to help you navigate the console.

User-Specific Learning Tracks

Follow these learning tracks to understand how to best use Vantage in your role.

FinOps Analyst lesson track logo

FinOps Analyst

Learn about how to use Vantage effectively as your organization’s FinOps power user, building a culture of cloud cost optimization.

Developer lesson track logo

Developer

Learn about how you can best use Vantage to manage and optimize the cloud resources you are responsible for.

Finance Manager lesson track logo

Finance Manager

Learn about how you can use Vantage to manage and analyze the total cost of your organization.

Video Lessons

Follow these sections to better understand how to use specific Vantage features.

Vantage University logo with Account Management as a title

  • Create a new workspace
  • Navigate through your workspaces

Vantage University logo with Integrations as a title

  • Create integrations
  • Add Custom Providers

Vantage University logo with Cost Reporting as a title

  • Create and view Cost Reports
  • Learn about additional Cost Reporting tools

Vantage University logo with Cost Allocation as a title

  • Create a segment hierarchy
  • Explore virtual tagging

Vantage University logo with Observability as a title

  • View and create anomaly alerts
  • Review and act on cost recommendations

Vantage University logo with Unit Costs as a title

  • Understand unit costs
  • View and analyze business metrics

Vantage University logo with Budgeting as a title

  • Create a cost budget
  • Configure budget alerts

Vantage University logo with Per Resource Costs as a title

  • Monitor and manage per-resource costs
  • View network flows and associated costs

- + \ No newline at end of file diff --git a/vantage_university_account_management/index.html b/vantage_university_account_management/index.html index 69f1f477..b1ad189d 100644 --- a/vantage_university_account_management/index.html +++ b/vantage_university_account_management/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Account Management

💡 What Are Workspaces?​

Workspaces in Vantage provide users with the ability to link multiple cloud infrastructure provider accounts to a single Vantage account. These workspaces serve as separate environments where users can organize and analyze costs and resources, either within individual cloud provider accounts or across multiple providers.

💭 Why Should I Use Workspaces?​

Workspaces in Vantage offers several benefits:

  • Cost Visibility: Workspaces enable users to gain a comprehensive view of expenses within a specific cloud provider account or across multiple providers, facilitating better cost management and optimization.
  • Resource Organization: By grouping resources within workspaces, teams can create focused views tailored to their specific needs.
  • Access Control: With role-based access controls (RBAC) (Enterprise feature), administrators can also limit user access to different workspaces.

📝 Workspaces Use Cases​

  • As a cloud administrator overseeing a diverse infrastructure, you can create a distinct Vantage workspace for each of your environments, such as Production, Staging, and Development. Then, specify which provider accounts are associated with which workspace. For example, a particular Datadog account may be associated with only your Development workspace.
  • As a product manager who is responsible for overseeing various products or services, attributing costs accurately is important for team accountability. By creating separate workspaces for each product or service, you can isolate expenses, track resource utilization, and easily assess the financial performance of individual offerings.

📚 Lesson 1: Navigate Workspaces​


📚 Lesson 2: Manage Workspace Provider Integrations​


📖 Additional Resources​

- + \ No newline at end of file diff --git a/vantage_university_budgeting/index.html b/vantage_university_budgeting/index.html index a66fdb0d..80f9f595 100644 --- a/vantage_university_budgeting/index.html +++ b/vantage_university_budgeting/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Budgeting

💡 What Is Budgeting in Vantage?​

In Vantage, you can create budgets and be alerted if costs are trending over budget. You can import budgets for hundreds of accounts, organizational units, and services as part of annual planning. Configure alerts for email, Slack, or Microsoft Teams when costs are trending over budget, with quick links to investigate.

💭 Why Should I Use Vantage Budgets?​

Using Vantage budgets allows you to control cloud spending effectively, ensuring costs stay within planned limits. You can create multiple alerts for various teams or projects to ensure budgets stay on track.

📝 Budgets Use Cases​

  • As a financial analyst, you create a budget for the entire organization. You configure the associated alert to notify you 10 days before the end of the month if costs are trending over budget. This allows you to review and adjust spending in time to stay within financial targets, ensuring that there are no surprises at month-end and supporting accurate financial reporting and planning.
  • As an application owner, you are responsible for ensuring that costs don't exceed the budget allocated to your specific application. You create a budget and alert that notifies you when costs have exceeded 75% of the budget. This way, you can take proactive measures to adjust resource usage for your application and stay within your team’s allocated budget.

📚 Lesson 1: Create a Budget​


📚 Lesson 2: Create Budget Alerts​


📖 Additional Resources​

- + \ No newline at end of file diff --git a/vantage_university_cost_allocation/index.html b/vantage_university_cost_allocation/index.html index cc0b3a7d..55dc89fe 100644 --- a/vantage_university_cost_allocation/index.html +++ b/vantage_university_cost_allocation/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Cost Allocation

💡 What Is Cost Allocation?​

Cost allocation is the process of assigning costs to different parts of an organization, such as teams, projects, or business units, to accurately track and manage expenses. Vantage provides a few different cost allocation tools, including:

  • Virtual tags: Virtual tags allow you to create consistent and standardized tags across all cloud providers within Vantage. You can tag costs without needing to make changes to your existing cloud infrastructure. Virtual tags are useful for ensuring uniform tagging practices.
  • Cost allocation segments: Cost allocation segments let you create hierarchical structures for your costs, mapping them to various organizational entities, such as business units, teams, or services. Segments ensure that costs are allocated only once, preventing duplication in showback or chargeback scenarios. This tool is ideal for detailed cost tracking and enforcing cost governance, allowing you to identify and address unallocated costs.

💭 Why Should I Use Cost Allocation?​

Using cost allocation tools like virtual tags and cost allocation segments in Vantage helps you gain better control over your cloud spending. Virtual tags ensure consistent and accurate cost tagging across all cloud providers, making your financial reporting more reliable. Cost allocation segments enable detailed tracking and governance of expenses, allowing you to allocate costs effectively.

📝 Cost Allocation Use Cases​

As a financial analyst, you can:

  • Use virtual tags to standardize tagging across all cloud providers without involving the engineering team, ensuring that your financial reports are uniform and reliable.
  • Use segments to identify unallocated costs. Ensure all expenses are properly assigned and accounted for. This improves financial accountability by ensuring no costs are overlooked in your financial reports.

As a cloud operations manager, you can:

  • Use virtual tags for tag consolidation. You may manage a large infrastructure with an inconsistent tagging schema. You also need reports that help you quickly filter and group cloud resources to identify cost-saving opportunities and optimize resource usage, such as changing instance types or selected databases.
  • Use segments to hierarchically map costs to the different cloud operations teams and their corresponding applications you are responsible for, providing a detailed and organized view of cost distribution across your division.

📚 Lesson 1: Create Virtual Tags​


📚 Lesson 2: Create Cost Allocation Segments​


📖 Additional Resources​

- + \ No newline at end of file diff --git a/vantage_university_cost_reporting/index.html b/vantage_university_cost_reporting/index.html index 9a3d7d79..9f035f33 100644 --- a/vantage_university_cost_reporting/index.html +++ b/vantage_university_cost_reporting/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Cost Reporting

💡 What Is Cost Reporting?​

Cost Reports are one of the fundamental tools in Vantage. They provide complex reporting to slice and dice the data for many use cases. You can create numerous reports in Vantage and use filters, grouping parameters, and timeframe options to see the exact data you want to see. Cost Reports include a chart view and a cost table. You can manipulate the view to highlight certain data points and zoom in on particular dates or areas where you see anomalies.

💭 Why Should I Use Cost Reporting?​

Cost Reports can help any user or stakeholder to view the exact costs they want to see across any cloud provider (e.g., AWS), a set of accounts, or even check on their current tagging schema. If you want to see a longitudinal view of your cost data and have the ability to filter by multiple parameters, then you can start with Cost Reports to get an overall picture of the state of your costs. Vantage provides you with Cost Reports and additional Cost Reporting tools, like:

  • Cost Report forecasts
  • Annotations
  • Vantage Issues

📝 Cost Reporting Use Cases​

Cost Reports are helpful for any FinOps stakeholder—from engineering managers to organizational management.

  • As an engineering manager, you may want to see why data transfer costs are increasing for storage resources. You can create a Cost Report with filters for AWS data transfer costs and view down to the resource level where you’re seeing the highest cost spikes. You use the Annotations and Vantage Issues feature to collaborate with other teams and understand changes in data transfer costs over time.
  • As a FinOps stakeholder, you may want to review your tagged resources and ensure teams are following tagging standards. You can create a report to check for untagged resources across one or more providers. Use this report to help you add missing tags or update existing tags.
  • As an application owner, create a monthly overview of all costs related to your application. You can create a report that breaks down expenses by resource and cost category. Filter for resources with your application’s corresponding tag. Use the report to track spending trends and variations to understand the cost impact of application usage and changes over time. You set up Cost Report notifications to send you a monthly digest of specific reports so you can remember to go in and check where things are at each month.

📚 Lesson 1: Create and View a Cost Report​


📚 Lesson 2: Filter a Cost Report​


📚 Lesson 3: View Cost Report Forecasts​


📚 Lesson 4: Create Cost Report Notifications​


📚 Lesson 5: Add Annotations to Cost Reports​


📚 Lesson 6: Create Vantage Issues​


📖 Additional Resources​

- + \ No newline at end of file diff --git a/vantage_university_developer/index.html b/vantage_university_developer/index.html index 7b5be191..4a82012a 100644 --- a/vantage_university_developer/index.html +++ b/vantage_university_developer/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Developer

Vantage University: Developer Track​

Welcome to the Developer learning track on Vantage University!

📚 Lesson 1: Introduction to the Developer Track​


📚 Lesson 2: Managing Resources​

See the following videos and other materials to help you get started with managing resources, like rightsizing EC2 instances and Kubernetes workloads, viewing network-related costs, and creating resource inventories to view resource reports.


📖 Additional Resources​

Click to view resources

📚 Lesson 3: Optimizing Kubernetes Efficiency​

See the following resources to help you get started with the Vantage Kubernetes agent and creating and viewing Kubernetes Efficiency Reports.


📖 Additional Resources​

Click to view resources

📚 Lesson 4: Using the Vantage API and Terraform Provider​

See the following resources to help you get started with the Vantage API and Terraform provider.


📖 Additional Resources​

Click to view resources
- + \ No newline at end of file diff --git a/vantage_university_finance_manager/index.html b/vantage_university_finance_manager/index.html index e40859c7..9d938360 100644 --- a/vantage_university_finance_manager/index.html +++ b/vantage_university_finance_manager/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Finance Manager

Vantage University: Finance Manager Track​

Welcome to the Finance Manager learning track on Vantage University!

📚 Lesson 1: Introduction to the Finance Manager Track​


📚 Lesson 2: Set Up Budget Visibility​

See the following resources to help you get started with Cost Reports, saved filters, folders, and dashboards.


📖 Additional Resources​

Click to view resources

📚 Lesson 3: Understanding the Cost of Your Business​

See the following resources to help you get started with Virtual Tags, dynamic cost allocation, untagged resources, and Cost Allocation Segments.


📖 Additional Resources​

Click to view resources

📚 Lesson 4: Viewing Report Forecasts​

See the following resources to help you get started anomalies, annotations, and issues in Vantage.


📖 Additional Resources​

Click to view resources
- + \ No newline at end of file diff --git a/vantage_university_finops_analyst/index.html b/vantage_university_finops_analyst/index.html index a36515f7..031c83b9 100644 --- a/vantage_university_finops_analyst/index.html +++ b/vantage_university_finops_analyst/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

FinOps Analyst

Vantage University: FinOps Analyst Track​

Welcome to the FinOps Analyst learning track on Vantage University!

📚 Lesson 1: Introduction to the FinOps Analyst Track​


📚 Lesson 2: Building Comprehensive Cloud Cost Visibility​

See the following resources to help you get started with Cost Reports, saved filters, folders, and dashboards.


📖 Additional Resources​

Click to view resources

📚 Lesson 3: Achieving 100% Cost Allocation​

See the following resources to help you get started with Virtual Tags, dynamic cost allocation, untagged resources, and Cost Allocation Segments.


📖 Additional Resources​

Click to view resources

📚 Lesson 4: Detecting and Preventing Unusual Spending​

See the following resources to help you get started anomalies, annotations, and issues in Vantage.


📖 Additional Resources​

Click to view resources
- + \ No newline at end of file diff --git a/vantage_university_integrations/index.html b/vantage_university_integrations/index.html index 4feb9aa9..414471e8 100644 --- a/vantage_university_integrations/index.html +++ b/vantage_university_integrations/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Integrations

💡 What Are Vantage Integrations?​

Vantage offers a number of native integrations to help you understand all your cloud costs. In addition to integrations within Vantage you can connect Custom Providers so that you can monitor costs across your entire tech stack.

📝 Integrations Use Cases​

  • As a DevOps Engineer, you need to consolidate cost data from various cloud providers into a single platform for better visibility. You connect both AWS and GCP, which are your main cloud providers. You also want to view monitoring costs from Datadog, which you help to oversee, so you use the native Datadog integration in Vantage to view the total cost impact of your work.
  • As a FinOps Analyst, you are very familiar with the FOCUS schema. You currently have a few of your major cloud providers connected to Vantage, but there are some other tools your organization uses that you would like to see displayed alongside those cloud providers. You convert cost and usage reports from these other providers to the schema that's used on Vantage, and based on FOCUS, and use the Custom Providers feature to see costs for your organization's entire tech stack.

📚 Lesson 1: Creating Integrations in Vantage​


📚 Lesson 2: Connecting Custom Providers​


📚 Lesson 3: Integration Example - GitHub​


📖 Additional Resources​

- + \ No newline at end of file diff --git a/vantage_university_observability/index.html b/vantage_university_observability/index.html index 4ae54f6d..a4a5ee37 100644 --- a/vantage_university_observability/index.html +++ b/vantage_university_observability/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Observability

💡 What Is Observability?​

Cloud cost observability is the practice of monitoring cloud spending to gain insights into resource usage, what's driving your costs, and opportunities to optimize. Vantage offers the following observability tools:

  • Cost anomalies in Vantage notify teams of excess costs and help engineers fix misconfigurations or other problems before they become very expensive.
  • Vantage analyzes your infrastructure as it evolves and changes and provides cost recommendations to lower your bill.

💭 Why Should I Use Observability Tools?​

It’s always better to know about something before it happens. Recommendations and anomaly alerts are tools that let you know about increasing costs. They provide a way for you to quickly act and implement cost-saving measures for your organization before costs get out of hand.

📝 Observability Tools Use Cases​

  • You are a site reliability engineer (SRE) and you are responsible for monitoring Datadog logs. You create a Cost Report for Datadog costs and set up an anomaly alert that will let you know if Log Management costs get out of hand.
  • As a platform engineer, you are responsible for ensuring that Kubernetes clusters are properly configured with the right amount of resources to optimize performance and cost. You use Vantage Kubernetes rightsizing recommendations to see your current usage and notice many of your clusters are overprovisioned. You implement these recommendations to realize the potential monthly savings.

📚 Lesson 1: View Cost Anomalies and Alerts​


📚 Lesson 2: View Cost Recommendations​


📖 Additional Resources​

- + \ No newline at end of file diff --git a/vantage_university_per_resource_costs/index.html b/vantage_university_per_resource_costs/index.html index bf69bfbc..11a37ab6 100644 --- a/vantage_university_per_resource_costs/index.html +++ b/vantage_university_per_resource_costs/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Per Resource Costs

💡 What Are Per Resource Costs?​

Per resource costs refer to the expenses associated with individual cloud resources, including both direct costs and those incurred through network traffic. By analyzing data from Active Resources, Resource Reports, and Network Flow Reports, you can gain a detailed understanding of how each resource contributes to your overall cloud spending.

  • Active Resources: Provide an overview of all active resources (e.g., and active virtual machine) and their associated costs.
  • Resource Reports: Break down costs by specific resources, providing insights into cost distribution.
  • Network Flow Reports: Analyze the costs of network traffic associated with your resources.

💭 Why Should I Use Them?​

  • Comprehensive cost visibility: Combining data from Active Resources, Resource Reports, and Network Flow Reports offers a complete picture of how each resource impacts your total expenses. This visibility helps in identifying major cost drivers and optimizing resource usage.
  • Optimization opportunities: By pinpointing high-cost resources and inefficient network traffic, you can make informed decisions to optimize resource allocation and reduce unnecessary spending. Use rightsizing recommendations for EC2 instances and Kubernetes workloads to rightsize specific expensive resources.

📝 Per Resource Cost Use Cases​

  • As a cloud architect, you can use these tools to ensure that your cloud infrastructure is designed efficiently. By analyzing Active Resources and Resource Reports, you identify underutilized or unused resources that could be downsized or terminated to save costs.
  • As a DevOps engineer managing a complex application with multiple microservices, Network Flow Reports help you detect that high cross-AZ traffic between microservices is leading to increased costs. You can then focus on optimizing network configurations, such as reducing cross-AZ traffic or implementing VPC endpoints, to lower costs while maintaining application performance.

📚 Lesson 1: View Active Resources and Create Resource Reports​


📚 Lesson 2: Understand Network Flow Reports​


📖 Additional Resources​

- + \ No newline at end of file diff --git a/vantage_university_unit_costs/index.html b/vantage_university_unit_costs/index.html index 47e73b35..b975e7fa 100644 --- a/vantage_university_unit_costs/index.html +++ b/vantage_university_unit_costs/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Unit Costs

💡 What Are Unit Costs and Business Metrics?​

A unit is any metric that your business tracks, like users, requests, transactions, or customers. In Vantage, you can add unit costs as a visualization on Cost Reports to visualize your cloud infrastructure costs on a per unit basis. A business metric is a unit of data from your business that’s aggregated and combined with costs to produce a per unit cost—like cost per daily active user, cost per customer, or cost per million API requests. Business metrics can be solely related to business goals, like cost per user, or related to system metrics, like cost per API request.

💭 Why Should I Use Them?​

Most organizations already have key performance indicators, or KPIs, as a part of their company's goals. They help to measure efficiency and provide a better context for why you may be experiencing cost spikes. For example, some spikes may be justified based on adding a new user or increasing your customer base. Tracking per unit costs helps to provide some details as to why costs are changing.

📝 Business Metrics Use Cases​

  • You are a financial analyst at a SaaS company and use unit costs and business metrics to understand the cost per daily active user (DAU). By visualizing cloud infrastructure costs on a per unit basis, you can determine how changes in user activity impact overall costs. For example, if there’s a spike in costs, you can correlate it with an increase in DAUs, justifying the expenditure and helping the company plan budgets more accurately.
  • As a DevOps engineer, you can use business metrics to track the cost per million API requests for a microservices-based application. By visualizing these costs, you can pinpoint which services are driving up expenses. If a particular microservice shows a disproportionate cost increase per API request, you can investigate performance tuning, resource optimization, or architectural changes to reduce costs and improve efficiency without compromising on service quality.

📚 Lesson 1: Understand Unit Costs and Business Metrics​


📚 Lesson 2: Create Business Metrics​


📖 Additional Resources​

- + \ No newline at end of file diff --git a/virtual_tagging/index.html b/virtual_tagging/index.html index 5c6cd2ce..6fa42703 100644 --- a/virtual_tagging/index.html +++ b/virtual_tagging/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Virtual Tagging

You can create virtual tags to consistently tag costs across providers in Vantage. This feature can help to increase tagging coverage across your cloud infrastructure. Create cost allocation tag keys with a set of corresponding values and filters directly in the Vantage without needing to involve your engineering team in making infrastructure changes. All provider integrations in Vantage are supported, including providers that don't natively support tags.

Virtual tags are available for filtering and aggregating on all Cost Reports and cost allocation segments. They can also be used in filter criteria on saved filters. There is no limit to the number of tag keys or values you define.

tip

To get started with virtual tagging, you can also view a video demo on Vantage University 🎓.

Virtual Tags vs. Saved Filters vs. Cost Allocation Segments​

Virtual tags can be considered foundational to the rest of the data within Vantage. They should remain fairly static, and changes should be considered delicate. These changes will flow across all data and apply to all workspaces. The most common tag keys will be items like team, cost center, and environment.

Segments can then be used to create different hierarchical views for tagged data. This feature is useful for breaking down the data by different perspectives, such as by cost center or by OPEX/CapEX.

Saved filters can then be used in a more ad-hoc fashion to add lenses on top of base data. For instance, you could create a saved filter just for North America that standardizes a set of regions across providers and can be used by teams on their reports or dashboards without having to know the set of filters needed to create the list of regions. When new regions come online, it’s easy to modify the saved filter to include this region.

note

If you want to transition any of your cost allocation segments to virtual tags, contact support@vantage.sh.

Custom Value Tags​

With custom value tags, you can create new cross-provider cost allocation tags to help better your tagging strategy. For example, you may have a series of resource tags, by product, across each of your providers. You can create custom tags in Vantage to combine those costs into one unique product tag for all resources in that product group.

See the example section below for details.

Cost-Based and Business Metrics-Based Allocation Tags​

The cost-based and business metrics-based allocation tag types allow for dynamic cost allocation, which is the process of allocating costs based on another existing cost or metric. See the below video for an introduction to dynamic cost allocation.

Cost-Based Allocation Tags​

With cost-based allocation tags, you can create a dynamically allocated cost structure. Select a set of input costs (e.g., all AWS costs), an existing cost tag to use for allocation (e.g., a teams cost tag), and an output cost (e.g, a static cost, like AWS Support) that you want to be allocated the same way as your input cost.

See the example section below for details.

Business Metrics-Based Allocation Tags​

With business metrics-based allocation tags, you select an existing business metric (e.g., CPU use per product) and indicate your output cost (e.g., all GCP Compute costs) so that the allocation of the output cost mimics the percentage allocation of the existing business metric.

See the example section below for details.

Create Virtual Tags​

note

This feature requires Owner permissions in Vantage. See the Role-Based Access Control documentation for details. Virtual tags apply to all workspaces.

  1. From the top navigation, click Settings.

  2. From the side navigation, under General Settings, click Virtual Tags.

  3. All existing virtual tags are displayed alphabetically. You can edit and delete any existing tags from this screen. To add a new virtual tag, click Create a Virtual Tag.

  4. Enter a title for the Tag Key.

  5. For Billing Period Backfill, select a billing period (e.g., Apr 2024) for which the tag should be backfilled.

  6. Enable the Can Override toggle if you want the virtual tag to override an existing service cost value. For example, if you create a virtual tag that conflicts with an existing provider tag, this option will override the existing provider tag key in Vantage reports.

  7. In the Values section, click +Add. Select whether you want to create a Custom Value, Business Metric, or Cost Based value. Click through the tabs below for instructions on each value type.

    note

    You cannot use an existing Virtual Tag within the Output Costs Filter for any type of new Virtual Tag. You can, however, select an existing provider tag (e.g., one that comes from AWS).

    1. Click Assign Custom Value.
    2. Enter a Tag Value title. Titles can contain only letters, numbers, and the following characters: \_ - & + , . : / \. You cannot use saved filters to define a virtual tag value's filters.
    3. Specify the tag value's filter criteria (i.e., Output Cost Filters). These filters function just like filters on Cost Reports and cost allocation segments. For information on how to create detailed filters, see the Cost Reports documentation.

  8. At the top, click Save.

Processing tag changes usually takes under an hour. At the top of the Virtual Tags screen, the processing status is displayed. Processing times vary based on the number of tags and volume of data you have imported into Vantage.

The Virtual Tag screen with a processing status displayed for Fastly and New Relic

Virtual Tag Order​

Tag values are arranged in priority order on the Virtual Tags screen. You can move tag values up and down in the UI to reorder them, as demonstrated in the visual example below.

GIF of two tag values, staging and production, being reordered in the Tags UI

When cost data is ingested into Vantage, the first value that matches the corresponding filters will be applied to that line item. In cases where filters overlap, the order of tag values within each key determines the value that is applied.

Filter and Group by Virtual Tags​

You can filter by virtual tags in Cost Reports, cost allocation segments, and when creating saved filters. Virtual tags are visible along with your existing provider tags. Use the Tag (Label in GCP) filter and grouping option.

A Cost Report filter with two filters applied: one for AWS costs for the team/data tag and one for GCP costs with the same tag

Delete a Virtual Tag​

To delete a virtual tag, navigate to the Virtual Tags page. All existing tag keys are displayed. Click the trashcan icon next to a tag key. Your data will be re-tagged, excluding the deleted virtual tag, going back to the deleted tag’s backfill bill period. Newly ingested data will no longer be tagged with the deleted tag.

Virtual Tagging Examples​

The following examples demonstrate how to use virtual tagging in a multi-provider organization.

Custom Value Examples​

Example 1: Cross-Provider Tagging​

You want to create a tag mapping for each of your teams that maps corresponding teams with certain services and provider accounts.

Step 1: Create a New Tag​

You create a tag key called Teams.

The Tag Key field displayed in the Virtual Tags UI; the name Teams is entered
Step 2: Add Tag Values and Filters​

You add the corresponding set of virtual tag values and filters:

  • The data team tag value corresponds with a filter for all costs for GCP BigQuery and Amazon Redshift.
  • The mobile team tag value corresponds with a filter for its related GCP projects and AWS accounts.
  • You continue this pattern and create similar values with corresponding filters for your other teams.
A sample Tag Value field for a value of data with filter for Service of BigQuery and Amazon RedshiftA sample Tag Value field for a value of data with a filter for GCP Project of mobile and AWS account of mobile

Within Cost Reports, you can easily filter and group by these tag options to easily see costs for an individual team. In the below visual example, the Cost Report is grouped by the team tag, and the mobile and data values are displayed along with the other team tag values you created.

A sample Cost Report grouped by Tag showing a mobile and data tag

Example 2: Consolidate Existing Tags​

You have a tagging practice established at your organization, but teams often create tags with spelling variations, tags with typos, or they create duplicate tags. For example, the data team has resources tagged with data, Data, and data-prod. This is an issue across many of your teams. You want to consolidate all these tags, across providers, into one data tag.

Step 1: Create a New Tag​

You create a tag key called Teams to override existing tags.

The Tag Key field displayed in the Virtual Tags UI; the name Teams is entered
Step 2: Add Tag Values and Filters​

You add the corresponding set of virtual tag values and filters. In this example, all permutations of the data team tag are combined into one virtual tag.

A sample Tag Value field for a value of AWS team tags equaling data, data-prod, and Data. Another value for a GCP team Label equaling data

Within Cost Reports, you can easily filter by this tag to see all costs related to the data team. This saves you the work of needing to always filter for all permutations of this tag. Now, you need to filter by only one tag.

A Cost Report with a filter for AWS and GCP team tag of data

Cost-Based Allocation Example​

In your organization, teams share resources, such as RDS databases or EC2 instances, and each team consumes different percentages of these resources each month. Your organization is also charged a static support fee each month for AWS. As shown in the diagram below, you want to allocate a portion of the support fee to each team based on their proportional use of AWS resources. So in the below example, since the Infra team is responsible for 50% of all AWS costs, they should also be responsible for 50% of the support fee. You can create a cost-based allocation virtual tag for allocating portions of the support fee to each respective team.

A flowchart that has the AWS logo in a block at the top. AWS has three arrows pointing to tag icons that say Infra 50%, Mobile 20%, and Data 30%. These tags point to a box that says Dynamic Cost Allocation with the icon for AWS Support. This box has three arrows that point to three boxes. The boxes say Infra Team AWS Support Costs 50%, Mobile Team AWS Support Costs 20%, and Data Team AWS Support Costs 30%.

Prerequisites​

You have an existing provider tag in AWS that identifies resources for your teams. This tag will be used in step 2.

Step 1: Create a New Cost-Based Allocation Tag​

  • Navigate to Settings > Virtual Tags.
  • Create a new virtual tag.
  • Select the Cost-Based option for the tag value.

Step 2: Select an Input Cost Filter​

For your input cost, select All AWS Costs. Set an additional filter for the Usage charge type to filter on only usage-related costs. This filter will ignore costs related to items like credits, taxes, fees, etc.

Step 3: Select a Tag Key​

You select your existing teams tag key you have in AWS that will be used for allocating costs.

Step 4: Select an Output Cost Filter​

In this example, since your infrastructure team is responsible for 50% of all AWS costs, the mobile team for 20%, and the data team for 30%, you can mimic this allocation across another static cost, or your output cost. Select the filters for the AWS support fee.

A sample Tag Value field for AWS Support Fee costs

Once the tag is created, create a new Cost Report and add the following criteria:

  • Create a filter for AWS Support costs.
  • Add grouping criteria to group by your new cost-based dynamic allocation tag.

The resulting report shows how much of the support fee each team is allocated.

A sample Tag Value field for AWS Support Fee costs

Business Metrics-Based Allocation Example​

You are working with your infrastructure team and want to ensure that the proportional cost of CPU time on a shared resource is allocated to the distinct cost centers that are consuming the CPU. In the below example, you want each team’s portion of CPU usage billed as a corresponding percentage of the overall Namespace CPU cost. So, if Team A uses 30% of the resource’s CPU, then they should be billed a proportional percentage of the total Namespace’s costs.

A flowchart that has a CPU icon in a block at the top and says Shared Resource CPU. CPU has two arrows pointing to two boxes with people icons that say Team A CPU Usage and Team B CPU Usage. These boxes point to a box that says Total Namespace Costs with the Kubernetes icon. This box has two arrows that point to two boxes that say Portion of Namespace Costs Allocated to Team Based on Portion of CPU Usage.

Prerequisite​

To determine the cost of CPU time to allocate to each respective team, you first create a labeled business metric that includes the CPU time labeled by team. Vantage then calculates the respective percentage of CPU time for each team. The labeled business metric has the following format.

date,amount,label
2024-01-09,825,teama
2024-01-09,600,teamb
2024-01-10,500,teama
2024-01-10,200,teamb
2024-01-11,723,teama
2024-01-11,456,teamb

Step 1: Create a New Business Metrics-Based Allocation Tag​

You create a new business metrics-based tag:

  • Navigate to Settings > Virtual Tags.
  • Create a new virtual tag.
  • Select the Business Metric option for the tag value.

Step 2: Select the Labeled Business Metric​

Search for and select the labeled business metric you just created to use for allocation.

Step 3: Select an Output Cost Filter​

Select the Vantage costs that will be split based on the percentages calculated in your business metric. In this case, you select a filter to show costs for the specific Namespace you want to be allocated.

A sample Tag Value field for specific Kubernetes namespace costs

Once the tag is created, create a new Cost Report and add the following criteria:

  • Create a filter for the specific Namespace.
  • Add grouping criteria to group by your new business metrics-based dynamic allocation tag.

The resulting report shows how much of the Namespace costs each team is allocated.

A sample Tag Value field for AWS Support Fee costs

Tagging Untaggable Resources in AWS Example​

While you can apply cost and metadata tags in AWS to many resources, there are many other resources that are untaggable in AWS. Therefore, it is hard, if not almost impossible, to achieve 100% allocation in AWS alone. One quick way to first get an inventory of all untagged resources in Vantage—regardless of if they are untaggable—is to create a Cost Report with the following filters:

  • Provider is AWS
  • Where Not Tagged with Any Key
Untagged cost filters

Then, add grouping criteria for Service and Category to get a view of the types of resources that are currently untagged. If these resources are taggable in AWS, you can add cost allocation tags there and see those tags represented in Vantage when you filter or group by specific tag.

info

See the AWS documentation for more information on what you can tag directly in AWS.

Untagged cost filters

Many services and resource categories, however, cannot be tagged in AWS. You can use Virtual Tags to create tags in Vantage for these untaggable resources. In the table below, the Vantage Resource Filters column represents the filters you can set as the Output Cost Filters in the Virtual Tag configuration.

For example, if you want to tag S3 Data Transfer for specific resources, you could use the following filter criteria.

Untagged cost filters
AWS ResourceDescriptionVantage Resource Filters
Elastic IPsAccording to AWS, "You can tag an Elastic IP address that's allocated for use in a VPC, however, cost allocation tags are not supported."Provider: AWS

Subcategory: Amazon Virtual Private Cloud contains inuse
CloudWatch MetricsCloudWatch Metrics involve performance data from AWS services, which are not taggable and are used for monitoring and alerting.Provider: AWS

Category: AmazonCloudWatch is Metric

Further filter by resource ID
S3 Data TransferData transferred in and out of S3 buckets, which is tracked but not taggable.Provider: AWS

Category: Amazon Simple Storage Service is Data Transfer

Further filter by resource ID
QuickSight resourcesResources within Amazon QuickSight, such as dashboards and analyses, which do not support tagging.Provider: AWS

Service: Amazon Quicksight

Optional detailed filters for Category (e.g., Business Analytics) or individual resource ID
CloudSearch resourcesAmazon CloudSearch domains and their configurations, which are untaggable.Provider: AWS

Service: Amazon CloudSearch

Optional detailed filters for Category (e.g., Data Transfer, Search Instance) or individual resource ID
EBS Snapshot CopyAmazon EBS Snapshots that are copied between regions for Disaster Recovery or restore purposesProvider: AWS

Service: Amazon Elastic Block Storage (EBS)

Category: Storage Snapshot

Further filter for resource ID
- + \ No newline at end of file diff --git a/vql/index.html b/vql/index.html index 59ab1a91..f11ff78f 100644 --- a/vql/index.html +++ b/vql/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

VQL (Vantage Query Language)

The Vantage Query Language (VQL) is a SQL-like language for filtering cloud cost data. It includes a normalized schema across cloud providers and basic filter syntax for creating complex filters. VQL is currently available as part of the Vantage API as well as within the Vantage Terraform provider.

tip

On Cost and Resource Reports, you can create a filter and click View as VQL to see the filter represented in VQL.

Show as VQL button on a Cost Report
  • API. On supported endpoints, such as /cost_reports and /resource_reports, you can use VQL in the filter parameter to programmatically create and fetch Cost Reports.
  • Terraform provider. In supported Terraform resources, such as vantage_saved_filter or vantage_cost_report, you can use VQL for the filter argument to create filtered Cost Reports or saved filters.

The below examples show how to use VQL on both the API and the Terraform provider. This example creates a saved filter in your Vantage account using VQL.

curl --request POST \
     --url https://api.vantage.sh/v2/saved_filters \
     --header 'content-type: application/json' \
     --header 'authorization: Bearer <ACCESS_TOKEN>' \
     --data @- <<EOF
{
  "filter": "(costs.provider = 'aws' AND costs.service = 'Amazon Relational Database Service') OR (costs.provider = 'kubernetes')",
  "title": "RDS and Kubernetes",
  "workspace_token": "wrkspc_abcde12345"
}
EOF

Key Concepts​

VQL is based on the following key concepts, further described in subsequent sections.

VQL uses a schema that organizes filters into namespaces. These namespaces comprise various fields that you can leverage to filter and retrieve specific cost-related data.

Scopes​

VQL has a separate scope for each type of report—meaning that you cannot use VQL statements for Cost Reports when querying Resource Reports. See the following pages below to learn more about each VQL scope.

- + \ No newline at end of file diff --git a/vql_cost_report/index.html b/vql_cost_report/index.html index 0d806ea4..a65f6f31 100644 --- a/vql_cost_report/index.html +++ b/vql_cost_report/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

VQL for Cost Reports

This page describes how to use VQL when querying Cost Reports in API or using the Terraform Provider.

Cost Reports VQL Schema​

VQL comprises two namespaces: costs and tags, which represent the available filters on Cost Reports in the Vantage console. To reference a filter, use the following syntax: namespace.field (e.g., costs.provider or tags.name).

NamespaceFieldVQL Example
costsproviderProviders example
allocationCost allocation example
regionRegion example
marketplaceMarketplace example
account_idAccount ID example
provider_account_idProvider account ID example
serviceService example
categoryCategory example
subcategorySubcategory example
resource_idResource example
charge_typeCharge Type example
tagsname
value
note

Availability of the fields listed above varies among different cloud providers. For a comprehensive list of available fields per provider, see the Data Dictionary.

Keywords​

VQL includes a set of keywords to create complex filter conditions. These keywords function similar to their SQL equivalents.

KeywordDescriptionVQL SampleExplanation
ANDLogical AND operatorcosts.provider = 'aws' AND costs.service = 'EC2'This example filters AWS costs for the EC2 service, where both conditions must be true.
ORLogical OR operatorcosts.provider = 'azure' OR costs.provider = 'aws'This example retrieves costs from either Azure or AWS. At least one condition must be true.
INUsed to compare against an array listcosts.provider = 'azure' AND costs.account_id IN ('account-1', 'account-2')This example filters based on a list of account IDs, returning data for the specified accounts

You can also use IN along with a special syntax for filtering by multiple tags. See Filter by Multiple Tags for details.
LIKEPerforms string comparisonscosts.provider = 'gcp' AND tags.name = 'environment' AND tags.value LIKE '%prod%'This example selects data where the tag value contains prod, such as production-1.
Note that at this time, LIKE is not compatible with costs.account_id, costs.provider_account_id, costs.region, and costs.service.
NOTRepresents negationcosts.provider = 'aws' AND costs.region NOT IN ('us-east-1', 'us-east-2')This example filters out data from both specified regions, providing all AWS costs not in these regions. Use NOT IN to specify a list of single or multiple values.

You can also use the != or <> operators for "is not."

costs.provider = 'aws' AND costs.region != 'us-east-1'

You can use NOT LIKE to perform string comparisons:

costs.provider = 'gcp' AND tags.name = 'environment' AND tags.value NOT LIKE '%prod%'

With these keywords, you can construct complex filter conditions in VQL, providing flexibility and precision when querying and analyzing cloud cost data.

Syntax​

You can think of VQL in its current iteration as the WHERE clause of a SQL query. By combining the schema and keywords above with parentheses, you can form complex filter operations, such as:

costs.provider = 'mongo' AND costs.allocation = 1.0 AND (costs.service = 'REALM' AND costs.resource_id IN ('s3')) OR (costs.provider = 'aws' AND costs.allocation = 1.0 AND costs.account_id IN ('123456798'))

VQL Examples​

The following examples cover common use cases for VQL.

Combining Providers​

note

To reference a Custom Provider in VQL queries, navigate to the Integrations page. Use the displayed Provider ID (e.g., custom_provider:accss_crdntl_123a45bfdaf38765).

Filter for provider costs associated with either MongoDB Atlas or AWS.

costs.provider = 'mongo' OR costs.provider = 'aws'

Cost Allocation​

Set cost allocation to 0.5.

costs.provider = 'gcp' AND costs.allocation = 0.5

Costs from a List of Regions​

Filter for Snowflake costs in two regions. Note that you will need to use the region code, such as us-east-1 in the case of AWS, or AWS_US_EAST_1 in the case of Snowflake, below.

costs.provider = 'snowflake' AND costs.region IN ('AWS_US_EAST_1', 'AWS_US_EAST_2')

Get Marketplace Transactions​

Retrieve costs associated with the AWS Marketplace.

costs.provider = 'aws' AND costs.marketplace = true

Costs by Account ID​

Costs for a specific set of services and account ID.

costs.provider = 'aws' AND costs.account_id = '123456758' AND costs.service IN ('Amazon Relational Database', 'Amazon Elastic Compute Cloud - Compute')

Costs by Provider Account ID​

The following example represents costs from a specific AWS billing account or costs from a specific Azure subscription.

(costs.provider = 'aws' AND costs.provider_account_id = 'abcd1234') OR (costs.provider = 'azure' AND costs.provider_account_id = 'abcd1234')

Per-Resource Costs and Costs by Service​

Resource costs require both provider and service in addition to the resource_id.

costs.provider = 'aws' AND costs.service = 'Amazon Relational Database Service' AND costs.resource_id = 'arn:aws:rds:us-east-1:123456789:db:primary-01'

Multiple Resource IDs​

costs.provider = 'aws' AND costs.service = 'Amazon Relational Database Service' AND costs.resource_id IN ('arn:aws:rds:us-east-1:123456789:db:primary-01', 'arn:aws:rds:us-east-1:123456789:db:primary-02')

Costs by Specific Category​

Filter costs to see a specific cost category. Category costs require both provider and service as well as category.

costs.provider = 'fastly' AND costs.service = 'CDN' AND costs.category = 'Data Transfer'

Costs by Specific Subcategory​

Filter costs by a specific service and subcategory. Subcategory costs require both provider and service as well as subcategory.

costs.provider = 'aws' AND costs.service = 'AWS Certificate Manager' AND costs.subcategory = 'USE1-PaidPrivateCA'

Cost by Charge Type​

Filter costs by a specific charge type.

costs.provider = 'aws' AND costs.charge_type = 'Usage'

Filter by Tag​

Filter by Single Tag​

Filter costs based on a specific tag, such as environment, with the value production, in AWS.

costs.provider = 'aws' AND tags.name = 'environment' AND tags.value = 'production'

Filter for Multiple Values from a Single Tag Key​

If you want to filter for multiple tag values that are tied to one tag key (e.g., costs tagged with the team tag of mobile and data), use the below syntax.

costs.provider = 'aws' AND tags.name = 'team' AND tags.value IN ('mobile', 'data')

Filter by Multiple Tags​

If you want to filter for resources that have more than one tag associated, you can use the syntax shown in the example below.

costs.provider = 'aws' AND (tags.name, tags.value) IN (('environment', 'staging'), ('team', 'engineering'))

This example filters for resources that are tagged with the environment tag with a value of staging as well as the team tag with a value of engineering. This filter is the same as creating the following manual filter in the console.

Filter by multiple tags in the console

Filter for Matching Tags Using LIKE​

costs.provider = 'azure' AND tags.name = 'environment' AND tags.value LIKE '%prod%'

Filter for Untagged Resources​

On providers that have a Not Tagged/Not Labeled filter option in the console, you can use the below VQL to see untagged resources. This example looks for untagged resources in a multi-cloud environment.

(costs.provider = 'aws' AND tags.name = NULL) OR (costs.provider = 'azure' AND tags.name = NULL) OR (costs.provider = 'gcp' AND tags.name = NULL)

Troubleshooting​

If you are receiving an error when trying to complete a query, check the following troubleshooting tips below.

  • Each provider exposes certain names to the API. Those names are normalized within the schema. Check the Data Dictionary for normalized field names.

  • Query parameter values should be wrapped in single quotes.

    Click to view examples
    This works
    costs.provider='aws'
    This does not work
    costs.provider="aws"

  • Currently, there is a limitation where AND and OR are not supported together in a single "query group."

    Click to view examples
    This works
    (costs.provider = 'aws' AND tags.name = 'environment' AND tags.value = 'dev') OR (costs.provider = 'aws' AND tags.name = 'environment' AND tags.value = 'prod')
    This does not work
    costs.provider = 'aws' AND ((tags.name = 'environment' AND tags.value = 'dev') OR (tags.name = 'environment' AND tags.value = 'prod'))

  • The costs.provider field is required on every call.

    Click to view examples
    This works
    costs.provider = 'fastly' AND costs.service = 'CDN'
    This does not work
    costs.service = 'CDN'

  • Resource costs require both provider and service in addition to the resource ID.

    Click to view examples
    This works
    costs.provider = 'aws' AND costs.service = 'Amazon Relational Database Service' AND costs.resource_id = 'arn:aws:rds:us-east-1:123456789:db:primary-01'
    This does not work
    costs.provider = 'aws' AND costs.resource_id = 'arn:aws:rds:us-east-1:123456789:db:primary-01'

  • Category and subcategory costs also require provider and service.

    Click to view examples
    These work
    costs.provider = 'fastly' AND costs.service = 'CDN' AND costs.category = 'Data Transfer'
    costs.provider = 'aws' AND costs.service = 'AWS Certificate Manager' AND costs.subcategory = 'USE1-PaidPrivateCA'
    These do not work
    costs.provider = 'fastly' AND costs.category = 'Data Transfer'
    costs.provider = 'aws' AND costs.subcategory = 'USE1-PaidPrivateCA'
- + \ No newline at end of file diff --git a/vql_resource_report/index.html b/vql_resource_report/index.html index a55ae9f3..cbfcd59f 100644 --- a/vql_resource_report/index.html +++ b/vql_resource_report/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

VQL for Resource Reports

This page describes how to use VQL when querying Resource Reports in API or using the Terraform Provider.

tip

If you need help constructing a VQL query, navigate to the Resource Reports page and click New Resource Report. From the top left, open the Filters menu. Create a filter and click the View as VQL button at the top of the Filters menu to see a filter's VQL representation. You can copy this syntax to use within your API calls.

Resource Reports VQL Schema​

VQL for Resources Reports comprises two namespaces: resources and tags, which represent the available filters on Resource Reports in the Vantage console. To reference a filter, use the following syntax: namespace.field (e.g., resources.region or tags.name). The following fields are available within these namespaces.

NamespaceFieldVQL Example
resourcesproviderProviders example
regionRegion example
account_idAccount example
provider_account_idBilling Account example
typeResource Type example
labelLabel example
uuidUUID (AWS ARN) example
metadataMetadata example
tagsname
value
note

Availability of the fields listed above varies among different cloud providers. See the Resource Reports documentation for a full list of filter fields available per provider.

Keywords​

VQL includes a set of keywords to create complex filter conditions. These keywords function similar to their SQL equivalents.

KeywordDescriptionVQL SampleExplanation
ANDLogical AND operatorresources.provider = 'aws' AND resources.label = '123456'This example filters AWS resources, with a specific associated label, where both conditions must be true.
ORLogical OR operator(resources.provider = 'aws') OR (resources.provider = 'gcp')This example retrieves resources from either AWS or GCP. At least one condition must be true.
LIKE and NOT LIKEPerforms string comparisonsresources.provider = 'aws' AND resources.uuid LIKE '%arn:aws:s3:::my-bucket%''This example selects data where the resource ARN contains arn:aws:s3:::my-bucket, such as arn:aws:s3:::my-bucket-123.

This same query also works for NOT LIKE where data does not contain a particular string: resources.provider = 'aws' AND resources.uuid NOT LIKE '%arn:aws:s3:::my-bucket%'.
!=Represents negation, "is not"resources.provider = 'azure' AND (resources.type != 'azurerm_public_ip' AND resources.type != 'azurerm_kubernetes_cluster')This example filters out data from two specified resource types, providing all Azure resources that are not these types.
<, >, <=, >=Mathematical operators for numerical queriesresources.provider = 'azure' AND (resources.type = 'azurerm_virtual_machine' AND resources.metadata->>'virtual_machine_size' > '7')This example looks for Virtual Machines that have a size greater than 7.
->>This operator is used only when constructing queries related to metadataresources.provider = 'aws' AND (resources.type = 'aws_instance' AND resources.metadata->>'architecture' = 'x86_64')This example looks for EC2 instances with an architecture of x86_64.

With these operators and keywords, you can construct complex filter conditions in VQL.

VQL Examples​

The following examples cover common use cases for VQL.

Combining Providers​

Filter for provider resources associated with either AWS or GCP.

(resources.provider = 'aws') OR (resources.provider = 'gcp')

Costs from a List of Regions​

Filter for AWS costs in two regions. Note that you will need to use the region code, such as us-east-1.

resources.provider = 'aws' AND (resources.region = 'us-east-1' OR resources.region = 'us-west-1')

Costs by Account ID​

Costs for a specific set of resource types and account ID.

resources.provider = 'gcp' AND (resources.account_id = 'user-proj-1234') AND (resources.type = 'google_compute_disk' OR resources.type = 'google_compute_instance')

Costs by Billing Account​

Costs for a specific billing account.

resources.provider = 'aws' AND (resources.provider_account_id = '11111111111')

Costs by Resource Type​

Filter costs to see a specific resource type. In the example below, the query is looking for any AWS resource that is not an AWS CloudFront Distribution. Resource types are represented like aws_cloudfront_distribution. Expand the box below for a list of all available resource types and their VQL equivalents.

resources.provider = 'aws' AND (resources.type != 'aws_cloudfront_distribution')
Resource Type VQL Representations
ProviderVQL RepresentationFriendly Name
AWSaws_batch_job_definitionBatch Job Definition
AWSaws_mq_brokerMQ Broker
AWSaws_cloudfront_distributionCloudFront Distribution
AWSaws_cloudtrailCloudTrail
AWSaws_codebuild_projectCodeBuild Project
AWSaws_codepipelineCodePipeline
AWSaws_config_config_ruleConfig Rule
AWSaws_ecr_repositoryECR Repository
AWSaws_ecs_serviceECS Service
AWSaws_docdb_cluster_instanceDocumentDB Cluster Instance
AWSaws_route53_zoneRoute 53 Zone
AWSaws_dynamodb_tableDynamoDB Table
AWSaws_ec2_reserved_instanceEC2 Reserved Instance
AWSaws_eks_clusterEKS Cluster
AWSaws_elasticache_clusterElastiCache Cluster
AWSaws_efs_file_systemEFS File System
AWSaws_elasticsearch_domainElasticsearch Domain
AWSaws_lambda_functionLambda Function
AWSaws_glacier_vaultGlacier Vault
AWSaws_globalaccelerator_acceleratorGlobal Accelerator
AWSaws_glue_jobGlue Job
AWSaws_internet_gatewayInternet Gateway
AWSaws_eipElastic IP
AWSaws_msk_clusterMSK Cluster
AWSaws_kms_keyKMS Key
AWSaws_lbLoad Balancer
AWSaws_cloudwatch_log_groupCloudWatch Log Group
AWSaws_mediaconnect_flowMediaConnect Flow
AWSaws_mediaconvert_jobMediaConvert Job
AWSaws_medialive_channelMediaLive Channel
AWSaws_media_package_channelMediaPackage Channel
AWSaws_media_package_vod_assetMediaPackage VOD Asset
AWSaws_media_store_containerMediaStore Container
AWSaws_media_tailor_channelMediaTailor Channel
AWSaws_media_tailor_playback_configurationMediaTailor Playback Configuration
AWSaws_nat_gatewayNAT Gateway
AWSaws_network_interfaceNetwork Interface
AWSaws_outposts_outpostOutposts Outpost
AWSaws_ec2_managed_prefix_listEC2 Managed Prefix List
AWSaws_db_instanceRDS Instance
AWSaws_rds_reserved_instanceRDS Reserved Instance
AWSaws_db_snapshotRDS Snapshot
AWSaws_redshift_clusterRedshift Cluster
AWSaws_route53_resolver_query_log_configRoute 53 Resolver Query Log Config
AWSaws_route_tableRoute Table
AWSaws_s3_bucketS3 Bucket
AWSaws_sagemaker_modelSageMaker Model
AWSaws_savings_planSavings Plan
AWSaws_secretsmanager_secretSecrets Manager Secret
AWSaws_sns_topicSNS Topic
AWSaws_sqs_queueSQS Queue
AWSaws_subnetSubnet
AWSaws_ecs_task_definitionECS Task Definition
AWSaws_transfer_serverTransfer Server
AWSaws_ec2_transit_gatewayEC2 Transit Gateway
AWSaws_instanceEC2 Instance
AWSaws_instance_snapshotEC2 Instance Snapshot
AWSaws_ebs_volumeEBS Volume
AWSaws_vpcVPC
AWSaws_vpc_endpointVPC Endpoint
AWSaws_flow_logFlow Log
AWSaws_vpc_peering_connectionVPC Peering Connection
AWSaws_vpn_gatewayVPN Gateway
AWSaws_wafv2_web_aclWAFv2 Web ACL
AWSaws_workspaces_workspaceWorkSpaces Workspace
Azureazurerm_application_gatewayApplication Gateway
Azureazurerm_application_insightsApplication Insights
Azureazurerm_app_service_planApp Service Plan
Azureazurerm_firewallFirewall
Azureazurerm_snapshotSnapshot
Azureazurerm_container_registryContainer Registry
Azureazurerm_cosmosdb_accountCosmosDB Account
Azureazurerm_databricks_workspaceDatabricks Workspace
Azureazurerm_managed_diskManaged Disk
Azureazurerm_dns_zoneDNS Zone
Azureazurerm_sql_elasticpoolSQL Elastic Pool
Azureazurerm_express_route_circuitExpressRoute Circuit
Azureazurerm_lbLoad Balancer
Azureazurerm_log_analytics_workspaceLog Analytics Workspace
Azureazurerm_logic_app_workflowLogic App Workflow
Azureazurerm_kubernetes_clusterKubernetes Cluster
Azureazurerm_nat_gatewayNAT Gateway
Azureazurerm_postgresql_flexible_serverPostgreSQL Flexible Server
Azureazurerm_postgresql_serverPostgreSQL Server
Azureazurerm_powerbi_dedicated_capacityPower BI Dedicated Capacity
Azureazurerm_private_endpointPrivate Endpoint
Azureazurerm_public_ipPublic IP
Azureazurerm_recovery_services_vaultRecovery Services Vault
Azureazurerm_redis_cacheRedis Cache
Azureazurerm_security_center_pricingSecurity Center Pricing
Azureazurerm_sql_databaseSQL Database
Azureazurerm_sql_managed_instanceSQL Managed Instance
Azureazurerm_storage_accountStorage Account
Azureazurerm_synapse_workspaceSynapse Workspace
Azureazurerm_virtual_machineVirtual Machine
Azureazurerm_virtual_machine_scale_setVirtual Machine Scale Set
Azureazurerm_virtual_network_gatewayVirtual Network Gateway
Googlegoogle_alloydb_backupAlloyDB Backup
Googlegoogle_alloydb_clusterAlloyDB Cluster
Googlegoogle_alloydb_instanceAlloyDB Instance
Googlegoogle_app_engine_serviceApp Engine Service
Googlegoogle_bigquery_datasetBigQuery Dataset
Googlegoogle_bigtable_instanceBigtable Instance
Googlegoogle_compute_diskCompute Disk
Googlegoogle_compute_instanceCompute Instance
Googlegoogle_container_clusterContainer Cluster
Googlegoogle_dataflow_jobDataflow Job
Googlegoogle_firestore_databaseFirestore Database
Googlegoogle_cloudfunctions_functionCloud Functions Function
Googlegoogle_logging_project_bucket_configLogging Project Bucket Config
Googlegoogle_redis_instanceRedis Instance
Googlegoogle_cloud_run_serviceCloud Run Service
Googlegoogle_secret_manager_secretSecret Manager Secret
Googlegoogle_spanner_instanceSpanner Instance
Googlegoogle_sql_database_instanceSQL Database Instance
Googlegoogle_storage_bucketStorage Bucket

Costs by Label​

Resource costs by specific label.

resources.provider = 'aws' AND resources.label = '123456'

Costs for Specific ARN​

The UUID is the unique identifier for the resource. In the case of AWS resources, this is the ARN. The below example shows a query for resources that contain specific text within the ARN.

resources.provider = 'aws' AND resources.uuid LIKE '%arn:aws:s3:::my-bucket%'

Resource Metadata Costs​

Resource metadata costs require both provider and type as well as metadata. Metadata uses a specific syntax (e.g., resources.metadata->>'domain' = 'vantage.sh').

resources.provider = 'aws' AND (resources.type = 'aws_cloudfront_distribution' AND resources.metadata->>'domain' = 'vantage.sh')

Filter by Tag​

Filter resources based on a specific tag, such as terraform, with the value true, in AWS.

resources.provider = 'aws' AND (tags.name = 'terraform' AND tags.value = 'true')

Filter for Untagged Resources​

On providers that have a Not Tagged filter option in the console, you can use the below VQL to see untagged resources. This example looks for untagged resources in a multi-cloud environment.

resources.provider = 'gcp' AND tags.name = NULL) OR (resources.provider = 'aws' AND tags.name = NULL
- + \ No newline at end of file diff --git a/workspaces/index.html b/workspaces/index.html index 13aa756c..0d1c8db0 100644 --- a/workspaces/index.html +++ b/workspaces/index.html @@ -10,7 +10,7 @@ - + @@ -20,7 +20,7 @@

Workspaces

In Vantage, a workspace is a way to separate your provider integrations into distinct cost views. Teams can use workspaces to create focused views of costs and even restrict access to costs within each workspace using Role-Based Access Controls (RBAC) (Enterprise customers). You can specify which integrations are available in which workspaces. Some use cases for workspaces are listed below.

  • You may have multiple accounts within the same cloud provider, such as Azure or AWS. You can use a single Vantage workspace to ingest costs for all these accounts into the same view.
  • Create a distinct Vantage workspace for each of your environments, such as Production, Staging, and Development. Then, specify which provider accounts are associated with which workspace. For example, a particular Datadog account may be associated with only your Development workspace.
  • If you manage multiple customers, you can create individual workspaces for each customer account (Customer A, Customer B, etc.). This allows you to separate and manage cost data for each customer independently. Then, you can connect only the corresponding integrations to each customer's workspace, ensuring that they have access only to their data and reports.
tip

To get started with workspaces and workspace integrations, you can also view a video demo on Vantage University 🎓.

If you have more than one workspace in your Vantage account, the Workspaces menu is displayed on the top left of the console. You can select any of the listed workspaces to move between each workspace.

Create a Workspace​

When your Vantage account is created, you are assigned a Default workspace. You can create other workspaces in addition to the default workspace. To create a new workspace, complete the following steps:

  1. From the top navigation menu, click Settings.
  2. On the left navigation, under General Settings, click Workspaces.
  3. Click Create a Workspace.
  4. Enter a Name for your new workspace (e.g., Management), then click Create.

Manage Workspaces​

All your existing workspaces are displayed on the Workspaces Settings screen. Select a listed workspace to view additional details, such as:

  • Turn off Active Resource Syncing. Turn off automatic syncing if you do not want Vantage to be automatically pulling active resource details from your account. This option is useful if you find Vantage is making too many API calls to your AWS endpoints.
  • View team workspace access. See the Role-Based Access Control documentation for more information about teams.
  • View configuration details for the workspace, including the workspace token, which is used as the workspace identifier in API calls.
  • Delete the workspace.
    danger

    Note that this action is not reversible.

Manage Workspace Provider Integrations​

Once you connect a cloud provider to Vantage, and costs are fully imported, you'll need to specify the workspaces where this integration should be accessible for creating reports and viewing costs. To manage the workspaces associated with an integration:

  1. From the top navigation, click Settings.
  2. From the left navigation, click Integrations.
  3. All your provider integrations are displayed. Click the settings icon (looks like a wheel) next to an integration (e.g., Fastly) in the list.
  4. The provider's integration page is displayed. Click the settings icon next to a listed account.
  5. The Manage Connection page is displayed. Under Workspace Access, select or deselect the checkbox next to a listed workspace to specify which workspaces the integration is associated with.

In the below example, the Fastly integration is only available in the Demo Accounts workspace. If you navigate to the Management or Marketing workspace, you'll be unable to view Fastly cost data in Cost Reports or other Vantage features.

The integration workspace is displayed with an arrow pointing from the settings icon. The arrow points to the integration screen with another arrow point from the settings icon. That arrow points to the specific integration and the Workspace access section.
- + \ No newline at end of file