Skip to content

Commit e572ffd

Browse files
committed
docs: use 10e9, not 10e8, for GB Estimate calculation
@annettejanewilson actually deserves the credit for spotting this 😄 Unless the definition of bytes or `GB` is unusual, dividing by `10e8` doesn't seem right!
1 parent cb919b6 commit e572ffd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ The [usage UI](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new
6565
This query breaks down [Metric data](/docs/telemetry-data-platform/understand-data/new-relic-data-types/#dimensional-metrics) by the top ten metric names. You could also facet by `appName` or `host` to adjust the analysis.
6666

6767
```sql
68-
FROM Metric SELECT bytecountestimate()/10e8 AS 'GB Estimate'
68+
FROM Metric SELECT bytecountestimate()/10e9 AS 'GB Estimate'
6969
SINCE 24 hours ago
7070
FACET metricName LIMIT 10 TIMESERIES 1 hour
7171
```

0 commit comments

Comments
 (0)