Finout allows users to import telemetry data to the platform on a daily basis. This functionality enables the creation of precise unit economics, detailed breakdowns of shared costs, and the development of telemetry-based widgets that enhance the monitoring of various data sources together with the MegaBill, Finout’s cost monitoring tool.
This documentation will clarify the process for importing external telemetry data into Finout.
Understanding Telemetry in Finout
In the context of Finout, telemetry refers to any data measurements that users intend to incorporate into Finout. This includes any metrics or data points that can be leveraged to enhance insights, enable monitoring, or assist in managing costs within the platform.
Exploring Telemetry in Finout: What It Looks Like
When preparing your telemetry data for Finout, ensure your input can support the following format, which includes three main attribute types: Date, Metadata, and Metric.
Type of attribute | How many columns can be used? | Mandatory/Optional | What is this used for? | Format / Notes |
Date | Single | Mandatory | Each data row input represents the telemetry for a specific date, accompanied by their metadata values, indicating the day on which the telemetry was recorded. | YYYY-MM-DD “date” column |
Metadata (multiple) | 0-10 | Optional | Any tagging attributes can be utilized to group and filter telemetry data based on metadata such as team, group, or feature. | Optional |
Telemetry | 1 | Mandatory | Represents the total of the telemetry for the given date and metadata. | Positive number |
If the data can be integrated into Finout using this format, it can be used as a telemetry source in Finout’s abilities.
Utilizing Telemetry Data for Shared Cost Breakdown
One of the major advantages of Finout’s telemetry data integration is its ability to provide detailed allocation and breakdown of shared costs, beyond the resource level. This capability is especially important for breaking down multi-tenant use cases (such as cost per development team or cost per customer) that are not easily attributed to their right destinations. It addresses the challenge of expenses that lack granularity from cloud service providers, such as EC2 data transfers or database instances utilized by several tenants (teams/customers).
With Finout's advanced capabilities, users achieve a more granular reallocation of costs beyond basic resource levels, enabling deeper cloud cost analysis and management.
For instance, users can utilize Finout’s reallocation abilities to select a Virtual Tag value and determine a reallocation strategy for that value. This means you can reallocate the cost of an S3 bucket according to an external metric using the Virtual Tags advanced allocation (reallocation) section.
Methods for Integrating Telemetry Data into Finout
To integrate your telemetry data with Finout effectively, please utilize one of the supported methods listed below.
Note: The data for each method is updated once a day as part of our data retrieval process.
S3 Bucket Telemetry Export - Export your telemetry data to an S3 bucket accessible by Finout. Finout automatically samples the bucket daily, identifying new CSV files and data by checking the uploaded file names and their last modification date.
Datadog- If your telemetry data is collected and managed via Datadog, integrate directly with Finout to import metrics.
Snowflake - Connect your Snowflake data warehouse directly with Finout. Documentation is coming soon.
Prometheus - For systems monitored by Prometheus, leverage this integration to forward metrics directly to Finout. This is supported only for accounts with K8s environments that are monitored using Prometheus. After integrating successfully, Finout collects the relevant metrics. Documentation is coming soon.