-
Notifications
You must be signed in to change notification settings - Fork 268
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
How to find the physical location and geographical region of the particular resource #598
Comments
Can you specify which specific OCI service or API you are using for obtaining resource and meter information? |
@richachugh11 , I used the below API to fetch the details of the particular resource present in the console. But, I am not able to get the two different regions. |
@adizohar can you look into this? I am using below api : |
Gopi, currently, there is no bandwidth and target region in the usage api |
Thank you for providing the information@adizohar |
@adizohar Can we get this information from Network flow logs or Network command center? |
Flowlogs will give you source and dest ip address and few more items |
For Azure: while getting the resource information from the cloud we are getting the following example-
when the meter type is bandwidth[it is the parameter the datatrasfer is happening in that resource] we were calculating the network traffic cost.
For OCI:
In the same way, the resource location is coming from the API response. But how to get the another location for the same resource. Is their any terminology difference to get that regions in OCI.
As per my knowledge, resource region means physical location of the resource. meter_region means the geographical scope of the usage being metered. By using these two locations and usage quantity we want to calculate the network traffic cost.
My query is, how to get the geographical scope of the usage being metered.
Is their any terminology difference in the OCI?
will you please provide the API to get the another region from where the data transfer is happening?
currently, we were using usageapi
The text was updated successfully, but these errors were encountered: