Usage measurements within Octane are data points that capture changes within your system caused by user action or automated processes. These measurements are the building blocks of your billing and analytics processes, enabling you to gain valuable insights into how your customers interact with your services.
The design of your usage measurements is a crucial step in setting up Octane to work optimally for your business. Properly designed measurements will enable you to generate meaningful metrics, filter data effectively, and aggregate information as needed. Types of usage events can include things such as: API requests, Storage, Login Attempts, Miles Travelled, CPU Utilization etc.
When deciding when to send usage measurements in your system, you have flexibility in choosing the timing that best aligns with your operational preferences. We have seen the following two options for measurement timing:
- Real-time Measurements: You have the option to send an event to Octane as soon as an API request hits your server. This real-time approach allows for granular tracking of usage as it happens and it facilitates invoicing at the end of each month but offers a real-time perspective, which may suit specific analytics needs.
- Summary Measurements: Alternatively, your system can internally track aggregation of all events and send Octane a hourly/daily/weekly per-customer summary. It is a matter of personal preference whether you prefer this periodicity or more immediate reporting.
Throughout & Volume
Octane is built to support extremely high throughput at low latency response times. By taking advantage of our highly scalable architecture Octane can support up to 100k measurements/minute out of the box. Additionally, Octane has the capacity to ramp up to 1 million measurements/minute if needed. We recommend contacting firstname.lastname@example.org in order high throughput needs.
When considering what data to include in these usage measurements, you can tailor the information to meet your specific requirements. While the core usage data is essential for invoicing purposes, you have the flexibility to enrich your events with additional details that could be valuable for your internal records. Here are some examples:
- Compute Type: Include details about what type of compute a customer is using. This information helps in charging differently on different types of compute resources.
- API Endpoint: Specify the URL and our HTTP resource type for the API request. This helps slice and dice your analytics by different kinds of API usage.
While not all of these additional data points are needed for pricing purposes, they can provide valuable insights for optimizing your services, troubleshooting issues, and enhancing your overall operational efficiency.
Ultimately, the choice of what data to include and when to send measurements should align with your unique business goals and preferences. Octane is designed to accommodate your specific requirements, whether you prioritize streamlined reporting or real-time visibility into usage.