Trace
A trace tracks time spent by an application processing a request and the status of this request. Each trace consists of one or more spans.
Span
A span represents a logical unit of work in a distributed system for a given time period. Multiple spans construct a trace.
- Change log retention to 14 days if you can
- Talk to your account manager to discuss discounts.
- Learn your usage and estimate, then commit spending to get lower rate
- Reduce cardinality of custom metrics
- Turn on Sampling (10% or lower) for everything
- Review your retention filters
Your App -> Ingestion Sampling rules -> 15m Live Search
15m Live Search -> Retention Filter -> 15 days indexed search
15m Live Search -> Metrics from Spans
- Static price v.s. on-demand price
- Charge for Infra host
- Charge for Fargate tasks
- Indexed Spans
- Ingested Spans
Custom Metrics
Ingested Custom Metrics
- Indexed Logs 7d $ per 1M logs
- Indexed Logs 15d $ per 1M logs
- Indexed Logs 30d $ per 1M logs
- Indexed Logs $ per GB
- Serverless invocation $ per 1M invocations