Telemetry-Based Reallocation Virtual Tag - Unsupported State

Finout’s telemetry-based cost reallocation distributes shared cloud costs based on external telemetry data. When using a telemetry-based reallocation virtual tag, it is essential to always filter or group by keys and values from:

• The same virtual tag

• A nested virtual tag – where at least one rule filters values from the telemetry-based reallocation virtual tag.

However: An issue arises when attempting to cross-match non-nested virtual tags or compare a virtual tag with unrelated tags, such as an AWS tag. Then, if you attempt to filter or group by a telemetry-based reallocation virtual tag while also filtering or grouping by an unrelated attribute, such as an AWS region, Finout cannot compute the query, resulting in an unsupported state. Reallocation is designed for cost allocation, not deep investigation. If a query does not follow these constraints, it may enter an unsupported query state.

Scenario	Supported / Not Supported
Filter by virtual tag "Teams" and group-by virtual tag "Services," where "Teams" is built from "Services" values (nested).	Supported
Filter by virtual tag "Teams" and group-by virtual tag"Services", where both "Teams" and "Services" are not nested.	Not Supported
Filter on AWS tag "Region" and group by virtual tag "Teams".	Not Supported
AND virtual tag rule on virtual tag "Services" and virtual tag "Teams," where "Teams" and "Services" are not nested.	Not Supported

Example: If you create a virtual tag to reallocate RDS compute costs based on telemetry data that shows the number of queries per team and then try to group by this virtual tag in Megabill while filtering by an AWS attribute (such as region), the query will fail.

Use cases that may result in an unsupported query state when using a virtual tag with telemetry-based reallocation:

Megabill View When filtering a value from a virtual tag with telemetry-based reallocation and grouping by an unrelated tag in Megabill (and vice versa). For example:

• Filtering “docs” from a telemetry-based reallocation virtual tag

• Grouping by “AWS Services”

  

Dashboard

When filtering a value from a virtual tag with telemetry-based reallocation on the dashboard while having a widget that groups by an unrelated MegaBill key.

For example:

• Filtering the dashboard by “Teams”, which is a telemetry-based reallocation virtual tag.

• The widget (Showback Report) is grouped by AWS Services.

  

Data Explorer

When adding columns that include both a virtual tag with telemetry-based reallocation and an unrelated MegaBill tag.

For example:

• Selecting “docs” from a telemetry-based reallocation virtual tag as a column.

• Adding another column with an unrelated MegaBill tag like “AWS Services”

  

Anomaly Configuration

When grouping by a telemetry-based reallocation virtual tag while filtering a value from an unrelated MegaBill tag (and vice versa).

For example:

• Filtering by telemetry-based reallocation virtual tag - “Teams”.

• Grouping by a value from an unrelated MegaBill tag like “AWS Services.”

  

Virtual Tags

An unsupported query state appears when filtering within the same rule a telemetry-based-reallocation virtual tag with another unrelated attribute. For example:

• Filtering "Data Team" from telemetry-based reallocation virtual tag “Teams.”

• Filtering “Amazon EC2" in the same rule.

CostGuard, Resource Page, Tag Governance

These pages display resources by default, preventing the addition of a telemetry-based reallocation virtual tag as a column.

Financial Plans

An unsupported query state appears when selecting a telemetry-based reallocation virtual tag for the financial plan hierarchy keys and another unrelated attribute from the Megabill.

My Commitments

An unsupported query state appears when filtering a telemetry-based reallocation virtual tag on the My Commitments page.

Data Access Groups

An unsupported query state appears when filtering a telemetry-based reallocation virtual tag in a data access group.