<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jimit Rangras on Medium]]></title>
        <description><![CDATA[Stories by Jimit Rangras on Medium]]></description>
        <link>https://medium.com/@rangrasjimit?source=rss-29fe7447339b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eMNfnA1U6s2xFyrJCw6zjg.png</url>
            <title>Stories by Jimit Rangras on Medium</title>
            <link>https://medium.com/@rangrasjimit?source=rss-29fe7447339b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 16:40:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rangrasjimit/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Getting Started with FinOps on Google Cloud]]></title>
            <link>https://medium.com/google-cloud/getting-started-with-finops-on-google-cloud-de6682f9e6af?source=rss-29fe7447339b------2</link>
            <guid isPermaLink="false">https://medium.com/p/de6682f9e6af</guid>
            <category><![CDATA[cloud-cost-management]]></category>
            <category><![CDATA[cost-optimization]]></category>
            <category><![CDATA[google-cloud]]></category>
            <category><![CDATA[finops]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Jimit Rangras]]></dc:creator>
            <pubDate>Mon, 17 Apr 2023 04:35:36 GMT</pubDate>
            <atom:updated>2023-04-17T11:46:01.160Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vn9ZsIUf1liAE-10" /><figcaption>Photo by <a href="https://unsplash.com/@lightscape?utm_source=medium&amp;utm_medium=referral">Lightscape</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>FinOps is on top of mind of pretty much every Enterprise working towards their Cloud Transformation journey and cloud teams are more focused than ever in leveraging the full potential of the public cloud in best way possible but before we dive into that….. what is FinOps anyway that you keep hearing about it so much these days?</p><p>Here’s how the FinOps Foundation defines it:</p><blockquote>FinOps is an evolving cloud financial management discipline and cultural practice that enables organizations to get maximum business value by helping engineering, finance, technology and business teams to collaborate on data-driven spending decisions.</blockquote><blockquote>Source: <a href="https://www.finops.org/introduction/what-is-finops/">FinOps Foundation Website</a></blockquote><p>A bit of historical context around FinOps is when organizations started moving to cloud rapidly and started interacting the old methods don’t work as we move forward as Cloud cost nature is more on the Opex side of things and this variable cost nature pushes the boundary of procurement teams and something new is required to operate at scale here.</p><p>FinOps essentially provides a framework that brings financial accountability to the spend in cloud as it gets Finance, Tech and leadership teams same language of communicating so that there can be better accountability of costs on an ongoing basis thereby allowing teams to leverage the agile and elastic nature of cloud to experiment and innovate at a faster pace.</p><p>FinOps in a concept is very much similar to DevOps and essentially comes from combination of words Finance + DevOps = FinOps, which fosters better collaboration and communication between different teams within the organization. This practice is also known with some other names such as Cloud Cost Management, Cloud Finance Engineering, Cloud Cost Optimization, Cloud Finance Management, etc.</p><figure><img alt="Overview of FinOps Framework" src="https://cdn-images-1.medium.com/max/1000/0*3JXgJ3yWSIi-ni5P.png" /><figcaption>Source: <a href="https://www.finops.org/introduction/what-is-finops/">FinOps Foundation Website</a></figcaption></figure><p>FinOps Framework essentially proposes three epics as it’s guiding principle to put it into practice i.e. Inform, Optimize and Operate which is an iterative and an ongoing process, you don’t need to wait and be perfect in each of these phases to move forward rather you can get started in crawl phase and then iterate on it to get better over time. It also suggests various personas who would be revolving around the FinOps operating model to put together some structure and accountability within the teams.</p><p>Key is to start with the Inform phase which focuses on visibility and allocation of the costs with mapping of workloads / applications within cloud vs which teams do they map to and who owns them and we will drill down into this in a bit, once you can good amount of visibility into your costs then you can look for opportunities to optimize them by leveraging various Cost Optimization techniques and operate phase focuses on maintaining these processes and continuously improve with Financial management and optimization to enable your organization to allocate the saved costs into fostering more innovation and exploring new areas with Cloud.</p><p>Now we will dig deep into what all tools &amp; techniques that we can leverage to get started with FinOps on Google Cloud around these epics</p><h4>Billing Export to BigQuery</h4><p>If not done already, first recommend step is to enable the Standard and Detailed Billing export to BigQuery within your Google Cloud Organization, once you do this it will start exporting all your billing data into the BigQuery datasets specified and all that data will be available to you for future analysis, timing is very important for enabling this export as the billing data in BigQuery is only available from the moment you turn on the Billing Export hence it is recommended to perform this as early as possible. Here’s a <a href="https://cloud.google.com/billing/docs/how-to/export-data-bigquery#setup"><strong>guide</strong></a> on how to enable the billing export.</p><h4>Setup a Looker Studio Dashboard to Visualize Costs</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JqOUrJBwLmCeXS7K.png" /><figcaption>Source: <a href="https://cloud.google.com/billing/docs/how-to/visualize-data">Looker Studio Dashboard Sample from Google Cloud Documentation</a></figcaption></figure><p>While Billing export allows you to gather the data into BigQuery Billing datasets the next step is to visualize that information once it has been collected overtime for better visibility into your cloud spend thereby giving accountability and visibility into cloud spend to the individual teams for their workloads on an ongoing basis. Our team members at Google Cloud have crafted a bespoke Looker Studio Dashboard that you can setup for your organization which takes data from the BigQuery Billing Export standard and detailed usage datasets &amp; tables to showcase your cloud spend and help you visualize it. Moreover once the dashboard has been setup it can be customized by adding new pages / views / visualizations to better suite your reporting requirements. Here’s a step by step <a href="https://cloud.google.com/billing/docs/how-to/visualize-data"><strong>guide</strong></a> on how to setup Looker Studio Dashboard to Visualize your Google Cloud Costs</p><h4>Apply Labels on Resources</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LYyCSBKB_mX_UOsWHlTSkg.png" /><figcaption>Source: <a href="https://cloud.google.com/blog/topics/cost-management/use-labels-to-gain-visibility-into-gcp-resource-usage-and-spending">Google Cloud Blog</a></figcaption></figure><p>Establishing a robust labeling strategy is very important when it comes to getting more and deeper visibility into your cloud costs, labels in Google Cloud are key-value pairs that can be applied across the resource hierarchy either on the project level or on the resource level and it helps you keep track of resources as the information about labels is forwarded into billing systems and can be used to extract drill down into the costs associated with those labels. Some of the examples of labels is as follows:</p><pre>&quot;cost-center&quot;: &quot;example&quot;<br>&quot;team&quot;: &quot;research&quot;<br>&quot;application&quot;: &quot;sample-application&quot;<br>&quot;module&quot;: &quot;frontend&quot;<br>&quot;environment&quot;: &quot;prod&quot;</pre><p>Here’s a <a href="https://cloud.google.com/resource-manager/docs/creating-managing-labels#what-are-labels">guide</a> to creating and managing labels there are multiple ways to do the same, most preferred way is if you are leveraging an Infrastructure as Code (IaC) tool such as <a href="https://cloud.google.com/docs/terraform"><strong>terraform</strong></a> labeling strategy should be documented before hand and then applied into resources as they are created in Google Cloud using the respective IaC tool.</p><h4>Active Assist Recommendations</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m2sgH41NzTVn829a.png" /><figcaption>Active Assist Console View from <a href="https://cloud.google.com/recommender/docs/whatis-activeassist#:~:text=Active%20Assist%20refers%20to%20the,and%20insights%20and%20analysis%20tools.">Google Cloud Documentation</a></figcaption></figure><p>Above three techniques help you to get started with the <strong><em>Inform</em></strong> Epic from FinOps Framework and enables you to get visibility from your Google Cloud Costs. Active Assist is a set of tools which gives you intelligent recommendations around different areas such as</p><ul><li><strong>Identifying Idle VMs</strong> in Compute Engine based on the CPU Usage over time of those VMs and provide you with recommendations around shutting them down</li><li><strong>Committed Usage Discounts</strong> (CUDs) recommendations based on your workloads within Compute Engine. If you have a steady state workload then signing up for CUDS can help you save the price that you pay for Compute resources on Google Cloud, you can sign up for CUDs based on the CPU and Memory of Compute Engine VM Families in respective projects for either 1 year or 3 year commitment period and can give you discounts of upto 37% and 57% respectively on top of list price which can help you optimize your costs in long run. Learn More about CUDs pricing here in this <a href="https://cloud.google.com/compute/vm-instance-pricing#committed_use"><strong>documentation</strong></a><strong>. </strong>CUDs can be applied for other resources as well in addition to compute engine such as Cloud Spanner, Cloud SQL, Cloud Run, etc and there are different types of CUDs such as Resource Based and Spend Based Commits, learn more about different types of CUDs and see which one would be a fit for you in detail <a href="https://cloud.google.com/docs/cuds"><strong>here</strong></a><strong>.</strong></li></ul><p>On top of cost optimization related recommendations Active Assist gives you other recommendations as well such as fixing IAM permissions and increasing performance of your resources, etc. Leveraging Active Assist recommendations helps you get started with <strong><em>Optimize</em></strong> and <strong><em>Operate</em></strong> Epic by enabling you to optimize your spend costs with data driven recommendations around the resources being used in your Google Cloud Organization, learn more about Active Assist in detail <a href="https://cloud.google.com/recommender/docs/whatis-activeassist">here</a>.</p><p>These are the areas that can help you kickstart your FinOps journey on Google Cloud as you progress through your Cloud Transformation Journey if you’d like to get more deeper understanding about FinOps checkout this <a href="https://cloud.google.com/learn/what-is-finops">article</a>, I would highly recommend checking out <a href="https://cloud.google.com/resources/cloud-finops-whitepaper">Google Cloud FinOps Whitepaper</a> as well for more insights.</p><p><em>Thanks for taking the time to read this article, do let me know your thoughts on these insights in comments and feel free to ask questions in comments or share any other ideas that you’ve come across around FinOps and Cloud. Do share this article with others as well so that they can get started with their FinOps journey in Google Cloud.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de6682f9e6af" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/getting-started-with-finops-on-google-cloud-de6682f9e6af">Getting Started with FinOps on Google Cloud</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>