You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWS FOCUS export stores TAG in MAP type. Azure fabric does not support this. Azure exports tags to maybe a string of some kind. Can the AWS export be changed so that the tag is exported in the same format as Azure in the parquet file. The workaround is not to export tags field in AWS focus export.
Which area does this issue relate to?
A: Missing FinOps feature, use case, or scenario
Detailed Description
Azure and AWS export to BLOB and S3 with different month/date path names and varying depths of file paths, i.e. they are not aligned which means separate pipelines to parse the file systems of each CSP.
What use cases, FinOps or others, can't be performed with the existing specification unless this issue is addressed?
Work around is in place.
Which FinOps personas does this issue relate to?
Engineering.
Which provider groups or specific providers does this issue relate to?
AWS & AZURE.
On a scale of 1 - 4, how critical is this for your organization?
3: Important for adoption in the next 6-12 months
Objective
Common file system pathing.
Data Examples
No response
Issues, PRs, or Other References
No response
The text was updated successfully, but these errors were encountered:
Summary
AWS FOCUS export stores TAG in MAP type. Azure fabric does not support this. Azure exports tags to maybe a string of some kind. Can the AWS export be changed so that the tag is exported in the same format as Azure in the parquet file. The workaround is not to export tags field in AWS focus export.
Which area does this issue relate to?
A: Missing FinOps feature, use case, or scenario
Detailed Description
Azure and AWS export to BLOB and S3 with different month/date path names and varying depths of file paths, i.e. they are not aligned which means separate pipelines to parse the file systems of each CSP.
What use cases, FinOps or others, can't be performed with the existing specification unless this issue is addressed?
Work around is in place.
Which FinOps personas does this issue relate to?
Engineering.
Which provider groups or specific providers does this issue relate to?
AWS & AZURE.
On a scale of 1 - 4, how critical is this for your organization?
3: Important for adoption in the next 6-12 months
Objective
Common file system pathing.
Data Examples
No response
Issues, PRs, or Other References
No response
The text was updated successfully, but these errors were encountered: