This topic describes how to view the state of work requests associated with a given load balancer.
The Load Balancing service does not use the common Work Requests API to support work request operations. Instead, Load Balancing work requests are supported by the Load Balancing API. See Using the Console to View Work Requests for information on viewing work requests for other services.
To use Oracle Cloud Infrastructure, you must be given the required type of access in a An IAM document that specifies who has what type of access to your resources. It is used in different ways: to mean an individual statement written in the policy language; to mean a collection of statements in a single, named "policy" document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean the overall body of policies your organization uses to control access to resources. written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which A collection of related resources that can be accessed only by certain groups that have been given permission by an administrator in your organization. you should work in.
For administrators: For a typical policy that gives access to load balancers and their components, see Let network admins manage load balancers.
Also, be aware that a policy statement with
inspect load-balancers gives the specified group the ability to see all information about the load balancers. For more information, see Details for Load Balancing.
Monitoring Work Requests
Many of the Oracle Cloud Infrastructure Load Balancing service requests do not take effect immediately. In these cases, the request spawns an asynchronous workflow for fulfillment. To provide visibility for in-progress workflows, the Load Balancing service creates a work request object. Because some operations depend on the completion of other operations, you must monitor each operation’s work request and confirm it has succeeded before proceeding to the next operation. For example, if you want to create a A logical entity defined by a list of backend servers, a load balancing policy, and a health check policy. and add a backend server to the new set, you first must create the backend set. After that operation completes, you can add the backend server. If you try to add a backend server before the backend set creation completes, the system cannot ensure that the request to add the server succeeds. You can monitor the request to add a backend set to determine when that workflow is complete, and then add the backend server.
The work request states are:
- The request is in the work request queue to be processed.
- in progress
- A work request record exists for the specified request, but there is no associated WORK_COMPLETED record.
- A work request record exists for this request and an associated WORK_COMPLETED record has the state SUCCEEDED.
- A work request record exists for this request and an associated WORK_COMPLETED record has the state FAILED.
Using the Console
The Oracle Cloud Infrastructure Console consumes the REST API and is subject to the same considerations as any Oracle Cloud Infrastructure client. You can view the state of a load balancing work request in the Console:
Open the navigation menu. Under the Core Infrastructure group, go to Networking and click Load Balancers.
- Click the name of the Compartment that contains the load balancer you want to review, and then click the load balancer's name.
- In the Resources menu, click Work Requests. The status of all work requests appears on the page.
Using the API
For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.
Use these operations to monitor the state of work requests: