Verifying service health and viewing default Cloudera Lakehouse Optimizer policy

After you verify whether you can access Cloudera Lakehouse Optimizer REST APIs, Cloudera recommends following the best practice of performing a health check of the service, and then verifying whether the ClouderaAdaptive default policy is available in the Cloudera Lakehouse Optimizer Data Hub.

Ensure that the Cloudera Lakehouse Optimizer Data Hub and its components are available and healthy using the GET /config/health API.
```
curl --location 'https://[***LAKEHOUSE OPTIMIZER ENDPOINT***]/cdp-proxy-token/clo/api/v1/config/health' \ --header 'Authorization: Bearer [**JWT Token**]'
```
By default, Cloudera Lakehouse Optimizer performs a partial health check. To perform a full health check, append scope.
```
curl --location 'https://[***LAKEHOUSE OPTIMIZER ENDPOINT***]/cdp-proxy-token/clo/api/v1/config/health?scope=full' \ --header 'Authorization: Bearer ey'
```
tip
Cloudera Lakehouse Optimizer monitors the service components, service tasks, and maintenance actions which include:
- Recent running tasks, task details, and task status.
- Livy connection status.
- Number of triggers available in the scheduler, the policy evaluation count, the ignore task count, and the paused table count.
- Count of tasks sent to Livy and the pending tasks count.
Verify whether the ClouderaAdaptive default policy is available in the Cloudera Lakehouse Optimizer Data Hub using the GET /policies/resource API. The API fetches the default ClouderaAdaptive policy details.
```
curl --location 'https://[***LAKEHOUSE OPTIMIZER ENDPOINT***]/api/v1/policies/resource?uri=clo%3A%2F%2Ftps%3Adefault%2FClouderaAdaptive' \ --header 'Authorization: Bearer ey'
```
For information about the URI to use in the GET /policies/resource API, see Constructing the URI to fetch, upload, and update policy resources.