Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Object Storage]: Collect and export actual cost data for Azure object storage #54

Open
Pokom opened this issue May 5, 2023 · 4 comments
Labels
area/monitoring good first issue Good for newcomers help wanted Extra attention is needed

Comments

@Pokom
Copy link
Contributor

Pokom commented May 5, 2023

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.

@Pokom 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 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
@the-it the-it self-assigned this May 30, 2023
@grafanabot
Copy link

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.

@Pokom Pokom self-assigned this Sep 20, 2023
@Pokom Pokom removed their assignment Dec 13, 2023
@Pokom Pokom transferred this issue from another repository Dec 13, 2023
@jjo
Copy link
Contributor

jjo commented Jun 5, 2024

Possibly happening in Q3 together with compute metrics effort on Azure, depending on #140127.

@Duologic
Copy link
Member

considering #140127 is done, unblock

@Pokom Pokom added area/monitoring good first issue Good for newcomers help wanted Extra attention is needed and removed area/capacity labels Dec 17, 2024
@Pokom
Copy link
Contributor Author

Pokom commented Dec 17, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/monitoring good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants