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
When we initially started cloudcost-exporter, our focus was on GCP and then AWS with Azure as a very far distant priority. Before we go live with cloudcost-exporter we should implement exporting Azure Object Storage costs.
The text was updated successfully, but these errors were encountered:
Pokom
changed the title
Collect and export actual cost data for GCP/AWS/Azure object storage
[Object Storage]: Collect and export actual cost data for GCP/AWS/Azure object storage
May 15, 2023
Pokom
changed the title
[Object Storage]: Collect and export actual cost data for GCP/AWS/Azure object storage
[Object Storage]: Collect and export actual cost data for Azure object storage
May 26, 2023
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution.
This is a good first issue for someone that would want to learn more about how to build a collector from scratch that isn't time sensitive. I've added appropriate labels and will update the issue with appropriate documentation and requirements.
When we initially started
cloudcost-exporter
, our focus was on GCP and then AWS with Azure as a very far distant priority. Before we go live withcloudcost-exporter
we should implement exporting Azure Object Storage costs.The text was updated successfully, but these errors were encountered: