Get the endpoint that is being used to call (ex, https://www.example.com).
Sets the endpoint to call (ex, https://www.example.com).
The endpoint of the service.
Sets the region to call (ex, Region.US_PHOENIX_1). Note, this will call {@link #endpoint(String) endpoint} after resolving the endpoint.
The region of the service.
Sets the regionId to call (ex, 'us-phoenix-1').
Note, this will first try to map the region ID to a known Region and call {@link #region(Region) region}. If no known Region could be determined, it will create an endpoint assuming its in default Realm OC1 and then call {@link #endpoint(String) endpoint}.
The public region ID.
Determines whether realm specific endpoint should be used or not. Set realmSpecificEndpointTemplateEnabled to "true" if the user wants to enable use of realm specific endpoint template, otherwise set it to "false"
flag to enable the use of realm specific endpoint template
Moves the dashboard from the existing compartment to a new compartment.
This operation does not retry by default if the user has not defined a retry configuration.
ChangeManagementDashboardsCompartmentResponse
Moves the saved search from the existing compartment to a new compartment.
This operation does not retry by default if the user has not defined a retry configuration.
ChangeManagementSavedSearchesCompartmentResponse
Close the client once it is no longer needed
Creates a new dashboard. Limit for number of saved searches in a dashboard is 20.
Here's an example of how you can use CLI to create a dashboard. For information on the details that must be passed to CREATE, you can use the GET API to obtain the Create.json file:
oci management-dashboard dashboard get --management-dashboard-id \"ocid1.managementdashboard.oc1..dashboardId1\" --query data > Create.json.
You can then modify the Create.json file by removing the id attribute and making other required changes, and use the oci management-dashboard dashboard create command.
This operation does not retry by default if the user has not defined a retry configuration.
CreateManagementDashboardResponse
Creates a new saved search.
Here's an example of how you can use CLI to create a saved search. For information on the details that must be passed to CREATE, you can use the GET API to obtain the Create.json file:
oci management-dashboard saved-search get --management-saved-search-id ocid1.managementsavedsearch.oc1..savedsearchId1 --query data > Create.json.
You can then modify the Create.json file by removing the id attribute and making other required changes, and use the oci management-dashboard saved-search create command.
This operation does not retry by default if the user has not defined a retry configuration.
CreateManagementSavedSearchResponse
Creates a new DashxApisWaiter for resources for this service.
The waiter configuration for termination and delay strategy
The service waiters.
Deletes a Dashboard by ID. This operation does not retry by default if the user has not defined a retry configuration.
DeleteManagementDashboardResponse
Deletes a saved search by ID. This operation does not retry by default if the user has not defined a retry configuration.
DeleteManagementSavedSearchResponse
Exports an array of dashboards and their saved searches. Export is designed to work with importDashboard.
Here's an example of how you can use CLI to export a dashboard:
$oci management-dashboard dashboard export --query data --export-dashboard-id \"{\\\"dashboardIds\\\":[\\\"ocid1.managementdashboard.oc1..dashboardId1\\\"]}\" > dashboards.json
This operation does not retry by default if the user has not defined a retry configuration.
ExportDashboardResponse
Gets a dashboard and its saved searches by ID. Deleted or unauthorized saved searches are marked by tile's state property. This operation does not retry by default if the user has not defined a retry configuration.
GetManagementDashboardResponse
Gets a saved search by ID. This operation does not retry by default if the user has not defined a retry configuration.
GetManagementSavedSearchResponse
Gets the waiters available for resources for this service.
The service waiters.
Imports an array of dashboards and their saved searches.
Here's an example of how you can use CLI to import a dashboard. For information on the details that must be passed to IMPORT, you can use the EXPORT API to obtain the Import.json file:
oci management-dashboard dashboard export --query data --export-dashboard-id \"{\\\"dashboardIds\\\":[\\\"ocid1.managementdashboard.oc1..dashboardId1\\\"]}\" > Import.json.
Note that import API updates the resource if it already exists, and creates a new resource if it does not exist. To import to a different compartment, edit and change the compartmentId to the desired compartment OCID.
Here's an example of how you can use CLI to import:
oci management-dashboard dashboard import --from-json file://Import.json
This operation does not retry by default if the user has not defined a retry configuration.
ImportDashboardResponse
Gets the list of dashboards in a compartment with pagination. Returned properties are the summary. This operation does not retry by default if the user has not defined a retry configuration.
ListManagementDashboardsResponse
Gets the list of saved searches in a compartment with pagination. Returned properties are the summary. This operation does not retry by default if the user has not defined a retry configuration.
ListManagementSavedSearchesResponse
Shutdown the circuit breaker used by the client when it is no longer needed
Updates an existing dashboard identified by ID path parameter. CompartmentId can be modified only by the changeCompartment API. Limit for number of saved searches in a dashboard is 20.
This operation does not retry by default if the user has not defined a retry configuration.
UpdateManagementDashboardResponse
Updates an existing saved search identified by ID path parameter. CompartmentId can be modified only by the changeCompartment API.
This operation does not retry by default if the user has not defined a retry configuration.
UpdateManagementSavedSearchResponse
This service client uses {@link common.CircuitBreaker.DefaultConfiguration} for all the operations by default if no circuit breaker configuration is defined by the user.