5 results found

1. CUD Expiry Report

   Hi, Can you create a GCP committed usage discount expiry report?

   20 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Planned  ·  1 comment  ·  Budgets & Alerts  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Need to track "grandfathered" customers who receive PE (Partner Escalation) on GCP without being charged.

   Request for a flag for legacy clients under "partner-led premium support" who receive Partner Escalation at no cost.

   We need to track "grandfathered" customers who receive PE (Partner Escalation) on GCP without being charged as a result of having a qualifying B2B agreement. A proposed solution involves creating dummy contracts in the console for these customers and adding a flag to identify grandfathered customers.

   Core Problem: Grandfathered customers receiving PE on GCP are not being charged, but there's no clear flag to indicate this, leading to confusion for CRE teams and auditors, as they are dependent on a PLPS contract to understand whether they can escalate to Google support. There are 2 types of customers eligible for escalation, those paying for PLPS and those receive a PLPS equivalent due to the timing of when they signed their agreement.

   Proposed Solution:
   Create Dummy Contracts: For all grandfathered customers, create a dummy contract in the console for PE on GCP.

   Add a Flag/Dropdown:
   Within this PE object (contract), add a dropdown or checkbox.

   Purpose:
   To indicate that this is a "grandfathered" or "legacy account."

   Auditing:
   This flag will explain to auditors why no charge is applied (0% fee).

   Match Contract Dates:
   Use the actual contract end dates for these dummy contracts.

   AM Nudge:
   When a dummy contract is within six months of expiration, it will automatically create opportunities to remind sales reps to re-upsell the customer to paid PLPS.
   CRE

   Tool Integration:
   CRE tools look at a PE contract to determine if a CRE can escalate to Google. Using a PE object, even a dummy one, would allow the CRE team to continue their normal process without needing to find a separate flag on the individual customer.

   Future Reuse:
   The flag field could potentially be reused for future versions of partner-led support (e.g., v1, v2).

   Requirements/Next Steps:
   Create a dummy contract in the console for grandfathered customers with PE on GCP.
   Add a flag (dropdown or checkbox) to these dummy contracts to indicate they are "grandfathered" or "legacy accounts," so auditors understand why no charge is applied.
   Ensure the PE object in the console allows for a dropdown to identify grandfathered customers, with dates matching their contract end and a 0% fee.
   Potentially reuse this field for future versions of partner-led support (e.g., v1, v2).

   Request for a flag for legacy clients under "partner-led premium support" who receive Partner Escalation at no cost.

   We need to track "grandfathered" customers who receive PE (Partner Escalation) on GCP without being charged as a result of having a qualifying B2B agreement. A proposed solution involves creating dummy contracts in the console for these customers and adding a flag to identify grandfathered customers.

   Core Problem: Grandfathered customers receiving PE on GCP are not being charged, but there's no clear flag to indicate this, leading to confusion for CRE teams and auditors, as they are dependent on a PLPS contract… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Billing & Invoicing  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Planned  ·  AdminDewey (Admin, DoiT) responded

   This is will be evaluated against our CP4 work loads.

3. Compare non-consecutive time periods in cloud analytics

   The customer—specifically the person responsible for FinOps—would like the ability to compare specific time periods while excluding everything in between. For example, they want to compare June 2024 vs. June 2025, or Q2 2024 vs. Q2 2025, without including the months in between.

   This is similar to the “this period vs. last month” view we currently offer, but they’re looking for a customizable comparison between non-consecutive timeframes—essentially, a way to isolate and break down specific months or quarters year over year.

   MoM, QoQ, or YoY

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Planned  ·  0 comments  ·  Cloud Analytics & Reports  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Split 'unallocated' costs by account

   Customers with shared resource accounts that need to be split amongst business units (or some other allocation) need to create allocations for those accounts and then do cost splitting. This can get tedious for large customers.

   Instead of requiring 100% coverage of allocations in order to do cost splitting, allow customers when using an allocation to split by account to re-allocate the costs for shared resources.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Planned  ·  0 comments  ·  Cloud Analytics & Reports  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Enable Attribution Groups in Alerts

   Today, I can't scope an Alert to an attribution group — only attributions. However, I think there's a compelling use case.

   If I create an attribution group "Engineering Team" I might want to set an alert that then monitors for each individual team in that Attribution Group with the optional "Evaluate for each" setting. Today I can't do that. Instead I have to create an alert for each attribution.

   Here's a video explaining my logic further. https://www.loom.com/share/9937b4dc51914bd08f9075b06c8e989c?sid=2e30b2b8-bbb1-438e-be58-610bb10bdc95

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Planned  ·  0 comments  ·  Attributions & Attribution Groups  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating