Skip to content

Commit cb919b6

Browse files
Merge pull request #22095 from newrelic/cci-nrql-update
K8S NRQL update for CCI
2 parents 6505cb6 + 9e8db72 commit cb919b6

File tree

1 file changed

+11
-2
lines changed

1 file changed

+11
-2
lines changed

src/content/docs/cci/financial-intelligence/nrql-for-cci.mdx

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Let us consider the following NRQL query to understand how to query your data fo
4343
title="CloudCost attributes"
4444
>
4545

46-
In New Relic, click **Integrations & Agents** on the left panel, locate and select **Cloud Cost Intelligence > Budgets**. Open the bottom Query Console drawer and enter the following NRQL query:
46+
In New Relic, navigate to **All Capabilities > CloudCost Intelligence**. Open the bottom Query Console drawer and enter the following NRQL query:
4747

4848
```sql
4949
FROM CloudCost SELECT * SINCE 24 hours ago
@@ -216,11 +216,20 @@ Let us consider the following NRQL query to understand how to query your data fo
216216
title="Kubernetes cost event type"
217217
>
218218

219-
In New Relic, click **Integrations & Agents** on the left panel, locate and select **Cloud Cost Intelligence > Budgets**. Open the bottom Query Console drawer and enter the following NRQL query:
219+
In New Relic, navigate to **All Capabilities > CloudCost Intelligence**. Open the bottom Query Console drawer and enter the following NRQL query:
220220

221221
```sql
222222
FROM KubernetesCost SELECT * SINCE 1 week ago
223223
```
224+
225+
To calculate accurate Kubernetes costs, multiply the `cpu_weightage + memory_weightage` parameters in your cost queries. The following example shows the correct query format:
226+
227+
```sql
228+
SELECT SUM(net_unblended_cost * (cpu_weightage + memory_weightage)) FROM KubernetesCost SINCE '2025-09-01' UNTIL '2025-09-10'
229+
```
230+
231+
This query multiplies the `net_unblended_cost` by the sum of CPU and memory weightage to provide accurate cost allocations based on resource usage.
232+
224233
<table>
225234
<tr>
226235
<th>

0 commit comments

Comments
 (0)