LogoLogo
Contact Us
  • Finout Documentation
  • Get Started with Finout
    • Introduction to Finout's Suite of Features
    • Onboarding New Users to Your Finout Account
    • Single Sign-On (SSO) Setup
    • Enterprise Discount Program (EDP)
    • Cost and Usage Types
      • FairShare Cost
      • List Cost
  • Integrations
    • Cloud Services
      • Connect to AWS
      • Connect to Azure
      • Connect to Oracle
      • Connect to GCP
    • Third Party
      • Connect to Confluent
      • Connect to Databricks
      • Connect to Snowflake
      • Connect to Jira
      • Connect to Datadog
        • Datadog API Cost Calculation
        • Datadog Integration Levels
        • Datadog Usage Attribution Tags (UAT)
      • Connect to Microsoft Teams
      • Connect to ServiceNow
      • Custom Cost Centers
      • Credentials Vault
    • Telemetry
      • S3 Telemetry Integration
      • Setting Up a Datadog - Finout Metrics Integration (Export)
      • MegaBill Telemetry
    • Kubernetes
      • Connect to Kubernetes Prometheus
      • Kubernetes - How Finout Calculates K8s Costs
      • Kubernetes MegaBill
      • Kubernetes Budgeting
      • Kubernetes Anomaly Detection
      • Kubernetes Custom Dashboards
      • Kubernetes Predefined Dashboards
      • Ensure Compatibility of Your Kubernetes Monitoring with Finout
  • User Guide
    • Inform
      • MegaBill
      • Custom Drilldown
      • Custom Cost Input
      • Virtual Tags
        • Relational Virtual Tags
        • Virtual Tag Sync
      • Shared Cost Reallocation
        • How to Use Shared Cost Reallocation
      • FinOps Dashboards
      • Financial Plans
      • Data Explorer
    • Optimize
      • My Commitments
      • Commitments Log
      • Anomalies
      • CostGuard
        • CostGuard - Scans
        • Connect CostGuard for AWS
          • AWS Extended Support Detection
        • Connect CostGuard for GCP
    • Operate
      • Reports
      • Tag Governance
  • Configuration
    • Finout API
      • Generate an API Token
      • Filter Object Definition
      • Cost API
      • Query Language API
      • Virtual Tags API
      • CostGuard API
      • Endpoint API
      • Virtual Tag Metadata API
    • Role-Based Access Control (RBAC)
      • Role Permissions
      • Managing Roles
        • Creating a Custom Role
        • Permissions List
        • Managing a Role and its Permissions
      • Managing Users
        • Inviting a User
        • Edit a User's Roles
      • Data Access Control
      • Groups
        • Create a New Group
        • Edit Group Data Access
        • Delete a group
        • Edit Group Users and SAML Groups
      • RBAC FAQs
    • Endpoints
      • Slack Notification Endpoint
  • Cross-Platform Features
    • List of Cross-Platform Features
      • ACL Permissions
      • Saved Views
Powered by GitBook

Still need help? Please feel free to reach out to our team at support@finout.io.

On this page
  • Utilizing Telemetry Data for Shared Cost Breakdown
  • Methods for Integrating Telemetry Data into Finout

Was this helpful?

Export as PDF
  1. Integrations

Telemetry

PreviousCredentials VaultNextS3 Telemetry Integration

Last updated 2 months ago

Was this helpful?

Finout allows users to import telemetry data to the platform daily. This functionality enables the creation of precise unit economics, detailed , and the development of telemetry-based widgets that enhance the monitoring of various data sources together with the .

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.

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 value and determine a reallocation strategy. 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. This can be done through external telemetry sources or internally through Finout.

Note: The data for each method is updated once a day as part of our data retrieval process.

External Telemetry Sources

  • 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.

Internal Telemetry Sources

- 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.

- If your telemetry data is collected and managed via Datadog, integrate directly with Finout to import metrics.

- You can create a MegaBill based telemetry using historical cost and usage data. This telemetry functions like externally sourced telemetry and supports virtual tag reallocations, enabling more precise cost attribution.

breakdowns of shared costs
MegaBill
Virtual Tag
S3 Bucket Telemetry Export
Datadog
MegaBill