V Rli APIs
APIs for managing vRealize Log Insight
1. vRealize Log Insight
In order to have vRealize Log Insight you need to first deploy vRealize Suite Lifecycle Manager and then Workspace ONE Access. After vRealize Suite Lifecycle Manager is deployed please refer to its public API documentation to deploy Workspace ONE Access and vRealize Log Insight.
Tip : Refer to Deploy vRealize Suite Lifecycle Manager API, Get all existing vRealize Log Insight instances API
1.1. Steps
- Deploy vRealize Suite Lifecycle Manager.
Tip : Refer to Deploy vRealize Suite Lifecycle Manager API
- Refer to vRealize Suite Lifecycle Manager Public API documentation for creating global environment.
Tip : Refer to vRSLCM create environment API guide
- Refer to vRealize Suite Lifecycle Manager Public API documentation for creating vRealize Log Insight environment.
Tip : Refer to vRSLCM create environment API guide
vRealize Log Insight is being automatically connected to the management domain after deployment.
Refer to Connect vRealize Log Insight to workload domains for connection vRealize Log Insight to workload domains.
2. Connect vRealize Log Insight to workload domains
You can connect vRealize Log Insight product deployment in Cloud Foundation to your workload domains.
2.1. Prerequisites
- Verify that the vRealize Log Insight cluster is online and operational.
Tip : Refer to Get all existing vRealize Log Insight instances API
2.2. Steps
- Assemble the vRealize Log Insight domain specification.
Tip : Refer to Vrli
- Trigger the vRealize Log Insight domain connection.
Tip : For help using the vRealize Log Insight domain connection API refer to: Connects vRealize Log Insight with domain API
cURL Request
$ curl 'https://sfo-vcf01.rainpole.io/v1/vrli/domains' -i -X PUT \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer etYWRta....' \
-d '{
"domainId" : "8e9dc2d6-a96c-4db3-b964-8326796d64d7",
"status" : "ENABLED"
}'
HTTP Request
PUT /v1/vrli/domains HTTP/1.1
Content-Type: application/json
Content-Length: 81
Host: sfo-vcf01.rainpole.io
Authorization: Bearer etYWRta....
{
"domainId" : "8e9dc2d6-a96c-4db3-b964-8326796d64d7",
"status" : "ENABLED"
}
HTTP Response
HTTP/1.1 202 Accepted
Location: /v1/tasks/9b56b98b-ba62-42cb-9ac1-f65e2d20ff9c
Allow: PUT
Content-Type: application/json
Content-Length: 130
{
"id" : "9b56b98b-ba62-42cb-9ac1-f65e2d20ff9c",
"status" : "SUCCESSFUL",
"creationTimestamp" : "2019-05-10T11:13:22.551Z"
}
Note : This operation is a long-running task which details can be obtained form the HTTP response.
- Track the task status using the "id" from the previous response.
Tip : Refer to: Get a Task.
If the "status" is "IN_PROGRESS", the task is still in progress.
If the "status" is "SUCCESSFUL", the task is completed successfully.
If the "status" is "FAILED", the task can be re-executed.
Tip : For task re-execution refer to: Retry a Task.
Last updated 2022-01-24 06:18:36 PST