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
We are currently in the process of developing a Prometheus exporter to make our Gridscale cloud costs transparent. In the context of this exporter, among others, we expose the running PaaS resources as metrics by periodically scraping the Gridscale API. To be able to determine the cost of a resource, as far as I am aware, we need the products it's using via the product number and in which location it is running. Usages can be retrieved via the usage API, but, in contrast to other resource types, such as servers, PaaS resources do not seem to expose a location attribute via the API.
Is it viable to indirectly determine the location of the PaaS resource via the connected network, or is there another mechanism to retrieve this information from the API?
The text was updated successfully, but these errors were encountered:
We are currently in the process of developing a Prometheus exporter to make our Gridscale cloud costs transparent. In the context of this exporter, among others, we expose the running PaaS resources as metrics by periodically scraping the Gridscale API. To be able to determine the cost of a resource, as far as I am aware, we need the products it's using via the product number and in which location it is running. Usages can be retrieved via the usage API, but, in contrast to other resource types, such as servers, PaaS resources do not seem to expose a location attribute via the API.
Is it viable to indirectly determine the location of the PaaS resource via the connected network, or is there another mechanism to retrieve this information from the API?
The text was updated successfully, but these errors were encountered: