Pricing
Metrics monitoring you pay for in credits - and can predict
A credit costs $0.001. A metric level costs 15 to 75 credits a month, 500 logs or 250 traces cost a credit - for each day they are kept - and you start with 10,000 free. You buy credits up front, so you can never be billed for more than you have chosen to buy.
What a metric costs
A metric is priced level by level - minute, hour, day, month and year - and the levels it keeps are added up. Each costs 15 to 75 credits a month (the finer the level, the more it holds and the more it costs) when kept for its default number of days - a short time for minutes, a long time for years. It is charged hourly, so a metric that exists for half the month costs half. So a metric kept at every level, for the defaults, is the sum of these (shown for a month):
| One level | Default retention | Credits a month | About |
|---|---|---|---|
| Minute level | 1 day | 75 credits | $0.075 |
| Hour level | 7 days | 30 credits | $0.03 |
| Day level | 30 days | 15 credits | $0.015 |
| Month level | 365 days | 15 credits | $0.015 |
| Year level | 3,650 days | 15 credits | $0.015 |
Keeping data longer
Everything costs in proportion to how long it is kept. Each level of a metric is priced in proportion to its default, so keeping a level twice as long costs twice as much (and half as long, half). For a metric kept down to the minute, with the other levels on their defaults, keeping the minutes:
| Minute-level metric, minutes kept | Credits a month | About |
|---|---|---|
| 1 day | 150 credits | $0.15 |
| 3 days | 300 credits | $0.30 |
| 7 days | 600 credits | $0.60 |
| 30 days | 2,325 credits | $2.325 |
- You choose how long on your account page - for logs and traces, and for the levels of new metrics - up to 365 days for logs and traces. Each metric can be set on its own
- A change applies to what arrives from then on: each log and trace is kept for the retention it arrived with
Distinct counts
Optional. A distinct count tells you how many different values a metric saw - the bigger the size you choose, the more it can count accurately. It multiplies the price of the level it is on (together with the multiplier for that level and the days it is kept). Shown here for a distinct count on the day level of a metric kept to day level, on default retention:
| Filter size | Different values (about) | Multiplier | Credits a month | About |
|---|---|---|---|---|
| 1 KB | 660 | ×2 | 60 credits | $0.06 |
| 8 KB | 5,300 | ×3 | 75 credits | $0.075 |
| 64 KB | 42,000 | ×4 | 90 credits | $0.09 |
| 512 KB | 340,000 | ×5 | 105 credits | $0.105 |
- Each level can have its own distinct count, and each is priced on its own - a filter on the day level adds nothing to the month or year level
Logs and traces
Charged for each day they are kept - so the same logs kept 7 days cost 7 times as much as kept 1 day:
- 500 logs cost 1 credit a day kept ($0.000002 each, kept 1 day)
- 250 traces cost 1 credit a day kept ($0.000004 each, kept 1 day) - a trace is a root trace, with its child spans
Examples
Worked out from the current prices, for a month:
| What you use | Credits | About |
|---|---|---|
| 1 metric kept to year -> day level | 45 credits | $0.045 |
| 1 metric kept to year -> minute level | 150 credits | $0.15 |
| 20 metrics kept to year -> day level | 900 credits | $0.90 |
| 10,000 logs a day, kept 1 day | 600 credits | $0.60 |
| 10,000 logs a day, kept 7 days | 4,200 credits | $4.20 |
| 1,000 traces a day, kept 1 day | 120 credits | $0.12 |
| 1,000 traces a day, kept 7 days | 840 credits | $0.84 |
| A small app: 20 day-level metrics with 1,000 logs and 100 traces a day | 972 credits | $0.972 |
Free credits
A new account starts with 10,000 credits (1,000 for a guest account, which is deleted after 24 hours and cannot buy more).
Buying credits
- Buy a pack with a one-off card payment, whenever you like: 5,000 credits - $5.00; 10,000 credits - $10.00; 25,000 credits - $25.00; 50,000 credits - $50.00
- Credits don't expire, and nothing is ever charged to your card automatically
- What you have stored is counted every hour and taken from your balance (rounded down); the app shows it day by day
- A calculator on your account page works out what a setup would cost
- If you run out, your metrics pause and new logs and traces are refused until you buy more - nothing is deleted
Questions, answered
How much does it cost?
There are no per-host, per-seat or per-gigabyte charges, and you start with 10,000 free credits. Add more credits any time as necessary, and use the pricing calculator to plan ahead. Each level of a metric costs 15 to 75 credits a month at its default retention (a day level is the cheapest, a minute level the dearest), and 500 logs, or 250 traces, kept for a day cost 1 credit.
What does keeping data longer cost?
Costs scale linearly with retention time, so you can tailor your setup to your needs and budget.
Do I need a subscription?
No. You buy credits when you want more with a normal one-off card payment, and use them as you go. Credits don't expire, and nothing is ever charged to your card automatically, so there is no surprise bill: the most you can spend is what you have chosen to buy. Signups get a generous amount of free credits to start with.
How is usage counted?
Billing runs every hour - the logs and traces you are holding, and the metrics you have - and its credits are taken from your balance. It is rent for what exists: a log kept 7 days is held for 7 days, so costs 7 times one kept 1 day, and a metric you create or delete part-way through the month only costs for the time it existed. Each hour is rounded down. The app shows your usage day by day.
What happens if I run out of credits?
Your metrics pause - they stop recording until you buy more, and restart as soon as you top up - and new logs and traces are refused with a clear message. Nothing is deleted.
Why is pricing per metric rather than per host or per gigabyte?
Because it is the number you can predict. A metric is identified by its name alone - it has no tags or labels - so its price never grows because of what you put in it, and a busy day costs the same as a quiet one. If you want a breakdown, create separate metrics (for example checkout_errors_uk and checkout_errors_us).