OCI does not charge per API request. OCI pricing for monitoring is based on datapoints, and it includes both ingestion and retrieval.
A datapoint represents a single metric value at a specific timestamp.
Cost calculation example
Retrieval example (relevant for Site24x7)
Let’s say your monitoring setup retrieves:
- 1.2 billion datapoints in a month
Cost calculation:
First 1 billion datapoints → Free
Remaining 200 million datapoints → Charged
Cost = 200 million ÷ 1 million × $0.0015
= $0.30
Ingestion example (for completeness)
If your environment sends:
- 600 million datapoints in a month
Cost calculation:
First 500 million datapoints → Free
Remaining 100 million datapoints → Charged
Cost = 100 million ÷ 1 million × $0.0025
= $0.25
Factors that impact cost
Your total datapoint usage depends on:
- Number of monitored resources
- Number of metrics per resource
- Query frequency
- Time range of each query
- Granularity of data (1 min vs 5 mins intervals)
Best practices to optimize costs
- Use longer aggregation intervals where possible.
- Avoid unnecessary high-frequency polling.
- Limit metrics to only what is required.
- Monitor your monthly datapoint usage trends.
Key takeaway
OCI monitoring pricing is datapoint-based, not API call-based. Even though Site24x7 uses the SummarizeMetricsData API, your cost depends entirely on how much metric data is retrieved. Staying within the free tier is achievable with efficient monitoring strategies and controlled query patterns.
Related articles
- OCI Monitoring