Skip to content

docs: use 10e9, not 10e8, for GB Estimate calculation #22098

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
+1 −1
Open

docs: use 10e9, not 10e8, for GB Estimate calculation #22098

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...ccounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ The [usage UI](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new
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.

```sql
FROM Metric SELECT bytecountestimate()/10e8 AS 'GB Estimate'
FROM Metric SELECT bytecountestimate()/10e9 AS 'GB Estimate'
SINCE 24 hours ago
FACET metricName LIMIT 10 TIMESERIES 1 hour
```
Expand Down